Update: So after some digging, it seems this has been reported as an issue many times.
As a workaround, I added the an entry to the kvm.conf in modprobe.d directory of ignore_msrs=1 and that allowed Blue Iris to boot. Would be nice to have an actual fix for this instead of a workaround. Would really like to know why kvm is thing that ia32_debugctl is not a valid cpu option. From: Robert Webb Sent: Saturday, February 8, 2020 10:33 AM To: users <users@ovirt.org> Subject: Win Server 2k19 and BlueIris So I have been running Windows Server 2019 on Proxmox VE with Blue Iris NVR. Tried to migrate the qcow disk over to oVirt, and like other Win2k19 servers, they all give a BSOD with a KMODE error. Last night I installed 2k19 from scratch, installed the latest drivers I could find, oVirt-toolsSetup-4.3-3.el7, and proceeded to load up Blue Iris. As soon as I go to start Blue Iris, the VM hangs, then gives a BSOD with SYSTEM SERVICE EXCEPTION. Looking at the debug log on the ovirt node the VM is running, there one entry that gets created on each crash with, "kvm [4723]: vcpu1 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop". Running on oVirt node 4.3.8, cluster cpu is Intel Westmere IBRS SSBD Family, pc-i440fx-rhel7.6.0, and the physical cpu is 24x Intel(R) Xeon(R) CPU X5670 @ 2.93GHz. Any ideas?
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/B2YJMXYQZVWI4TAX2ZZ4SE55KABQ4NYL/
