From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Olney Subject: Re: xp guest, blue screen c0000221 on boot Date: Tue, 3 Nov 2009 18:18:46 -0600 Message-ID: <4AF0C866.3000401@memphis.edu> References: <4AE6100F.6040705@memphis.edu> <4AE6BE76.2010503@redhat.com> <4AE862E9.9000701@memphis.edu> <4AE863FB.803@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Avi Kivity Return-path: Received: from itmx2.memphis.edu ([141.225.112.71]:43511 "EHLO itmta2.memphis.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753379AbZKDASn (ORCPT ); Tue, 3 Nov 2009 19:18:43 -0500 Received: from itexfe7.uom.memphis.edu (itexfe7.memphis.edu [10.15.1.68]) by itmta2.memphis.edu (Postfix) with ESMTP id 249C8A0C05A for ; Tue, 3 Nov 2009 18:18:48 -0600 (CST) In-Reply-To: <4AE863FB.803@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Thanks for the suggestion. I've successfully installed on a new qcow2 image. Strangely all of my xp raw images no longer work. That makes me think that this is more than just a corrupt image. I've been using kvm for several years with raw images, so I don't think the BIOS could be a factor either. If there's a way to get my raw images to work, that would be nice. I'm trying to convert one of the raw images to qcow2 -- perhaps that will work. Avi Kivity wrote: > On 10/28/2009 05:27 PM, Andrew Olney wrote: >> Thanks. In pursuing this suggestion I discovered that I also can't >> make new XP VMs. Setup fails with "the disk may be damaged". >> >> The image was created with >> >> qemu-img create xp_new.img 13G >> >> And the setup command is >> >> kvm -cdrom xp/xp_pro.iso -hda xp_new.img -boot d -m 512 -no-acpi -usb >> -usbdevice tablet > > What happens if you use a new qcow2 disk? Does it fail in the same way? >