From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CU5RX-0007qz-Id for qemu-devel@nongnu.org; Tue, 16 Nov 2004 10:40:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CU5RU-0007pP-Cp for qemu-devel@nongnu.org; Tue, 16 Nov 2004 10:40:28 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CU5RU-0007om-5j for qemu-devel@nongnu.org; Tue, 16 Nov 2004 10:40:28 -0500 Received: from [66.124.73.250] (helo=marvin.brittainweb.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CU5IB-00051P-QA for qemu-devel@nongnu.org; Tue, 16 Nov 2004 10:30:52 -0500 Received: from [10.1.2.102] ([10.1.1.2]) by marvin.brittainweb.org (8.12.8/8.12.8) with ESMTP id iAGFUcjv009413 for ; Tue, 16 Nov 2004 07:30:38 -0800 Message-ID: <419A1A03.9010707@brittainweb.org> Date: Tue, 16 Nov 2004 07:17:23 -0800 From: Jason Brittain MIME-Version: 1.0 Subject: Re: [Qemu-devel] qemu-img documentation References: <41993485.6060704@bellard.org> <41e41e7a041115150417b7468d@mail.gmail.com> <41995BF4.7020102@bellard.org> <4199B04F.8020307@railnet.it> In-Reply-To: <4199B04F.8020307@railnet.it> 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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ML wrote: > --- > Fabrice Bellard said the following on 11/16/2004 02:46 AM: > >> Try my last fix. The important fix is in >> hw/ide.c:ide_guess_geometry(). I think the problem is that after >> reboot when installing ide_guess_geometry() returns an invalid >> geometry because the BIOS translated geometry is stored in the MBR >> instead of the real hard disk geometry. >> >> For the desperate user, I added an option to manually specify the BIOS >> translation mode. > > With this fix now I can boot XP images newly created with 0.6.1 but I > can't boot any longer my older images created with versions < 0.6.1 > unless I specify hda geometry on the command line. This is going to cause lots of people to not be able to figure out how to use qemu anymore after an upgrade. For example, even if I knew that I needed to use the -hdachs option (pronounced "headaches"), how would I know what geometry numbers to give it? I'm not real good with this sort of thing, and I haven't found any docs yet that try to explain it from the perspective of a VM user. I know, I know, you can't have everything. But, I do think this will cause users repeated hdachs. :) -- Jason Brittain