September 11, 20178 yr Hello, I set up a new VM and configured a Windows 10 ISO downloaded from Microsoft as the boot CD device. When the VM boots, I have the ability to press any key to get the CD to boot, and then the blue windows logo shows, but then the boot sequence halts there and I don't see a progress indicator, and the screen sticks on the windows logo. I get this result whether I use a VNC GPU or a passthrough device. This VM does not have a virtual hard drive defined because I'm passing through an NVMe device for direct storage access. The log shows the following output: 2017-09-11 20:05:05.888+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.1, hostname: unRAIDLC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 10/master-key.aes' -machine pc-i440fx-2.7,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/04d899b6-eae2-27b9-cbe4-d403629438d9_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 62464 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid 04d899b6-eae2-27b9-cbe4-d403629438d9 -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ichlport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x4 -device vfio-pci,host=01:00.1,id=hostdev1,bus=pci.0,addr=0x5 -device vfio-pci,host=07:00.0,id=hostdev2,bus=pci.0,addr=0x6 -device usb-host,hostbus=1,hostaddr=4,id=hostdev3,bus=usb.0,port=1 -device usb-host,hostbus=1,hostaddr=5,id=hostdev4,bus=usb.0,port=2 -device usb-host,hostbus=1,hostaddr=3,id=hostdev5,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=onDomain id=1 is tainted: high-privilegesDomain id=1 is tainted: host-cpuchar device redirected to /dev/pts/0 (label charserial0) Any ideas?
September 11, 20178 yr Author Actually, after ignoring it for several minutes, it did eventually boot to the CD drive. However, after running the install to the NVMe drive, the VM will not boot and just shows the BIOS prompt. Now what?
Archived
This topic is now archived and is closed to further replies.