From: "André Braga" <meianoite@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU won't load QCOW images under Windows
Date: Sat, 9 Oct 2004 00:42:37 -0300 [thread overview]
Message-ID: <2ad73a0410082042be44bb5@mail.gmail.com> (raw)
The title says it all. If I try to start QEMU with a qcow image passed
as an argument to -hda , the emulator won't load. If I pass a raw
image instead, it works perfectly.
Wasn't QCOW supposed to address exactly a problem regarding Windows
and the lack of support for holes in the filesystem?
Any clues? Is there a strace equivalent for Windows so I can at least
try to track the problem down? (I'm not really fond of the mingw gdb
port, mind you...)
--
"A year spent in artificial intelligence is enough to make one believe in God"
Alan J. Perlis
next reply other threads:[~2004-10-09 3:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 3:42 André Braga [this message]
2004-10-09 12:27 ` [Qemu-devel] Re: QEMU won't load QCOW images under Windows Ronald
2004-10-09 12:42 ` Ronald
2004-10-09 18:51 ` André Braga
2004-10-09 19:25 ` [Qemu-devel] " Ronald
2004-10-09 19:53 ` André Braga
2004-10-10 6:59 ` [Qemu-devel] " Anand Kumria
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=2ad73a0410082042be44bb5@mail.gmail.com \
--to=meianoite@gmail.com \
--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).