From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EBZRY-0001Vy-OS for qemu-devel@nongnu.org; Sat, 03 Sep 2005 10:56:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EBZRN-0001SN-Ka for qemu-devel@nongnu.org; Sat, 03 Sep 2005 10:56:23 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EBZRN-0001RK-8i for qemu-devel@nongnu.org; Sat, 03 Sep 2005 10:56:21 -0400 Received: from [195.250.128.83] (helo=smtp3.vol.cz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EBZPD-0005vj-Co for qemu-devel@nongnu.org; Sat, 03 Sep 2005 10:54:07 -0400 Received: from [10.0.0.2] (prg-v-6-220.static.adsl.vol.cz [62.177.70.220]) by smtp3.vol.cz (Postfix) with ESMTP id AC4E15932C for ; Sat, 3 Sep 2005 16:48:32 +0200 (CEST) Message-ID: <4319B7C3.8010105@reactos.com> Date: Sat, 03 Sep 2005 16:48:35 +0200 From: Filip Navara MIME-Version: 1.0 Subject: Re: [Qemu-devel] QEMU_TMPDIR temp folder for KQEMU for Windows. References: <20050830134218.17388.qmail@web50508.mail.yahoo.com> In-Reply-To: <20050830134218.17388.qmail@web50508.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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 there. What I'm saying is that on QEMU/Windows there's no "big hidden file containing the RAM of the virtual machine", it's simply stored in the host RAM (and the host OS can decide to page out parts of it to disk - to pagefile.sys, or whatever is setup - but it may not do so if you have enough physical memory available). On other platforms where QEMU runs there's the famous "big hidden file containing the RAM of the virtual machine" and it's mapped into memory and used as the storage of guest RAM. Whenever the OS decides the in-memory contents are synced with the on-disk file. Actually I don't understand the benefits of putting it on real ramdisk (...but /dev/shm, or actually TMPFS is not *REAL RAMDISK* since it grows and shrink based on the contents and the pages can be be swapped out ... so in a way it does the same thing as we accomplish on Windows with pure virtual memory allocation). Maybe I haven't explained the details correctly (and I'm not exactly sure about them on the *nix side of things), but the point is that no such file containing the guest RAM is present on Windows. - Filip