From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: xp guest, blue screen c0000221 on boot Date: Wed, 28 Oct 2009 17:32:11 +0200 Message-ID: <4AE863FB.803@redhat.com> References: <4AE6100F.6040705@memphis.edu> <4AE6BE76.2010503@redhat.com> <4AE862E9.9000701@memphis.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Andrew Olney Return-path: Received: from mx1.redhat.com ([209.132.183.28]:26224 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753899AbZJ1PcN (ORCPT ); Wed, 28 Oct 2009 11:32:13 -0400 In-Reply-To: <4AE862E9.9000701@memphis.edu> Sender: kvm-owner@vger.kernel.org List-ID: 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? -- error compiling committee.c: too many arguments to function