From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EhzGR-00060J-JM for qemu-devel@nongnu.org; Thu, 01 Dec 2005 19:59:04 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EhzGI-0005vG-Td for qemu-devel@nongnu.org; Thu, 01 Dec 2005 19:59:01 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EhzGH-0005um-Cm for qemu-devel@nongnu.org; Thu, 01 Dec 2005 19:58:54 -0500 Received: from [142.58.101.21] (helo=rm-rstar.sfu.ca) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EhzGG-0005HW-Uv for qemu-devel@nongnu.org; Thu, 01 Dec 2005 19:58:53 -0500 Received: from asb8834craig (asb8834craig.ensc.sfu.ca [142.58.140.17]) by rm-rstar.sfu.ca (8.13.4/8.13.4/SFU-5.0H) with ESMTP id jB20wiTA017738 for ; Thu, 1 Dec 2005 16:58:44 -0800 (PST) From: "W. Craig Scratchley" Date: Thu, 1 Dec 2005 16:58:34 -0800 Message-ID: <004901c5f6db$8b702360$4033a8c0@asb8834craig> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004A_01C5F698.7D4CE360" Subject: [Qemu-devel] Location of temporary file for sectors on Windows (XP) 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 This is a multi-part message in MIME format. ------=_NextPart_000_004A_01C5F698.7D4CE360 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The user manual reads: =20 "If you use the option `-snapshot', all disk images are considered as = read only. When sectors in written, they are written in a temporary file = created in `/tmp'." =20 On Windows (XP), however, I am getting files of the form s??? in the C:\ directory. This is causing problems at SFU because student accounts = don't have write access to the C:\ directory and this seems to be causing Qemu = to immediately crash. =20 Note that I do have a directory C:\tmp, but it is not being used for = this temporary file. Also, my system has environment variables TMP and TEMP, = and these are not being consulted. =20 Then, I entered the following line: =20 set QEMU_TMPDIR=3Dc:\tmp =20 But this also had no effect. =20 Finally, note that the s??? files in my C:\ directory are not being = deleted by Qemu, which means an arbitrary amount of space can get taken up by = the files over time. =20 Seems like an issue which has not yet been addressed for Windows builds. =20 Thanks, Craig Scratchley, Simon Fraser University =20 p.s. I am now successfully using Qemu for QNX 6.3.0 as a guest (seems I must use the -isa option for Qemu to get networking). The -loadvm = option is great, as QNX is very slow to boot in QNX (it is much faster for me in Bochs). ------=_NextPart_000_004A_01C5F698.7D4CE360 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The user manual reads:

“If you use the option = `-snapshot', all disk images are = considered as read only. When sectors in written, they are written in a temporary file created in `/tmp'.”

On Windows (XP), however, I am getting files of the form s??? in = the C:\ directory. This is causing problems at SFU because student = accounts don’t have write access to the C:\ directory and this seems to be causing Qemu = to immediately crash.

Note that I do have a directory C:\tmp, but it is not being used = for this temporary file. Also, my system has environment variables TMP = and TEMP, and these are not being consulted.

Then, I entered the following line:

set QEMU_TMPDIR=3Dc:\tmp

But this also had no effect.

Finally, note that the s??? files in my C:\ directory = are not being deleted by Qemu, which means an arbitrary amount of space can get = taken up by the files over time.

Seems like an issue which has not yet been addressed = for Windows builds.

Thanks,

Craig Scratchley, = Simon Fraser University

=

p.s. I am now successfully using Qemu for QNX = 6.3.0 as a guest (seems I must use the –isa option for Qemu to get = networking). The –loadvm option is great, as QNX is very slow to boot in QNX (it is = much faster for me in Bochs).

------=_NextPart_000_004A_01C5F698.7D4CE360--