From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IRBia-00074q-8D
	for qemu-devel@nongnu.org; Fri, 31 Aug 2007 14:59:44 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IRBiX-000741-L0
	for qemu-devel@nongnu.org; Fri, 31 Aug 2007 14:59:42 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IRBiX-00073x-He
	for qemu-devel@nongnu.org; Fri, 31 Aug 2007 14:59:41 -0400
Received: from ebox1.ebox.com ([64.7.141.6] helo=ebox1b.ebox.com)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <cfriedt@visible-assets.com>) id 1IRBiX-0001xI-37
	for qemu-devel@nongnu.org; Fri, 31 Aug 2007 14:59:41 -0400
Received: from [192.168.0.117] (unknown [142.46.150.157])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by ebox1b.ebox.com (Postfix) with ESMTP id 463B517DFDE
	for <qemu-devel@nongnu.org>; Fri, 31 Aug 2007 14:59:32 -0400 (EDT)
Message-ID: <46D8675F.1050300@visible-assets.com>
Date: Fri, 31 Aug 2007 15:09:19 -0400
From: Christopher Friedt <cfriedt@visible-assets.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] disk images & driver geometry
References: <46BB7C30.3050007@visible-assets.com>
	<46BB7E37.7050609@codemonkey.ws>
In-Reply-To: <46BB7E37.7050609@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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

Anthony Liguori wrote:
> I have no idea what you're talking about.  QEMU doesn't care whether you 
> use a physical disk or a file.  It handles geometry the same way.
> 
> Is there a concrete example that doesn't work that you think should?

Yes, a simple example is running CentOS after a typical install from a 
hard disk image.

If Qemu is started with the installation cdrom (-cdrom CentOS-1of4*.iso) 
the installation creates several partitions on the virtual disk, 
including /boot, and a logical disk containing /. The first 512 Bytes of 
the disk image are assumed to be the MBR of the disk, which is where the 
installation will write the boot loader.

After installation, qemu is started with

qemu -hda centos.img -boot c

and it hangs after saying 'booting from hard disk'

If anyone knows a way to work around this, please don't hesitate to 
offer a suggestion.

~/Chris