From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HqpBt-0000TK-8m
	for qemu-devel@nongnu.org; Wed, 23 May 2007 07:39:41 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HqpBr-0000SI-PM
	for qemu-devel@nongnu.org; Wed, 23 May 2007 07:39:40 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HqpBr-0000SE-Mj
	for qemu-devel@nongnu.org; Wed, 23 May 2007 07:39:39 -0400
Received: from wx-out-0506.google.com ([66.249.82.226])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kaiven.long@gmail.com>) id 1HqpBr-0003ZM-5N
	for qemu-devel@nongnu.org; Wed, 23 May 2007 07:39:39 -0400
Received: by wx-out-0506.google.com with SMTP id t15so152769wxc
	for <qemu-devel@nongnu.org>; Wed, 23 May 2007 04:39:38 -0700 (PDT)
Message-ID: <8770b6af0705230439x6e932f79qf5398fea3017e3d4@mail.gmail.com>
Date: Wed, 23 May 2007 19:39:38 +0800
From: "kaiven long" <kaiven.long@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_97938_33292228.1179920378465"
Subject: [Qemu-devel] problem with qemu-img to create boot disk
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

------=_Part_97938_33292228.1179920378465
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,folks
     I am using QEMU to debug Linux Kernel. And a boot disk is create
through qemu-img. It can cannot be booted with other built kernel. The
process is as the following show:
    create disk image like this:
           qemu-img create -f raw rootdisk.img 8G
    install redhat EL4 U4:
           qemu -boot d -cdrom rhel4u4-disc1.img -hda rootdisk.img
    during installation:
           /dev/hda1 ---> /boot ext2
           /dev/hda2 ----->/       ext2
           /dev/hda3------>    swap
    after the installation, file rootdisk.img, it shows:
           rootdisk.img:      x86 boot sector, code offset 0x48
     it can work like this:
           qemu rootdisk.img
     enter the system:fdisk -l, it shows that
         Partition table entries are not in disk order

     it also panics with other new built kernel like:
      qemu -kernel bzImage -hda rootdisk.img
     but the same kernel can work with the disk image down from qemu's
website:
      qemu -kernel bzImage -hda linux-0.2.img
      The only difference between rootdisk.img and linux-0.2.img is their
file atrributes as the following:
       rootdisk.img:      x86 boot sector, code offset 0x48
       linux-0.2.img:      x86 boot sector

       pls help check the above process. I will appreciate that anyone
points the potential errors.
      thank you~

best wishes,
kaiven

------=_Part_97938_33292228.1179920378465
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hi,folks</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; I am using QEMU to debug Linux Kernel. And a boot disk is create through qemu-img. It can cannot be booted with other built kernel. The process is as the following show:</div>
<div>&nbsp;&nbsp;&nbsp; create disk image like this:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; qemu-img create -f raw rootdisk.img 8G</div>
<div>&nbsp;&nbsp;&nbsp; install redhat EL4 U4:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; qemu -boot d -cdrom rhel4u4-disc1.img -hda rootdisk.img</div>
<div>&nbsp;&nbsp;&nbsp; during installation:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /dev/hda1 ---&gt; /boot ext2</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /dev/hda2 -----&gt;/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ext2</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /dev/hda3------&gt;&nbsp;&nbsp;&nbsp; swap</div>
<div>&nbsp;&nbsp;&nbsp; after the installation, file rootdisk.img, it shows:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;rootdisk.img:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x86 boot sector, code offset 0x48</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; it can work like this:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; qemu rootdisk.img</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; enter the system:fdisk -l, it shows that</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Partition table entries are not in disk order</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; it also panics with other new built kernel like:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; qemu -kernel bzImage -hda rootdisk.img</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; but the same kernel can work with the disk image down from qemu&#39;s website:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; qemu -kernel bzImage -hda linux-0.2.img</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The only difference&nbsp;between rootdisk.img and linux-0.2.img is their file atrributes as the following:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rootdisk.img:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x86 boot sector, code offset 0x48</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; linux-0.2.img:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x86 boot sector</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pls help check the above process. I will appreciate that anyone points the potential errors.</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; thank you~</div>
<div>&nbsp;</div>
<div>best wishes,</div>
<div>kaiven</div>
<div>&nbsp;</div>
<div>&nbsp; </div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp; <br>&nbsp;</div>

------=_Part_97938_33292228.1179920378465--