From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GquOV-0006zX-9S for qemu-devel@nongnu.org; Sun, 03 Dec 2006 11:40:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GquOT-0006yp-KL for qemu-devel@nongnu.org; Sun, 03 Dec 2006 11:40:46 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GquOT-0006yj-F5 for qemu-devel@nongnu.org; Sun, 03 Dec 2006 11:40:45 -0500 Received: from [66.249.82.239] (helo=wx-out-0506.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GquOS-0005HU-MS for qemu-devel@nongnu.org; Sun, 03 Dec 2006 11:40:44 -0500 Received: by wx-out-0506.google.com with SMTP id i30so5193508wxd for ; Sun, 03 Dec 2006 08:40:43 -0800 (PST) Message-ID: From: "Mike Smith" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_21686_5588135.1165164043246" Subject: [Qemu-devel] Bug report Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Sun, 03 Dec 2006 16:40:47 -0000 To: qemu-devel@nongnu.org ------=_Part_21686_5588135.1165164043246 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I was running Windows 2000 Pro in QEMU (FreeBSD as host) and needed more disk space. So I created a spare hard drive with this command: $ qemu-img create -f qcow hd2.img 3GB And then I started QEMU again like this: qemu -hda hd.img -hdb hd2.img -cdrom scrap1.iso -kernel-kqemu (hd.img already had Windows installed on it, so I left it there.) But I went to control panel > administrative tools > disk management and right-clicked the empty hard drive to make a new partition, I got this: EAX=bf3a77dc EBX=bf3a7ac0 ECX=bf3a7588 EDX=00000000 ESI=00000000 EDI=00000100 EBP=bf3a77c4 ESP=bf3a7514 EIP=a0086b2b EFL=00010246 [---Z-P-] CPL=3 II=0 A20=1 SMM=0 HLT=0 ES =0023 00000000 ffffffff 00cff300 CS =0008 00000000 ffffffff 00cffb00 SS =0010 00000000 ffffffff 00cff300 DS =0023 00000000 ffffffff 00cff300 FS =003b 7ffde000 00000fff 7f40f3fd GS =0000 00000000 00000000 00000000 LDT=0000 00000000 00000000 00008000 TR =0028 8066b000 000020ab 80008966 GDT= 80036000 000003ff IDT= 80036400 000007ff CR0=e001003b CR2=000b9005 CR3=060e1000 CR4=00000690 Unsupported return value: 0xffffffff And QEMU just closed. I'm not sure if this is a QEMU bug, a FreeBSD bug, or a Windows bug, but I guess it's worth reporting here anyway. P.S. I just tried it with -no-kqemu and it worked fine. So I think it's a kqemu bug. I can't find a kqemu bug reporting place, so I guess this is the next best place to report it. ------=_Part_21686_5588135.1165164043246 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I was running Windows 2000 Pro in QEMU (FreeBSD as host) and needed more disk space. So I created a spare hard drive with this command:
$ qemu-img create -f qcow hd2.img 3GB


And then I started QEMU again like this:
qemu -hda hd.img -hdb hd2.img -cdrom scrap1.iso -kernel-kqemu
(hd.img already had Windows installed on it, so I left it there.)

But I went to control panel > administrative tools > disk management and right-clicked the empty hard drive to make a new partition, I got this:
EAX=bf3a77dc EBX=bf3a7ac0 ECX=bf3a7588 EDX=00000000
ESI=00000000 EDI=00000100 EBP=bf3a77c4 ESP=bf3a7514
EIP=a0086b2b EFL=00010246 [---Z-P-] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =0023 00000000 ffffffff 00cff300
CS =0008 00000000 ffffffff 00cffb00
SS =0010 00000000 ffffffff 00cff300
DS =0023 00000000 ffffffff 00cff300
FS =003b 7ffde000 00000fff 7f40f3fd
GS =0000 00000000 00000000 00000000
LDT=0000 00000000 00000000 00008000
TR =0028 8066b000 000020ab 80008966
GDT=     80036000 000003ff
IDT=     80036400 000007ff
CR0=e001003b CR2=000b9005 CR3=060e1000 CR4=00000690
Unsupported return value: 0xffffffff

And QEMU just closed. I'm not sure if this is a QEMU bug, a FreeBSD bug, or a Windows bug, but I guess it's worth reporting here anyway.

P.S. I just tried it with -no-kqemu and it worked fine. So I think it's a kqemu bug. I can't find a kqemu bug reporting place, so I guess this is the next best place to report it.
------=_Part_21686_5588135.1165164043246--