On 9/3/05, ace <[EMAIL PROTECTED]> wrote:
> Hi.
> 2. you say you can't see the temporary file. Neither do I, on linux. I
> suspect it is not hidden using plain filesystem attributes. On linux, if
> you open a file and then delete (unlink) it, you can still work with it
> until you hold the file des
Francois Rioux wrote:
Filip,
I'm not trying to put the guest in ram. As you state, let's Windows
manage its whole memory, paging and swapping. I agree it would be as
dumb as setting up a ramdisk to put the swapfile. Let's not trying to
outsmart the OS.
There's slight misunderstaning the
Hi.
Two points for you:
1. currently your tempfile with qemu quest system memory is located on
disk. Is your disk working hard? If you have enough free ram that you
consider the ramdisk, the whole file is probably cached in host system
memory so that read/write access is fast. Of course there it w
> "When using KQEMU, QEMU will create a big hidden file containing the RAM of
> the virtual machine. For best performance, it is important that this file
> is kept in RAM and not on the hard disk. QEMU uses the `/dev/shm' directory
> to create this file because tmpfs is usually mounted on it (check
Filip,
I'm not trying to put the guest in ram. As you state, let's Windows manage its whole memory, paging and swapping. I agree it would be as dumb as setting up a ramdisk to put the swapfile. Let's not trying to outsmart the OS.
I was trying to follow Fabrice recommendation to set the QEMU
Francois Rioux wrote:
[snip]
Ramdisk might have been a real performance accelerator for Windows
hosts with enough RAM available. Since I can't find the temp memory
image file is saved, I can't use that option.
Why do you think that it would improve performance? Sorry, but that's
complete ru
Thank you folks for the insights.
I know everyone with the knowledge in made magic to come with the current QEMU and you're working on enhancements. I'm unfortunately unable to help with that. I couldn't even make my own build for on Windows!
That said, I'm curioux and looking for out of t
On Mon, Aug 29, 2005 at 11:05:05AM -0700, Francois Rioux wrote:
>
> The KQEMU doc mentions setting QEMU_TMPDIR to a ramdisk for increased
> performances under KQEMU which saves the memory image of the guest OS.
>
> I'm running XP Pro as the Host with qemu version 0.7.1-3 which includes KQEMU
>
On Mon, Aug 29, 2005 at 11:53:26AM -0700, John R. Hogerhuis wrote:
> On Mon, 2005-08-29 at 11:05 -0700, Francois Rioux wrote:
>
> KQEMU presumably does this on X86 by inlining more of the original code
> with minimal changes (i.e more tokens containing bigger swaths of native
> code, and less simp
On Mon, 2005-08-29 at 11:05 -0700, Francois Rioux wrote:
> I notice that QEMU is quite slower than VMWare.
It certainly is.
> Apparently due to the way IO occur. What are the strategies to
> enhance that performance?
Curious, why do you think that? There are probably a whole host of
reasons
The KQEMU doc mentions setting QEMU_TMPDIR to a ramdisk for increased performances under KQEMU which saves the memory image of the guest OS.
I'm running XP Pro as the Host with qemu version 0.7.1-3 which includes KQEMU (I can see it is enabled with 'info kqemu'.)
I've added 'set QEMU_TMPDIR=c:\tmp'
11 matches
Mail list logo
