From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KDc9j-0004Be-Fh for qemu-devel@nongnu.org; Tue, 01 Jul 2008 05:28:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KDc9h-0004BE-OU for qemu-devel@nongnu.org; Tue, 01 Jul 2008 05:28:10 -0400 Received: from [199.232.76.173] (port=60152 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KDc9h-0004Az-Gx for qemu-devel@nongnu.org; Tue, 01 Jul 2008 05:28:09 -0400 Received: from ra.siriusit.co.uk ([217.207.197.130]:53725) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KDc9g-0002T5-CC for qemu-devel@nongnu.org; Tue, 01 Jul 2008 05:28:09 -0400 Received: from [192.168.1.83] ([192.168.1.83]) by ra.siriusit.co.uk (8.13.3/8.13.3) with ESMTP id m619bD21010122 for ; Tue, 1 Jul 2008 10:37:14 +0100 Message-ID: <4869F954.6000406@siriusit.co.uk> Date: Tue, 01 Jul 2008 10:31:00 +0100 From: Mark Cave-Ayland MIME-Version: 1.0 Subject: Re: [Qemu-devel] "A disk read error occurred" References: <478c82f00806281242q52a7fa55qcd458c9915e0c5a7@mail.gmail.com> <4867061B.2090309@qumranet.com> <20080630230542.GD20187@shareable.org> <4869F2D8.9020504@siriusit.co.uk> <20080701090815.GA564@shareable.org> In-Reply-To: <20080701090815.GA564@shareable.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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Jamie Lokier wrote: > Yes, very similar, except I saw the problem _without_ migrating > anything. Windows 2000 was installed _inside_ QEMU (with no special > -hdachs setting) from its CD installer. It couldn't boot its own > install after restarting QEMU. > > I looked at the partition with fdisk, then copied the c,h,s values to > -hdachs... > > ...and QEMU said the values were out of range and refused to start! > > So I guessed some values which were not what fdisk reported, and it > worked and booted fine. Yeah, I went through exactly the same process with -hdachs myself :) If you still have the broken image around, it would be interesting to compare the CHS settings between the MBR and VBR on your QEMU-installed copy to see what values you were getting... ATB, Mark. -- Mark Cave-Ayland Sirius Corporation - The Open Source Experts http://www.siriusit.co.uk T: +44 870 608 0063