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.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
