From: "W. Craig Scratchley" <wcs@sfu.ca>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Location of temporary file for sectors on Windows (XP)
Date: Thu, 1 Dec 2005 16:58:34 -0800 [thread overview]
Message-ID: <004901c5f6db$8b702360$4033a8c0@asb8834craig> (raw)
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
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=c:\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).
[-- Attachment #2: Type: text/html, Size: 5305 bytes --]
next reply other threads:[~2005-12-02 0:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 0:58 W. Craig Scratchley [this message]
2005-12-06 1:30 ` [Qemu-devel] Location of temporary file for sectors on Windows (XP) Johannes Schindelin
2005-12-06 1:46 ` malc
2005-12-06 1:56 ` Johannes Schindelin
2005-12-06 2:01 ` malc
2005-12-06 7:44 ` [Qemu-devel] Location of temporary file for sectors on Windows Jernej Simončič
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004901c5f6db$8b702360$4033a8c0@asb8834craig' \
--to=wcs@sfu.ca \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).