Jump to content

VM failing to start


bobbintb

Recommended Posts

I followed the wiki to virtualize my existing PC and I am getting an error trying to start it:

 

internal error: process exited while connecting to monitor: 2016-04-18T19:22:58.387426Z qemu-system-x86_64: -device vfio-pci,host=06:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver.
2016-04-18T19:22:58.387445Z qemu-system-x86_64: -device vfio-pci,host=06:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to get group 1
2016-04-18T19:22:58.387452Z qemu-system-x86_64: -device vfio-pci,host=06:00.0,id=hostdev0,bus=pci.0,addr=0x6: Device initialization failed

 

I dug around on the forum for similar issues. I tried to use an absolute path and not a disk share. Didn't work. I looked at my iommu_group setting but don't know what do make of it. Any ideas?

Link to comment

I forgot to mention, I did read that but my video card shows up under PCI devices, so I'm not sure if that's the issue. That and my error was a little different than the post I was looking at that mentioned that. I'm not at home to try the override settings but I'll post with the results. Thanks.

Link to comment

Ok, well, VM is started now but now what? How do I view it? Nothing is on the monitor connected to the server. What am I missing? Might there be a GPU issue? My video card is GeForce GTX 560 and I have it set to passthru.

 

Here's my VM log:

 

2016-04-18 22:31:53.935+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 10' -S -machine pc-i440fx-2.5,accel=kvm,usb=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/47c8ec03-299d-f758-3c59-34787ad51a2e_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2048 -realtime mlock=on -smp 1,sockets=1,cores=1,threads=1 -uuid 47c8ec03-299d-f758-3c59-34787ad51a2e -nographic -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,mastrg.qemu.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=06:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
Domain id=1 is tainted: high-privileges
Domain id=1 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)

Link to comment

VNC is built in under the vm menu (where you start, stop, edit etc). It's the topmost entey and clicking on it will invoke a connection via vnc to your vm.

 

Sent from my LG-D855 using Tapatalk

 

I have no such option in my menu. I'm not sure why.

 

EDIT: Ah, nevermind. I Figured that part out.

 

Capture.PNG.8eae4f9fded6f2d3d9dbf4ca205d2d7f.PNG

Link to comment

The VNC output shows this:

 

switch your VM install from OVMF to SeaBios perhaps?

 

I thought about that but how do I do it? The VM is stopped but the option to change is greyed out.

You can't change it without creating a new VM

 

Yes, I figured that out eventually. Thank you everyone.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...