- Package:
- virtinst
- Source:
- virt-manager
- Submitter:
- Date:
- 2022-01-13 20:06:02 UTC
- Severity:
- normal
- Tags:
When trying to create a new virtual machine virt-manager prints on "Step 1": Warning: host doest't support hardware virtualization. Installation parameters may be restricted. (I got this message in Russian so this is my translation. If one have this message in English please fix it) However, creation comletes succesfully and then guest runs in "xen (fullvirt)" mode. Version 0.8.4 also affected. Processor Xeon E5630, motherboard Supermicro X8DTU, Intel 5520 (Tylersburg) Chipset. RHEL5.4 with old virt-manager hasn't this problem on it.
Le Thursday 21 April 2011 14:37:40, Cole Robinson a écrit : This patch is part of virtinst 0.500.6 and system information specifies that virtint 0.500.6-1 is installed (required by virt-manager 0.8.7-1).
Sorry, missed that. In that case, it would be interesting to see virsh --connect xen:/// capabilities cat /proc/cpuinfo
It's in attachment. There's no "vmx" in cpuinfo, but according to some maillists it's normal. Actually it's exists and enabled.
Using that capabilities XML I can't reproduce your issue with latest upstream virt-manager and virtinst. Are you definitely using virtinst 0.500.6 ? If not, I'm not really sure what the issue is.
Hi, Cole Robinson wrote (03 May 2011 17:42:29 GMT) : Ping? Cole asked for more information more than 3 years ago. Can you still reproduce this on current Wheezy or testing/sid? Unless the requested information is provided, I think the next person who passes over this bug report in a month or so (possibly me) should close this bug report. Cheers, -- intrigeri
Dear Maintainer, I can confirm to experience the same issue, virt-manager/libvirt are unable to detect the presence of KVM on the system. It stopped working after updating to version 1.2.0.0-3. Virt-manager the tries to run the virtual machines with QEMU TCG... I've checked with both lsmod and kvm-ok and they reports that the required modules are loaded. Intel Virtualisation Technology is enabled in BIOS. The CPU running on the machineis an i7 7820HQ. I've tried purging all qemu-system-* libvirt-* packages and reinstalling qemu-kvm, libvirt-client, qemu-utils and libvirt-daemon-system As opposed to using libivirt I can run the virtual machines fine with qemu-system and experience bare-metal performance. So my guess is that this might be a bug in libvirt/ virt-manager, as the other systems can detect KVM us usual ? Best regards, Nils J. Haugen
Dear maintainer, I can confirm that i fixed the issue after consulting with some support over at the #virt channel on OFTC. The issue was that the libvirt system user account (libvirt-qemu) was not a member of the plugdev group, which owns /dev/kvm. After adding the libvirt-qemu to the plugdev group, libvirt recognises KVM and runs as normal. I'm not sure how this happend, as I've never done any changes to that group. Kind regards, Nils J. Haugen On Mon, 25 Feb 2019 11:30:40 +0100 nils+buglist@gaupne.net wrote: > Package: virt-manager > Version: 1:2.0.0-3 > Followup-For: Bug #623537 > > Dear Maintainer, > > > I can confirm to experience the same issue, virt-manager/libvirt are > unable to detect the presence of KVM on the system. It stopped working > after updating to version 1.2.0.0-3. Virt-manager the tries to run the > virtual machines with QEMU TCG... > > I've checked with both lsmod and kvm-ok and they reports that the > required modules are > loaded. Intel Virtualisation Technology is enabled in BIOS. > The CPU running on the machineis an i7 7820HQ. I've tried purging all > qemu-system-* libvirt-* packages and reinstalling qemu-kvm, libvirt-client, > qemu-utils and libvirt-daemon-system > > As opposed to using libivirt I can run the virtual machines fine with > qemu-system and > experience bare-metal performance. So my guess is that this might be a > bug in libvirt/ virt-manager, as the other systems can detect KVM us > usual ? > > Best regards, > Nils J. Haugen > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=nn_NO.UTF-8, LC_CTYPE=nn_NO.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages virt-manager depends on: > ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 > ii gir1.2-gtk-3.0 3.24.5-1 > ii gir1.2-gtk-vnc-2.0 0.9.0-1 > ii gir1.2-libosinfo-1.0 1.2.0-1 > ii gir1.2-libvirt-glib-1.0 1.0.0-1 > ii gir1.2-vte-2.91 0.54.2-2 > ii librsvg2-common 2.44.10-1 > ii python-requests 2.20.0-2 > ii python3 3.7.2-1 > ii python3-dbus 1.2.8-3 > ii python3-gi 3.30.4-1 > ii python3-gi-cairo 3.30.4-1 > ii python3-libvirt 5.0.0-1 > ii virtinst 1:2.0.0-3 > > Versions of packages virt-manager recommends:
Hi Nils, Thanks for investigating1! On Debin user libvirt-qemu should be in group kvm and $ ls -l /dev/kvm crw-rw----+ 1 root kvm 10, 232 Mär 5 09:30 /dev/kvm Plugdev is not the right group here: $ getfacl /dev/kvm getfacl: Removing leading '/' from absolute path names # file: dev/kvm # owner: root # group: kvm user::rw- user:agx:rw- group::rw- mask::rw- other::--- so s.th. seems to be wired in you setup. Since this does not seem to be a packaging bug can we close that issue? Cheers, -- Guido
Welcome Valuable Member, Thank you for your interest in our products. Your Yearly subscription for NORTON 360 PROTECTION has been renewed AND updated successfully. *Product Title* *End Date* *Quantity* *Total* *Payment Method* NORTON 360 PROTECTION In One year 1 $337.00 USD Auto Debit Order No. YEIG01132022P Order Date: 2022-01-13 *If you require urgent assistance, please call our Experts for refund and settlement issue on ** +1 – ( 877 ) – ( 397 ) – 1420*