On 2016-08-08 8:04 AM, Prof. Dr. Michael Schefczyk wrote:
The error message shown is "0xC1900101 - 0x20017 The installation failed in the SAFE_OS phase with an error during BOOT operation." Searching for that, one ends up with BIOS issues and problems around wireless and Bluetooth drivers. This is either not applicable for a KVM guest (wireless, Bluetooth) or not really accessible (BIOS). Beyond that, I was not able to detect meaningful errors in the Windows eventviewer.
I'm having the same problem. Linux 4.4.0 (Ubuntu xenial), qemu 2.5, the KVM guest is configured pc-q35, virtio-scsi, virtio-net, CPU is host-model (w/ libvirt) all Hyper-V enlightenments are enabled:
/usr/bin/qemu-system-x86_64 -name arwan-20150704 -S -machine pc-q35-2.2,accel=kvm,usb=off -cpu Haswell,+abm,+pdpe1gb,+rdrand,+f16c,+osxsave,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1000 -m 8192 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 7c2fc02d-2798-4fc9-ad04-db5f1af92723 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-arwan-20150704/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x1d.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x1d -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x1d.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x1d.0x2 -device nec-usb-xhci,id=usb1,bus=pci.2,addr=0x4 -device virtio-scsi-pci,id=scsi0,bus=pci.2,addr=0x6 -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x5 -drive file=/dev/mapper/crypt-arwan-20150704,format=raw,if=none,id=drive-scsi0-0-0-0,cache=none,discard=unmap,aio=native -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 -drive file=/var/lib/libvirt/media/Windows.iso,format=raw,if=none,media=cdrom,id=drive-sata0-0-2,readonly=on -device ide-cd,bus=ide.2,drive=drive-sata0-0-2,id=sata0-0-2,bootindex=1 -netdev tap,fds=29:34:36:37,id=hostnet0,vhost=on,vhostfds=38:39:40:41 -device virtio-net-pci,mq=on,vectors=10,netdev=hostnet0,id=net0,mac=52:54:00:f3:6b:c4,bus=pci.2,addr=0x2 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-arwan-20150704/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -vnc 127.0.0.1:4 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x1 -msg timestamp=on
I'm wondering if it's maybe a CPU microcode update? Are you also using host-model for CPU? I'm seeing a black screen when the update initiates.
Regards.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
