Bug 575993 - "New VM" wizard shows "Error: No guests are supported for this connection."
Summary: "New VM" wizard shows "Error: No guests are supported for this connection."
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-22 22:30 UTC by Dave Malcolm
Modified: 2010-11-17 18:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 581824 (view as bug list)
Environment:
Last Closed: 2010-11-17 18:52:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Screenshot of "New VM" wizard, showing error (21.30 KB, image/png)
2010-03-22 22:30 UTC, Dave Malcolm
no flags Details

Description Dave Malcolm 2010-03-22 22:30:23 UTC
Created attachment 401880 [details]
Screenshot of "New VM" wizard, showing error

Description of problem:
I'm attempting to use virt-manager to create my first guest on a fresh install on Fedora 12, but get an error in the first page:
"Error: No guests are supported for this connection."

Version-Release number of selected component (if applicable):
libvirt-0.7.1-15.fc12.x86_64
qemu-img-0.11.0-13.fc12.x86_64
virt-manager-0.8.2-1.fc12.noarch

$ uname -a
Linux surprise 2.6.32.9-67.fc12.x86_64 #1 SMP Sat Feb 27 09:26:40 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:
100% for now

Steps to Reproduce:
1. System Tool > Virtual Machine Manager
2. (Authenticate with root password)
3. List view is empty apart from "localhost (QEMU)"
4. Right-click on "localhost (QEMU)", select "New" 
  
Actual results:
Dialog has "Error: No guests are supported for this connection."

Expected results:
Dialog should provide a diagnostic indicating what the problem is.  I'm not sure how to go about troubleshooting this further.

Additional info:
As I said, I'm not sure how to go about troubleshooting this further.

$ service libvirtd status
libvirtd (pid  1918) is running...

Does anything else need to be installed, or be running?

$ cat /proc/cpuinfo | grep flags | uniq
flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt aes lahf_lm ida arat tpr_shadow vnmi flexpriority ept vpid

Looking at: http://virt-manager.sourcearchive.com/documentation/0.7.0/create_8py-source.html
I see that this appears to be due to an exception inside vmmCreate.change_caps, but it's not clear to me how to debug this further.

Comment 1 Cole Robinson 2010-03-22 23:45:31 UTC
Yeah, the error message is crap. Upstream has much better error reporting here.

What it basically means is that libvirt didn't detect any available qemu emulators. So either qemu isn't installed, or the kvm binary is the only one present but the modules aren't loaded.

Comment 2 Dave Malcolm 2010-03-23 15:19:40 UTC
Looks like I had too early a version of qemu-system; "yum install kvm" did the following:

--> Processing Dependency: qemu-common = 2:0.11.0-13.fc12 for package: 2:qemu-system-x86-0.11.0-13.fc12.x86_64
--> Processing Dependency: bochs-bios >= 2.3.8-0.8 for package: 2:qemu-system-x86-0.11.0-13.fc12.x86_64
--> Processing Dependency: /usr/share/gpxe/virtio-net.rom for package: 2:qemu-system-x86-0.11.0-13.fc12.x86_64
--> Processing Dependency: /usr/share/gpxe/rtl8029.rom for package: 2:qemu-system-x86-0.11.0-13.fc12.x86_64
--> Processing Dependency: vgabios for package: 2:qemu-system-x86-0.11.0-13.fc12.x86_64
--> Processing Dependency: /usr/share/gpxe/e1000-0x100e.rom for package: 2:qemu-system-x86-0.11.0-13.fc12.x86_64
--> Processing Dependency: /usr/share/gpxe/pcnet32.rom for package: 2:qemu-system-x86-0.11.0-13.fc12.x86_64
--> Processing Dependency: /usr/share/gpxe/rtl8139.rom for package: 2:qemu-system-x86-0.11.0-13.fc12.x86_64
--> Running transaction check
---> Package bochs-bios.noarch 0:2.3.8-0.9.git04387139e3b.fc12 set to be updated
---> Package gpxe-roms-qemu.noarch 0:0.9.9-1.20091018git.fc12 set to be updated
---> Package qemu-common.x86_64 2:0.11.0-13.fc12 set to be updated
---> Package vgabios.noarch 0:0.6b-3.fc12 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package            Arch      Version                          Repository  Size
================================================================================
Installing:
 qemu-system-x86    x86_64    2:0.11.0-13.fc12                 updates    2.1 M
Installing for dependencies:
 bochs-bios         noarch    2.3.8-0.9.git04387139e3b.fc12    updates     52 k
 gpxe-roms-qemu     noarch    0.9.9-1.20091018git.fc12         updates    223 k
 qemu-common        x86_64    2:0.11.0-13.fc12                 updates    213 k
 vgabios            noarch    0.6b-3.fc12                      fedora      36 k

Transaction Summary
================================================================================
Install       5 Package(s)
Upgrade       0 Package(s)


...etc.   After upgrade:

$ rpm -q --whatprovides kvm
qemu-system-x86-0.11.0-13.fc12.x86_64

Comment 3 Bug Zapper 2010-11-03 18:52:31 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Cole Robinson 2010-11-17 18:52:38 UTC
Not backporting to F12 at this point, so closing against F13 where this is
currently fixed.


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