qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU won't load QCOW images under Windows
Date: Sat, 09 Oct 2004 14:27:11 +0200	[thread overview]
Message-ID: <pan.2004.10.09.12.27.10.342085@reply.to> (raw)
In-Reply-To: 2ad73a0410082042be44bb5@mail.gmail.com

Le Sat, 09 Oct 2004 00:42:37 -0300, André Braga a écrit :

> 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...)

some observations:
I can't get infos from qcow images created under windows with qemu-img
under linux.
Qcow images created under linux and windows for the same base file,
don't differs only by the path of the base file.
I don't know if this is normal or not.
Here is two hexdump from qcow images created under linux and windows:

ronald@Athena$ hexdump -C slack.qco
00000000  51 46 49 fb 00 00 00 01  00 00 00 00 00 00 00 30  |QFIû...........0|
00000010  00 00 00 12 41 67 19 58  00 00 00 00 1f 40 00 00  |....Ag.X.....@..|
00000020  09 0c 00 00 00 00 00 00  00 00 00 00 00 00 00 48  |...............H|
00000030  2f 6d 6e 74 2f 64 6f 73  2f 73 6c 61 63 6b 2e 64  |/mnt/dos/slack.d|
00000040  73 6b 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |sk..............|
00000050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00000810  00 00 00 00 00 00 00 00                           |........|
00000818

ronald@Athena$ hexdump -C slack.qcw
00000000  51 46 49 fb 00 00 00 01  00 00 00 00 00 00 00 2e  |QFIû............|
00000010  00 00 00 0c 19 58 41 67  00 00 00 00 1f 40 00 00  |.....XAg.....@..|
00000020  09 0c 00 00 00 00 00 00  00 00 00 00 00 40 43 3a  |.............@C:|
00000030  5c 73 6c 61 63 6b 2e 64  73 6b 00 00 00 00 00 00  |\slack.dsk......|
00000040  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00000810

  reply	other threads:[~2004-10-09 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-09  3:42 [Qemu-devel] QEMU won't load QCOW images under Windows André Braga
2004-10-09 12:27 ` Ronald [this message]
2004-10-09 12:42   ` [Qemu-devel] " 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=pan.2004.10.09.12.27.10.342085@reply.to \
    --to=look@reply.to \
    --cc=daimon55@free.fr \
    --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).