From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CGGQb-00037U-94 for qemu-devel@nongnu.org; Sat, 09 Oct 2004 08:34:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CGGQa-00037H-Qm for qemu-devel@nongnu.org; Sat, 09 Oct 2004 08:34:25 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CGGQZ-00037C-MX for qemu-devel@nongnu.org; Sat, 09 Oct 2004 08:34:24 -0400 Received: from [80.91.229.2] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CGGJg-00016h-Ag for qemu-devel@nongnu.org; Sat, 09 Oct 2004 08:27:16 -0400 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CGGJf-0005LB-00 for ; Sat, 09 Oct 2004 14:27:15 +0200 Received: from amarseille-206-1-17-3.w81-50.abo.wanadoo.fr ([81.50.82.3]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Oct 2004 14:27:15 +0200 Received: from daimon55 by amarseille-206-1-17-3.w81-50.abo.wanadoo.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Oct 2004 14:27:15 +0200 From: Ronald Date: Sat, 09 Oct 2004 14:27:11 +0200 Message-ID: References: <2ad73a0410082042be44bb5@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Sender: news Subject: [Qemu-devel] Re: QEMU won't load QCOW images under Windows Reply-To: daimon55@free.fr, 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 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