This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 411901 - virt-manager doesn't pick up presence of kvm (qemu-kvm)
virt-manager doesn't pick up presence of kvm (qemu-kvm)
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
8
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Berrange
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-05 08:03 EST by Jonathan Underwood
Modified: 2007-12-05 09:53 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-12-05 09:53:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jonathan Underwood 2007-12-05 08:03:57 EST
Description of problem:
On installation of virt-manager and kvm, virt-manager doesn't seem to notice
that qemu-kvm is present.

Version-Release number of selected component (if applicable):
python-virtinst-0.300.1-3.fc8
virt-viewer-0.0.2-2.fc8
libvirt-0.3.3-2.fc8
libvirt-python-0.3.3-2.fc8
virt-manager-0.5.2-2.fc8
kvm-36-7.fc8

How reproducible:
Everytime

Steps to Reproduce:
1. yum install virt-manager kvm
2. run virt-manager
3. choose to make a new VM
  
Actual results:
The tick box to select hardware acceleration is greyed out and not selectable.
Proceeding with the installation crashes out with:

Unable to complete install '<class 'libvirt.libvirtError'>
virDomainCreateLinux() failed Cannot find QEMU binary
/usr/bin/qemu-system-x86_64: No such file or directory
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 616, in do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 724, in
start_install
    return self._do_install(consolecb, meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 741, in
_do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib64/python2.5/site-packages/libvirt.py", line 573, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: virDomainCreateLinux() failed Cannot find QEMU binary
/usr/bin/qemu-system-x86_64: No such file or directory
'

So, virt-manager is not aware of qemu-kvm and is looking for qemu binaries.


Expected results:
A hardware accelerated qemu-kvm guest is created.

Additional info:
Comment 1 Jonathan Underwood 2007-12-05 08:05:15 EST
Oh, I should've mentioned, in between steps 1 and 2 above I did do a 
/sbin/service libvirtd start
Comment 2 Jonathan Underwood 2007-12-05 08:34:58 EST
This might also be useful info (note that I did also install plain qemu). I am
not sure why it is listing qemu-system-x86_64 as the emulator for hvm, surely
this should be qemu-kvm

virsh # connect qemu:///system

virsh # list
 Id Name                 State
----------------------------------

virsh # capabilities
<capabilities>
  <host>
    <cpu>
      <arch>x86_64</arch>
    </cpu>
  </host>

  <guest>
    <os_type>hvm</os_type>
    <arch name="x86_64">
      <wordsize>64</wordsize>
      <emulator>/usr/bin/qemu-system-x86_64</emulator>
      <domain type="qemu"/>
      <machine>pc</machine>
      <machine>isapc</machine>
    </arch>
    <features>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
    </features>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name="i686">
      <wordsize>32</wordsize>
      <emulator>/usr/bin/qemu</emulator>
      <domain type="qemu"/>
      <machine>pc</machine>
      <machine>isapc</machine>
    </arch>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name="mips">
      <wordsize>32</wordsize>
      <emulator>/usr/bin/qemu-system-mips</emulator>
      <domain type="qemu"/>
      <machine>mips</machine>
    </arch>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name="mipsel">
      <wordsize>32</wordsize>
      <emulator>/usr/bin/qemu-system-mipsel</emulator>
      <domain type="qemu"/>
      <machine>mips</machine>
    </arch>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name="sparc">
      <wordsize>32</wordsize>
      <emulator>/usr/bin/qemu-system-sparc</emulator>
      <domain type="qemu"/>
      <machine>sun4m</machine>
    </arch>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name="ppc">
      <wordsize>32</wordsize>
      <emulator>/usr/bin/qemu-system-ppc</emulator>
      <domain type="qemu"/>
      <machine>g3bw</machine>
      <machine>mac99</machine>
      <machine>prep</machine>
    </arch>
  </guest>
</capabilities>
Comment 3 Daniel Berrange 2007-12-05 09:27:17 EST
That list of capabilities shows that no KVM support is detected. It is not
sufficient to merely have the 'qemu-kvm' binary installed. You need to have the
kernel modules loaded. If /dev/kvm does not exist, then you won't be able to
create KVM guests. Please confirm whether /dev/kvm exists.

Comment 4 Jonathan Underwood 2007-12-05 09:42:09 EST
Aha... that's a weird thing. /dev/kvm is not there. However, the kvm module is
loaded:

# /sbin/lsmod | grep kvm
kvm                    69657  0

But, I see there's no kvm-intel loaded. And worse:

# /sbin/modprobe kvm-intel
FATAL: Error inserting kvm_intel
(/lib/modules/2.6.23.8-63.fc8/kernel/drivers/kvm/kvm-intel.ko): Operation not
supported

I suspect then this is a bug with the kernel...
Comment 5 Daniel Berrange 2007-12-05 09:53:19 EST
Not a virt-manager bug then....

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