From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: qemu-kvm-0.14.x regression - windows 2K8 R2 stopped booting Date: Thu, 26 May 2011 15:13:34 +0300 Message-ID: <20110526121334.GO29458@redhat.com> References: <20110526095910.GA2172@nik-comp.lan> <20110526100502.GJ29458@redhat.com> <20110526102056.GB2172@nik-comp.lan> <20110526102237.GK29458@redhat.com> <20110526115035.GC2172@nik-comp.lan> <20110526115440.GM29458@redhat.com> <20110526120357.GD2172@nik-comp.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm To: Nikola Ciprich Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42655 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757369Ab1EZMNh (ORCPT ); Thu, 26 May 2011 08:13:37 -0400 Content-Disposition: inline In-Reply-To: <20110526120357.GD2172@nik-comp.lan> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, May 26, 2011 at 02:03:57PM +0200, Nikola Ciprich wrote: > > This BSOD usually indicates that Windows can't write to the boot disk. > > This is usually happens if qemu has no permission to write to the image > > file. But if you are starting qemu as a root this is probably is not the > OK, I see. May be libvirt does something funny with selinux. > > case. So what is your 0.14 command line? > here it goes: > /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name vmtst04 -uuid 1f8328b8-8849-11e0-91e9-00259009d78c -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmtst04.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=14,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:18:04:00,bus=pci.0,addr=0x3 -usb -vnc 0.0.0.0:24104 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 Try to run with -M pc-0.13. -- Gleb.