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
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
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
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
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
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 simple
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
(I
