Debian 12 KVM Windows guest fails to start.

sr_25 · 09-01-2023, 03:13 PM

Booting into Debian 12 with the current kernel vmlinuz-6.1.0-11-amd64 and trying to start a windows guest with Virtual Machine Manager give an error: 'Error starting the domain: the CPU is incompatible with host CPU: Host CPU does not provide required features: hle, rtm.

Code:

Error starting domain: the CPU is incompatible with host CPU: Host CPU does not provide required features: hle, rtm

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1402, in startup
    self._backend.create()
  File "/usr/lib/python3/dist-packages/libvirt.py", line 1373, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: the CPU is incompatible with host CPU: Host CPU does not provide required features: hle, rtm

When I boot with the previous kernel vmlinuz-5.10.0-23-amd64 it works as expected.

How do I go about tracking down the problem?

smallpond · 09-01-2023, 04:37 PM

Try adding the tsx=on kernel command-line parameter. See https://wiki.ubuntu.com/SecurityTeam...AA_MCEPSC_i915

sr_25 · 09-01-2023, 06:02 PM

I tried the tsx=on, and still get the same error. Perhaps I did it wrong:

Code:

sudo dmesg | grep 'Command line'
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-11-amd64 root=UUID=aca026aa-d115-4abc-b781-f598df017918 ro quiet tsx=on

and

Code:

cat /sys/devices/system/cpu/vulnerabilities/tsx_async_abort
Mitigation: TSX disabled

smallpond · 09-02-2023, 06:55 AM

Looks like tsx alone isn't enough, but I'm confused about what the msr shows for the combinations. See https://docs.kernel.org/admin-guide/...ync_abort.html

pan64 · 09-02-2023, 07:50 AM

I found this: https://bugzilla.redhat.com/show_bug.cgi?id=1182650
I don't really know if you find something useful in it, but probably yes. It looks like it is an extremely old issue, should have been solved already.

only-connect · 09-02-2023, 03:20 PM

Quote:

Originally Posted by sr_25

When I boot with the previous kernel vmlinuz-5.10.0-23-amd64 it works as expected.
How do I go about tracking down the problem?

[/QUOTE]

KVM is Red Hat. It's not Debian.
Red Hat is a profit-making company.
If you want a virtual machine on Linux - it's not KVM (Red Hat). I tried.
You need to use a different VM.

smallpond · 09-04-2023, 09:18 AM

Quote:

KVM is Red Hat. It's not Debian.
Red Hat is a profit-making company.
If you want a virtual machine on Linux - it's not KVM (Red Hat). I tried.
You need to use a different VM.

qemu/kvm is available on every distro.

sr_25 · 09-04-2023, 11:17 AM

I ended up removing intel-microcode, and setting the CPU to host-passthrough in VMM. Everything works as expected. Now all I have to install the previous microcode.

only-connect · 09-17-2023, 12:53 PM

Quote:

Originally Posted by smallpond

qemu/kvm is available on every distro.

Have you installed qemu or kvm?
Do you know how easy it is to use as a free virtual machine?