Hey guys!

 

Absolute unRAID newbie here.

 

I'm having trouble setting up a Windows VM. I got an Arch Linux VM running and can't identify the problem. I try to start the setup, the CPU usage goes up, something starts, the screen stays black and nothing happens. After a few seconds CPU usage goes back to 0. I tried several settings from Youtube videos and guides but nothing seems to work. 

 

I attached the Tower Diagnostics and here is the log of the VMs.

 

Arch:

2018-03-25 22:03:39.271+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: Tower
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=Arch,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-7-Arch/master-key.aes -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -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/313169d2-6fc5-ae6f-b233-4e06df4dd18b_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid 313169d2-6fc5-ae6f-b233-4e06df4dd18b -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-Arch/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x7 -device ahci,id=,bus=pci.0,addr=0x8 -device usb-host,hostbus=3,hostaddr=5,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=3,hostaddr=4,id=hostdev3,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on
2018-03-25 22:03:39.271+0000: Domain id=7 is tainted: high-privileges
2018-03-25 22:03:39.271+0000: Domain id=7 is tainted: host-cpu
2018-03-25T22:03:39.316318Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)

Windows:

2018-03-25 20:46:18.787+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: Tower
LC_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-4-Windows 10/master-key.aes' -machine pc-i440fx-2.11,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/ce1b59b8-01ee-e2d7-ade6-f0b2c8ad89de_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 7,sockets=1,cores=7,threads=1 -uuid ce1b59b8-01ee-e2d7-ade6-f0b2c8ad89de -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-4-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device qem0,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=0x5 -device vfio-pci,host=01:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=3,hostaddr=5,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=3,hostaddr=4,id=hostdev3,bus=usb.0,port=2 -device usb-host,hostbus=3,hostaddr=3,id=hostdev4,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
2018-03-25 20:46:18.787+0000: Domain id=4 is tainted: high-privileges
2018-03-25 20:46:18.787+0000: Domain id=4 is tainted: host-cpu
2018-03-25T20:46:18.835505Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
2018-03-25T20:47:27.687340Z qemu-system-x86_64: terminating on signal 15 from pid 5135 (/usr/sbin/libvirtd)
2018-03-25 20:47:29.288+0000: shutting down, reason=destroyed

 

I hope I'm just overlooking something. Thanks in advance!

tower-diagnostics-20180325-1527.zip

Edited March 25, 20188 yr by Snow

Not sure if this has anything to do with it:

Mar 25 14:28:05 Tower kernel: vfio-pci 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

Try to pass a graphics ROM BIOS and the "... expecting 0xaa55, got 0xffff" error should disappear. Also try to start the VM installation after shutting down and powering up the server, to see if it makes a difference...

Edited March 26, 20188 yr by thomas