From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1ENITj-00037g-DF
	for qemu-devel@nongnu.org; Wed, 05 Oct 2005 19:15:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1ENITg-00036j-Oi
	for qemu-devel@nongnu.org; Wed, 05 Oct 2005 19:15:14 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1ENITg-00035y-C2
	for qemu-devel@nongnu.org; Wed, 05 Oct 2005 19:15:12 -0400
Received: from [207.65.58.204] (helo=darkstar.shires.org)
	by monty-python.gnu.org with esmtp
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1ENITg-00014e-1j
	for qemu-devel@nongnu.org; Wed, 05 Oct 2005 19:15:12 -0400
Received: from [207.65.58.205] (sabra.shires.org [207.65.58.205] (may be
	forged))
	by darkstar.shires.org (8.12.11/8.12.11) with ESMTP id j95NF9aP034337
	for <qemu-devel@nongnu.org>; Wed, 5 Oct 2005 18:15:09 -0500 (CDT)
	(envelope-from mare@shires.org)
Message-ID: <43445E7D.2090803@shires.org>
Date: Wed, 05 Oct 2005 18:15:09 -0500
From: Brett Henley <mare@shires.org>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] harddrives and QEMU
References: <434419E9.7070800@shires.org>
	<20051005213402.GA24303@jbrown.mylinuxbox.org>
In-Reply-To: <20051005213402.GA24303@jbrown.mylinuxbox.org>
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

Jim C. Brown wrote:

>On Wed, Oct 05, 2005 at 01:22:33PM -0500, Brett (Mare) Henley wrote:
>  
>
>>  The Longer one goes into greater detail. WaxDragon's first suggestion 
>>was to use -hdachs to define the drive for the bios. I had to read up 
>>well to do this but entered 65383,16,63 as my definition and still ended 
>>up with exactly the same behavior.
>>    
>>
>
>-hdachs doesn't make a difference, unless the OS reads the size of the
>hard disk from the bios.
>
>If it gets its size from the MBR or partition table, it won't help at all.
>
>There is probably a way to force freebsd into using a certain size or c/h/s
>value for the hard disk. I recommend trying this to see if its just the bad
>disk size thats causing problems.
>
>  
>
Alright, but here's the rub. If a drive can be booted by a machine. Why 
can't it boot from Qemu if it's accessing the raw disk via the windows 
interface? This needs no messing with bios or disksize to boot of a 
regular machine.