From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CTp3R-0005y3-08 for qemu-devel@nongnu.org; Mon, 15 Nov 2004 17:10:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CTp3Q-0005xr-JH for qemu-devel@nongnu.org; Mon, 15 Nov 2004 17:10:32 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CTp3Q-0005xo-Cz for qemu-devel@nongnu.org; Mon, 15 Nov 2004 17:10:32 -0500 Received: from [64.233.170.196] (helo=rproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CTouP-0007Yt-2r for qemu-devel@nongnu.org; Mon, 15 Nov 2004 17:01:13 -0500 Received: by rproxy.gmail.com with SMTP id y7so189428rne for ; Mon, 15 Nov 2004 14:01:09 -0800 (PST) Message-ID: <41e41e7a041115140120b83bf8@mail.gmail.com> Date: Tue, 16 Nov 2004 00:01:09 +0200 From: Hetz Ben Hamo Subject: Re: [Qemu-devel] whats up with QEMU and virtual disks? In-Reply-To: <4199223E.3040300@railnet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41e41e7a04111513146259739a@mail.gmail.com> <4199223E.3040300@railnet.it> Reply-To: Hetz Ben Hamo , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org > > 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 or * Provide a simple script to convert from the old to new format? 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? Thanks, Hetz