From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1CTq0Y-0003J5-Jv
	for qemu-devel@nongnu.org; Mon, 15 Nov 2004 18:11:38 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1CTq0Y-0003Ix-AD
	for qemu-devel@nongnu.org; Mon, 15 Nov 2004 18:11:38 -0500
Received: from [129.104.30.34] (helo=mx1.polytechnique.org)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1CTprM-0008Ri-22
	for qemu-devel@nongnu.org; Mon, 15 Nov 2004 18:02:08 -0500
Message-ID: <41993578.5030804@bellard.org>
Date: Tue, 16 Nov 2004 00:02:16 +0100
From: Fabrice Bellard <fabrice@bellard.org>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] whats up with QEMU and virtual disks?
References: <41e41e7a04111513146259739a@mail.gmail.com>	
	<4199223E.3040300@railnet.it>
	<41e41e7a041115140120b83bf8@mail.gmail.com>
In-Reply-To: <41e41e7a041115140120b83bf8@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; 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

Hetz Ben Hamo wrote:
>>>in both cases, the only way to bypass this problem is by using the
>>>-hdachs parameter..
>>>Why? what has changed that broke the normal behavior? how can it be fixed?
>>
>>My quick and dirty fix of commenting out the call to bdrv_set_geometry_hint in
>>line 1898 of hw/ide.c doesn't appear to work anymore with the disk image newly
>>created with the 0.6.1 version.
>>However my older disk images, created with previous versions of Qemu, don't
>>work with 0.6.1 (it says that NTLDR is missing) but, if I comment out the line
>>as per above, everything goes back to normal behavior.
> 
> 
> I see...
> 
> Fabrice, since this change breaks compatibility, is there a way to either:
> 
> * Add a parameter to load "old" images with the old bdrv_set_geometry_hint 

No one gave precise enough information to fix the problem. The problem 
is related to the default Bochs BIOS tranlation mode, and I would like 
to understand first before doing a fix.

> * Provide a simple script to convert from the old to new format?

If it is the only solution, I can do it, but there may be a better one.

> One more thing Fabrice, regarding the message about the RTC. Could you
> detect if the user is running 2.6.x kernel and if so, avoid showing
> the RTC message please?

I'll try.

Fabrice.