From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QCOW/QCOW2 for win32
Date: Thu, 7 Sep 2006 15:13:23 +0900 [thread overview]
Message-ID: <000601c6d244$b9eddb20$0464a8c0@athlon> (raw)
Hi,
A patch below fixes QCOW/QCOW2 for win32.
-snapshot option works. When -snapshot is used, a temporary file is
created at C:\Documents and Settings\(user name)\Local Settings\temp.
In path_is_absolute in block.c, path separation '/' also works for win32.
A named snapshot works. I can make a named temporary file by qemu-img.exe
and boots from it.
When I used qcow2, VM snapshots work.
localtime in block.c is thread-safe for win32.
For more information, see.
http://www.h7.dion.ne.jp/~qemu-win/HowToFloppyCdrom-en.html#snapshot
Patch.
http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060906-qcow.patch
Binary.
http://www.h6.dion.ne.jp/~kazuw/qemu-win/qemu-20060906-qcow.zip
Regards,
Kazu
next reply other threads:[~2006-09-07 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 6:13 Kazu [this message]
2006-09-11 0:28 ` [Qemu-devel] QCOW/QCOW2 for win32 Jamie Lokier
2006-09-11 5:32 ` Kazu
2006-09-11 21:53 ` Jamie Lokier
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='000601c6d244$b9eddb20$0464a8c0@athlon' \
--to=kazoo@r3.dion.ne.jp \
--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).