Unable to start any VMs : Domain requires KVM, but it is not available.

[Sreyan Chakravarty]

Hi,

I have just upgraded to the latest version of Fedora 32, and switched to
KDE.

Now the problem is that I Virt-Manager doesn't work anymore.

Whenever I try to start a VM I get:

Error starting domain: unsupported configuration: Domain requires KVM, but
it is not available. Check that virtualization is enabled in the host BIOS,
and host configuration is setup to load the kvm modules.

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279,
in startup
    self._backend.create()
  File "/usr/lib64/python3.8/site-packages/libvirt.py", line 1234, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: unsupported configuration: Domain requires KVM, but
it is not available. Check that virtualization is enabled in the host BIOS,
and host configuration is setup to load the kvm modules.

I have tried doing :
        sudo modprobde kvm

While it worked it did not change anything. I am still unable to start any
VMs.

I also tried

sudo modprobe kvm_intel

This failed since there is no such module.

What went wrong ?

I don't think switching to KDE will have any impact on the VM services.

[Ed Greshko]

On 18/11/2020 18:24, Sreyan Chakravarty wrote:
> Hi,
>
> I have just upgraded to the latest version of Fedora 32, and switched to KDE.
>
> Now the problem is that I Virt-Manager doesn't work anymore.
>
> Whenever I try to start a VM I get:
>
> Error starting domain: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
>
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
>     callback(asyncjob, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
>     callback(*args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
>     ret = fn(self, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279, in startup
>     self._backend.create()
>   File "/usr/lib64/python3.8/site-packages/libvirt.py", line 1234, in create
>     if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirt.libvirtError: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
>
> I have tried doing :
>         sudo modprobde kvm
>
> While it worked it did not change anything. I am still unable to start any VMs.
>
> I also tried
>
> sudo modprobe kvm_intel
>
> This failed since there is no such module.
>
> What went wrong ?

Well, kvm/qemu was working just fine for me on my KDE F32 system and continues to work just fine
after upgrade to F33.

Just to check, if you do

sudo grep --color vmx /proc/cpuinfo

You see the flag is present?

---
The key to getting good answers is to ask good questions.

[Sreyan Chakravarty]

On Wed, Nov 18, 2020 at 4:23 PM Ed Greshko  wrote:
> Well, kvm/qemu was working just fine for me on my KDE F32 system and
> continues to work just fine
> after upgrade to F33.
>
> Just to check, if you do
>
> sudo grep --color vmx /proc/cpuinfo
>
> You see the flag is present?

Interesting.

It seems that the flag is not present.

These are my flags that are currently set (gathered from /proc/cpuinfo)

flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl
est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm
3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp
fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap
clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts
hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d

I haven't changed any BIOS settings although I did update my BIOS.

[Tom Horsley]

On Wed, 18 Nov 2020 23:03:56 +0530
Sreyan Chakravarty wrote:
> I haven't changed any BIOS settings although I did update my BIOS.

I would suspect the BIOS update decided to reset the virt flag.
I'd go through the BIOS settings and see if it is now disabled
(I've never understood why so many BIOSes hate having the virt
flag enabled. I even saw one system where you had to completely
power down the system after changing the flag before it
would take effect).

[Sreyan Chakravarty]

On Wed, Nov 18, 2020 at 11:28 PM Tom Horsley  wrote:
> I would suspect the BIOS update decided to reset the virt flag.
> I'd go through the BIOS settings and see if it is now disabled
> (I've never understood why so many BIOSes hate having the virt
> flag enabled. I even saw one system where you had to completely
> power down the system after changing the flag before it
> would take effect).

Your suspicions were correct.

[Ed Greshko]

On 19/11/2020 01:33, Sreyan Chakravarty wrote:
> On Wed, Nov 18, 2020 at 4:23 PM Ed Greshko <[e-mail] > wrote:
> Well, kvm/qemu was working just fine for me on my KDE F32 system and continues to work just fine
> after upgrade to F33.
>
> Just to check, if you do
>
> sudo grep --color vmx /proc/cpuinfo
>
> You see the flag is present?
>
>
> Interesting.
>
> It seems that the flag is not present.
>
> These are my flags that are currently set (gathered from /proc/cpuinfo)
>
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
>
> I haven't changed any BIOS settings although I did update my BIOS.

Additionally, you can also us the "lscpu" command which would show something like for Intel processors.

CPU min MHz:                     1200.0000
BogoMIPS:                        5320.04
Virtualization:                  VT-x
L1d cache:                       128 KiB

In the output.

If not, best to double check your BIOS settings as the update may have affected it.

---
The key to getting good answers is to ask good questions.

[Sreyan Chakravarty]

On Wed, Nov 18, 2020 at 11:43 PM Ed Greshko  wrote:
> Additionally, you can also us the "lscpu" command which would show
> something like for Intel processors.
>
> CPU min MHz:                     1200.0000
> BogoMIPS:                        5320.04
> Virtualization:                  VT-x
> L1d cache:                       128 KiB
>
> In the output.
>
> If not, best to double check your BIOS settings as the update may have
> affected it.

Yup you were right.

Enabled VT-x from BIOS and now everything works like a charm.

Got disabled in the update.

[Patrick O'Callaghan]

On Wed, 2020-11-18 at 15:54 +0530, Sreyan Chakravarty wrote:
> I have just upgraded to the latest version of Fedora 32, and switched
> to
> KDE.
>
> Now the problem is that I Virt-Manager doesn't work anymore.

Works for me with no issues (on F32 and now on F33). Given your recent
questions about installing KDE, I have to wonder if something is
missing in your configuration.

poc

[Sreyan Chakravarty]

On Wed, Nov 18, 2020 at 4:33 PM Patrick O'Callaghan 
wrote:
> Works for me with no issues (on F32 and now on F33). Given your recent
> questions about installing KDE, I have to wonder if something is
> missing in your configuration.
>
> Yeah I am wondering the same thing.

I did swap fedora-release-workstation for fedora-release-kde.

Any other packages that I might need to change/swap/install ?

[Patrick O'Callaghan]

On Wed, 2020-11-18 at 23:05 +0530, Sreyan Chakravarty wrote:
> On Wed, Nov 18, 2020 at 4:33 PM Patrick O'Callaghan 
> wrote:
> > Works for me with no issues (on F32 and now on F33). Given your recent
> > questions about installing KDE, I have to wonder if something is
> > missing in your configuration.
> >
> > Yeah I am wondering the same thing.
>
> I did swap fedora-release-workstation for fedora-release-kde.

I don't know what you mean by this. I presume you didn't do a fresh
install of the KDE spin of Fedora, but installed the KDE group on your
existing system. The later is what I did for F32, but for F33 I just
installed the KDE spin. I don't think it makes any material difference
for this issue.
> Any other packages that I might need to change/swap/install ?

None that occur to me. I certainly didn't do anything special to get
this working.

poc

[Sreyan Chakravarty]

On Thu, Nov 19, 2020 at 3:53 AM Patrick O'Callaghan 
wrote:
> None that occur to me. I certainly didn't do anything special to get
> this working.

It was not enabled in the BIOS.