@olivierlambert said in Windows 10 VM reboots when starting software:

If it's MSR related, you should see xl dmesg output when the VM crashes.

This is output from xl dmesg when machine crashes:

(XEN) [57920.851786] d10v1 Unknown Host LBR MSRs
(XEN) [57920.851789] domain_crash called from vmx.c#vmx_msr_write_intercept+0x4c2/0x510
(XEN) [57920.851790] Domain 10 (vcpu#1) crashed on cpu#8:
(XEN) [57920.851791] ----[ Xen-4.13.0-8.6.1.xcpng8.1  x86_64  debug=n   Not tainted ]----
(XEN) [57920.851792] CPU:    8
(XEN) [57920.851793] RIP:    0010:[<fffff8014a7de482>]
(XEN) [57920.851794] RFLAGS: 0000000000040002   CONTEXT: hvm guest (d10v1)
(XEN) [57920.851795] rax: 0000000000000001   rbx: 0000000000000000   rcx: 00000000000001d9
(XEN) [57920.851796] rdx: 0000000000000000   rsi: 0000000000000000   rdi: 00000000000000f0
(XEN) [57920.851797] rbp: fffff68839bd7b00   rsp: fffff68839bd7a78   r8:  0000000000000001
(XEN) [57920.851798] r9:  fffff68839bd75f8   r10: 0000000000000000   r11: ffffd50f3594a080
(XEN) [57920.851799] r12: 0000000002a4b528   r13: 00007ff907ec4900   r14: 00000000000000f0
(XEN) [57920.851799] r15: 0000000000000000   cr0: 0000000080050033   cr4: 0000000000370678
(XEN) [57920.851800] cr3: 0000000061fa4002   cr2: 000000000027425a
(XEN) [57920.851801] fsb: 0000000000000000   gsb: ffffb980e01d1000   gss: ffffb980e01d1000
(XEN) [57920.851802] ds: 002b   es: 002b   fs: 0053   gs: 002b   ss: 0018   cs: 0010

I installed a Windows 10 Home VM on XCP-ng 8.1. I'm going to use it for BlueIris NVR application.
Software is installed and all looks good, but when I start the application the VM just stops or reboots. No apparent messages in EventLog.

Googling for the same issue I see that other people had similar issues using Proxmox/KVM/QUEMU.
Solution seems to be to add the following to /etc/modprobe.d/kvm.conf:
options kvm ignore_msrs=1
I did try this on XCP-ng but no change.
Is there are similar setting for XCP-ng? To ignore MSRs or not to passthrough CPU features from the host?