From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Maubv-0004ex-Tl for qemu-devel@nongnu.org; Tue, 11 Aug 2009 12:54:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Maubq-0004YR-NT for qemu-devel@nongnu.org; Tue, 11 Aug 2009 12:54:07 -0400 Received: from [199.232.76.173] (port=35226 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Maubq-0004YK-Ck for qemu-devel@nongnu.org; Tue, 11 Aug 2009 12:54:02 -0400 Received: from mail-ew0-f210.google.com ([209.85.219.210]:61130) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Maubp-0000zA-US for qemu-devel@nongnu.org; Tue, 11 Aug 2009 12:54:02 -0400 Received: by ewy6 with SMTP id 6so2078853ewy.34 for ; Tue, 11 Aug 2009 09:53:58 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 11 Aug 2009 09:53:57 -0700 Message-ID: From: Atoosah Content-Type: multipart/alternative; boundary=001517491f4e6d33ab0470e08c20 Subject: [Qemu-devel] Qemu snapshot mode: /tmp/vl.xxx file missing? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --001517491f4e6d33ab0470e08c20 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit When using the -snapshot mode of Qemu, shouldn't the vl.xxx file that is created be visible in the host /tmp directory? I use the command: $qemu -snapshot -hda disk_image.img -m 256 which seems to write the file to /tmp/vl.xxx where xxx is some random filename chosen by Qemu during every boot (I see this by commenting [QEMU_PATH]/block.c I'm using a modified version of qemu-0.8.2 on a Linux machine, but I also can't find the vl.xxx file that's created using qemu-0.9.0. In the documentation, it says that when using snapshot mode "When sectors in [misspelling] in written, they are written in a temporary file created in '/tmp'..." but i cannot see the file that is supposedly created on the host directory /tmp (or in QEMU_PATH directory). Where is Qemu actually writting to in snapshot mode, before commit ever occurs? Any suggestions and ideas would be helpful. thank you, Atoosaah --001517491f4e6d33ab0470e08c20 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable When using the -snapshot mode of Qemu, shouldn't the vl.xxx file that i= s created be visible in the host /tmp directory?

I use the command: = $qemu -snapshot -hda disk_image.img -m 256

which seems to write the= file to /tmp/vl.xxx where xxx is some random filename chosen by Qemu durin= g every boot (I see this by commenting [QEMU_PATH]/block.c I'm using a = modified version of qemu-0.8.2 on a Linux machine, but I also can't fin= d the vl.xxx file that's created using qemu-0.9.0.

In the documentation, it says that when using snapshot mode "When = sectors in [misspelling] in written, they are written in a temporary file c= reated in '/tmp'..." but i cannot see the file that is suppose= dly created on the host directory /tmp (or in QEMU_PATH directory). Where i= s Qemu actually writting to in snapshot mode, before commit ever occurs?
Any suggestions and ideas would be helpful.

thank you,
Atoosa= ah
--001517491f4e6d33ab0470e08c20--