Warning: KVM Not Available

Trying to get virtualization set up on TW. But I get a warning that looks like this:

1711065084_grim

I thought maybe I hadn’t installed the pattern correctly, but every package under the pattern is installed:

(I know I didn’t scroll down, but all the boxes are checked).

And yet, I still get the kvm warning.

lsmod | grep kvm
kvm                  1380352  0
irqbypass              12288  1 kvm

I also have the libvirt daemon installed and running. I have added my USER to the libvirt group. I’ve also rebooted several times post installing the pattern.

I think that’s what is supposed to be there, but I may be wrong. I do know that virtualization is enabled, as it was working before on this install of openSUSE. It was just never reinstalled after I did a rollback a few months back.

Anyone know what I can do to get this to work? I can get virt-manager to work, but it terrifyingly slow to the point that it is unusable. I attempted to google this, and most say that it’s because virtualization isn’t enabled, but I’m positive it is. Nothing has changed in the BIOS since the last time I used kvm+qemu.

Thanks in advance.

Matt

@thelinuxcast what about libvirtd (virt-manager if needed), is that installed?

1 Like

Hey Matt, nice to see you here :slight_smile:

Have you tried setting up virtualization from Yast?
It should re-(setup) everything needed for VMs to work except adding your user to the appropriate groups (kvm,libvirt,qemu), without which you would need to grant it permission each time connecting to the qemu socket, etc. but this has no impact on functionality otherwise.

On my AMD system, there are a few more modules related to kvm loaded:

pavin@suse-pc:~> lsmod | grep kvm
kvm_amd               204800  0
kvm                  1359872  1 kvm_amd
irqbypass              12288  1 kvm
ccp                   151552  1 kvm_amd
1 Like

There’s no package in the repos named that. I’m guessing it’s because it’s a part of the pattern.

Yeah, I’ve done it both ways now and get the same result.

As for the output of lsmod, IDK what the missing things would be. I will look up how to enable virtualization and check to make sure everything is still enabled, but IDK how it would have changed as it was working before.

@thelinuxcast libvirt libvirt-daemon virt-manager

Yeah, all three already installed.

@thelinuxcast and did you start the libvirtd service and enable (if needed)?

Yup.

They also need to be part of the kvm group, and remember to log out and log back in if you change group membership.

But not being in those groups should cause virt-manager to simply prompt for root creds and everything should work. The core of your issue is probably that ‘rollback a few months back.’ I’m betting your system isn’t in the consistant state you think it’s in. You might want to consider reinstalling the needed virtualization packages.

@mhurron no kvm here, but I’m in the libvirt group…

I will add me to that group and see. But I have already re-installed. A couple of times actually. Once with zypper once with YaST

The kvm group should exist if you are on the host running kvm, if you are just running libvirt frontends then you won’t have the group. By default, the kvm group is required to access /dev/kvm

Could you provide the priority 3 errors since the current boot?

sudo journalctl -p3 -b

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.