spants Posted April 28, 2016 Share Posted April 28, 2016 I have been using and writing a lot of Docker images and thought that I would take a look at VMs. However, none will start: LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 7' -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 -m 2048 -realtime mlock=off -smp 2,sockets=1,cores=1,threads=2 -uuid e8e3ee70-eaa9-e1cd-68e6-14c24d766113 -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 7/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,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 'file=/mnt/cache/.keep/vm/Windows 7/v-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on Domain id=2 is tainted: high-privileges Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) I have tried selecting other CPU cores etc. This seems to be the problem: Domain id=2 is tainted: high-privileges Domain id=2 is tainted: host-cpu argggg: I guess I need IOMMU capability?. No menu to set it... Model: N/A M/B: ASUSTeK Computer INC. - P8Z68-V PRO CPU: Intel® Core™ i7-2600K CPU @ 3.40GHz HVM: Enabled IOMMU: Disabled Cache: 256 kB, 1024 kB, 8192 kB Memory: 16384 MB (max. installable capacity 32 GB) Network: eth0: 1000Mb/s, Full Duplex, mtu 1500 Kernel: Linux 4.4.6-unRAID x86_64 OpenSSL: 1.0.2g Uptime: Quote Link to comment
tim8v Posted April 28, 2016 Share Posted April 28, 2016 have you checked in the BIOS? CPU should be fine. Quote Link to comment
spants Posted April 28, 2016 Author Share Posted April 28, 2016 There is no option to enable iommu in the bios that I can see. HVM is enabled though. Is IOMMU a requirement for VMs? Quote Link to comment
tim8v Posted April 28, 2016 Share Posted April 28, 2016 There is no option to enable iommu in the bios that I can see. HVM is enabled though. Is IOMMU a requirement for VMs? Look for VT-d in the BIOS, i suspect it will be disabled. Just enable it (VT-d is Intel and IOMMU is AMD) Quote Link to comment
spants Posted April 28, 2016 Author Share Posted April 28, 2016 ah ok. vt-d is enabled in the bios.... It must be something else that is causing those errors. I'm on 6.2.0-beta21 Interestingly: http://ark.intel.com/products/52214/Intel-Core-i7-2600K-Processor-8M-Cache-up-to-3_80-GHz says that my processor doesnt have vt-d! Quote Link to comment
tim8v Posted April 28, 2016 Share Posted April 28, 2016 ah ok. vt-d is enabled in the bios.... It must be something else that is causing those errors. I'm on 6.2.0-beta21 Interestingly: http://ark.intel.com/products/52214/Intel-Core-i7-2600K-Processor-8M-Cache-up-to-3_80-GHz says that my processor doesnt have vt-d! ah my bad. assumed it would be ok. Quote Link to comment
TiHKAL Posted April 28, 2016 Share Posted April 28, 2016 I could be wrong but you should still be able to have VM's you just won't be able to pass-through. You will need to use VNC to access them. Quote Link to comment
Guest spants01 Posted April 28, 2016 Share Posted April 28, 2016 That's all I need. I wonder what is causing the error then Quote Link to comment
saarg Posted April 28, 2016 Share Posted April 28, 2016 That's all I need. I wonder what is causing the error then The error you are seeing is not really an error. It's always in the logs. You need to post more info if you want to get a solution. Diagnostic zip and xml is a minimum. Quote Link to comment
spants Posted April 28, 2016 Author Share Posted April 28, 2016 solved - its a problem with Chrome! Firefox seems to work (adblock maybe?) the real vnc wasnt working Quote Link to comment
StarFox10 Posted March 21, 2020 Share Posted March 21, 2020 I understand this is an old thread, but just in case anyone else like me comes across this - it can also be caused when you first start a new VM, and it's attempting to boot off the install ISO. You’ll get a "press any key to boot from CD" prompt, but only for a few seconds, then the boot fails and you get a shell prompt. If you don’t get in to VNC quickly enough, it's easy to miss that "press any key" prompt. Quote Link to comment
67rynorod Posted April 4, 2020 Share Posted April 4, 2020 Just in case anyone else runs into this issue, Safari will not open VNC properly either and you'll get the three horizontal scrolling dots, when in all actuality, your VM is running just fine. As of right now, Chrome (80.0.3987.149) in Catalina 10.15.3/.4 is working. Quote Link to comment
Dallas.toth Posted April 12, 2020 Share Posted April 12, 2020 I had the same issue with Chrome and had to use Edge for the browser Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.