https://bugzilla.suse.com/show_bug.cgi?id=1216463 https://bugzilla.suse.com/show_bug.cgi?id=1216463#c10 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kallan@suse.com --- Comment #10 from James Fehlig <jfehlig@suse.com> --- (In reply to ell1e from comment #9)

virt-manager launches and works fine without root here, which is the part that worries me. I assume to create HW accelerated VMs it should normally require some sort of elevation?

A normal user should be able to start a kvm-accelerated VM, but it will have limited privileges and functionality. See some of the links I referenced in #5. BTW, I'm not sure if vTPM works with an unprivileged VM. It's clear the type of VM you are trying to create does not work unprivileged. From your virt-manager log, I see it's unable to connect to the system daemon: [Wed, 01 Nov 2023 20:55:01 virt-manager 5426] DEBUG (engine:180) Autostart connection error: Unable to connect to libvirt qemu:///system. Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory Libvirt URI is: qemu:///system I think the socket path is a little misleading. Perhaps virt-manager is only reporting the last one it tried. On Leap 15.5, the monolithic libvirtd is still the "preferred" deployment, so the path should be /var/run/libvirt/libvirt-sock. But that's a cosmetic detail. Do you have the libvirtd service enabled? E.g. is it shown as enabled and running in the output of 'systemctl status libvirtd.service'? If not, enable and start it (systemctl enable libvirtd.service && systemctl start libvirtd.service), then see if you can connect to the system daemon with virt-manager. You should be prompted for root passwd before you can actually do anything useful on the privileged connection. KVM+TPM2.0+Win10/11 has been tested on SLES 15 SP5, which has the same virtualization components as Leap 15.5, but only with the libvirt system daemon. I think you will also have success after connecting virt-manager to your system daemon. -- You are receiving this mail because: You are on the CC list for the bug.