![]() But VF devices are definitely supported (see the Windows docs here for example), and Intel provides drivers for VF instances of their devices for many versions of Windows. But after shutting down the Win10 guest and virsh edit'ing the CPU type to kvm64, it just boot-loops (and this is without having Blue Iris even being installed yet!) Setting the CPU back to Penryn allows the guest to boot again, but trying to start Blue Iris results in the same SYSTEM SERVICE EXCEPTION.Īny ideas? After all this, it will be a bummer if I can't virtualize Blue Iris under KVM!Ĭlick to expand.I understand about needing to meet all the hardware requirements - and my system does. That OS install and update also went fine. I configured another VM with the Penryn CPU type as suggested by VirtualCam above. But as soon as you try to launch Blue Iris 5, the Win10 guest BSODs with a SYSTEM SERVICE EXCEPTION. I'm using the 1909 Win10 ISO, and OS installation went fine. The server is running Ubuntu 18.04, and is mostly Docker containers, but I just configured KVM in order to set up a Windows 10 guest to run Blue Iris. I recently consolidated multiple old, crusty servers into one "real" server (with a Xeon CPU) that will serve as a VM host for everything. Just curious if anybody has made progress on this.
0 Comments
Leave a Reply. |