I've compiled sys-kernel/gentoo-sources-6.2.0 today. I'm now getting the following error when trying to start an Arch Linux guest on Virt Manager: Error starting domain: internal error: qemu unexpectedly closed the monitor: 2023-02-20T17:18:30.520219Z qemu-system-x86_64: System Management Mode not supported by this hypervisor. 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.10/site-packages/libvirt.py", line 1373, in create raise libvirtError('virDomainCreate() failed') libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 2023-02-20T17:18:30.520219Z qemu-system-x86_64: System Management Mode not supported by this hypervisor. I also have a Windows 10 guest VM which starts just fine. I don't have the issue described above if booted with kernel 6.1.12. Reproducible: Always Steps to Reproduce: 1. Boot from 6.2.0 kernel 2. Try to start an existing Arch Linux guest VM Actual Results: The error mentioned appear and the VM doesn't start Expected Results: The error mentioned doesn't appear and the VM starts normally
Created attachment 853338 [details] emerge --info
Created attachment 853340 [details] Arch Linux VM properties
Updating to sys-kernel/linux-headers-6.2 didn't make any difference. On the same host machine using Arch Linux, I updated to 6.2.arch1-1 kernel and the guest VM works just fine.
(In reply to ut2s7kol87 from comment #0) > libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: > 2023-02-20T17:18:30.520219Z qemu-system-x86_64: System Management Mode not > supported by this hypervisor. > > It's dying in https://github.com/qemu/qemu/blob/v7.2.0/hw/i386/x86.c#L1238. We don't build with TCG right now in Gentoo because of the number of bugs with it (although maybe we should revisit that). I assume your kernel definitely supports KVM. > I don't have the issue described above if booted with kernel 6.1.12. Oh, I missed this bit. Let me see what Arch does with their kernel.
I assume you're using equivalent kernel configs on both? gentoo-sources could obviously be any configuration you like.
Arch doesn't seem to have any patches for their kernel so this sounds entirely in the config diff.
(In reply to Sam James from comment #5) > I assume you're using equivalent kernel configs on both? gentoo-sources > could obviously be any configuration you like. Yes, apart from the new 6.2 options of course. (In reply to Sam James from comment #6) > Arch doesn't seem to have any patches for their kernel so this sounds > entirely in the config diff. OK, thanks. I'll try compiling sys-kernel/gentoo-sources-6.2.0 kernel with my config file from 6.1.12 one more time. I'll pay more attention to the new options when running make oldconfig this time around.
Indeed, I missed enabling CONFIG_KVM_SMM: Virtualization (VIRTUALIZATION) [Y/n/?] y Kernel-based Virtual Machine (KVM) support (KVM) [Y/n/m/?] y KVM for Intel (and compatible) processors support (KVM_INTEL) [M/n/y/?] m Software Guard eXtensions (SGX) Virtualization (X86_SGX_KVM) [N/y/?] n KVM for AMD processors support (KVM_AMD) [N/m/y/?] n System Management Mode emulation (KVM_SMM) [Y/n/?] (NEW) y All good now after recompiling a 6.2.0 kernel with this option enabled. Sorry for the false report.
