Bug 31065 - Qemu-KVM fails to install or is broken in current Cauldron
Summary: Qemu-KVM fails to install or is broken in current Cauldron
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-02 15:50 CET by Ulrich Beckmann
Modified: 2022-11-05 20:41 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
log of dnf install qemu-kvm (1.42 KB, text/plain)
2022-11-02 15:50 CET, Ulrich Beckmann
Details
log of urpmi commands, see comment #1 (2.37 KB, text/plain)
2022-11-04 19:14 CET, Ulrich Beckmann
Details
cauldron dnf install log (109.50 KB, text/plain)
2022-11-04 19:36 CET, sturmvogel
Details

Description Ulrich Beckmann 2022-11-02 15:50:30 CET
Created attachment 13470 [details]
log of dnf install qemu-kvm

I tried to install Qemu/KVM in a fresh Mageia 9 alpha 1 KDE Plasma installation. It fails with the attached error message.

In another installation, upgrade from Mageia 8, opening the guest machine fails with the error message "Error lauching details: Host does not support virtualisation type 'hvm' for architecture x86_64".

Best regards,
Ulrich
Ulrich Beckmann 2022-11-02 15:51:32 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=30992

Comment 1 Lewis Smith 2022-11-02 21:18:37 CET
Thank you for the report.

I tested installing all the pkgs xxx claimed "requires xxx, but none of the providers can be installed". Since they could all (but 1) be installed, reasonable to say they exist and are available:

$ sudo urpmi --test qemu-block-rbd     [1 of 8]
  qemu-block-rbd                 7.0.0        3.mga9        x86_64  

$ sudo urpmi --test qemu-system-x86     [1 of 62]
  qemu-system-x86                7.0.0        3.mga9        x86_64

$ urpmf librbd.so.1
lib64rbd1:/usr/lib64/librbd.so.1
$ sudo urpmi --test lib64rbd1          [1 of 5]
  lib64rbd1                      17.2.5       1.mga9        x86_64  

$ urpmf libfmt.so.8              ***
$

$ sudo urpmi --test qemu-kvm         [1 of 63]
  qemu-kvm                       7.0.0        3.mga9        x86_64

$ sudo urpmi --test libvirt-utils    [1 of 76]
  libvirt-utils                  8.8.0        1.mga9        x86_64
-----------
libfmt.so.8 was the only one I could not find. To bear in mind for the moment.

And I have just installed
 $ sudo urpmi qemu-kvm
which (63 pkgs) worked OK; but do not ask me to try it!
Do you want to try again? If you do not want to use urpmi, do use it with --test to see what would happen, but should not interfere with DNF.

Ever confirmed: 1 => 0
CC: (none) => lewyssmith
Status: NEW => UNCONFIRMED

Comment 2 sturmvogel 2022-11-02 21:28:49 CET
(In reply to Ulrich Beckmann from comment #0)
> In another installation, upgrade from Mageia 8, opening the guest machine
> fails with the error message "Error lauching details: Host does not support
> virtualisation type 'hvm' for architecture x86_64".

This sounds like as if virtualization isn't enabled in BIOS.
Comment 3 Ulrich Beckmann 2022-11-04 16:44:06 CET
(In reply to sturmvogel from comment #2)
> (In reply to Ulrich Beckmann from comment #0)
> > In another installation, upgrade from Mageia 8, opening the guest machine
> > fails with the error message "Error lauching details: Host does not support
> > virtualisation type 'hvm' for architecture x86_64".
> 
> This sounds like as if virtualization isn't enabled in BIOS.

No, Qemu/KVM is working unter Mageia 8 on the same machine. It is a multi-boot installation.

The kernel modules are loaded

[root@mga9-cauldron ~]# lsmod | grep kvm
kvm_intel             368640  0
kvm                  1085440  1 kvm_intel
irqbypass              16384  1 kvm
Comment 4 Lewis Smith 2022-11-04 17:09:37 CET
OK, that answers
> This sounds like as if virtualization isn't enabled in BIOS
But this bug was initially about "Qemu-KVM fails to install". Please go back to that in the light of comment 1.
This problem might exist just on new M9 installations, not upgrades.
CC'ing DaveH to ask ISO testers to try it, it is easy:
 $ sudo urpmi qemu-kvm virt-manager virt-viewer
[I only tried the first before; have just installed all 3 no problems]
OR
 # dnf install qemu-kvm virt-manager virt-viewer

> In another installation, upgrade from Mageia 8, opening the guest machine
> fails with the error message "Error lauching details:
> Host does not support virtualisation type 'hvm' for architecture x86_64"
> Qemu/KVM is working unter Mageia 8 on the same machine
Perhaps raise a separate bug for this.

CC: (none) => davidwhodgins

Comment 5 Ulrich Beckmann 2022-11-04 19:14:40 CET
Created attachment 13483 [details]
log of urpmi commands, see comment #1

I repeated all the commands of comment #1 in my older installation. 
The other one has yet no mirrors configured for urpmi.

I don't recall any related errors or messages during dnf upgrades.

I tried then to downgrade the to packages with errors.
No package libvirt-utils-8.6.0-1.mga9.x86_64 available.
No package lib64rbd1-17.2.3-2.mga9.x86_64 available.

Unfortunately older packages are not kept in Cauldron. Perhaps they should be downgraded on the mirrors to move on.

Ulrich
Comment 6 sturmvogel 2022-11-04 19:36:20 CET
Created attachment 13484 [details]
cauldron dnf install log

Something is really strange about your package versions.

(In reply to Ulrich Beckmann from comment #0)
> Created attachment 13470 [details]
> log of dnf install qemu-kvm
> 
> I tried to install Qemu/KVM in a fresh Mageia 9 alpha 1 KDE Plasma
> installation. It fails with the attached error message.
Tested in a fresh 64 Bit Plasma cauldron netinstall. The packages install just fine without problems. See attachment.
Comment 7 Dave Hodgins 2022-11-04 20:09:27 CET
Installation of the packages goes ok on my laptop in an m9 install. Rebooted.

Creating a vm using virt-manager fails in step 1 with
"Error: No hypervisor options were found for this connection."

the kvm, kvm_amd, irqbypass and ccp kernel modules are loaded.

Installed the packages on an m8 install on the same laptop, and rebooted.
In virt-manager step 1 goes ok. Chose to stop at step2.

So it's detecting the modules properly in m8, but not in m9.
Comment 8 Ulrich Beckmann 2022-11-05 20:41:04 CET
I confirm, the installation with dnf works here now, too.

I get the same error message when trying to create a new VM:
"Error: No hypervisor options were found for this connection."

I don't know which change led to the new situation.
I am closing the bug and will open a new one.

Resolution: (none) => FIXED
Status: UNCONFIRMED => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.