Bug 517285 - Host does not support any virtualization options
Summary: Host does not support any virtualization options
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-13 11:40 UTC by Tim Waugh
Modified: 2009-08-13 11:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-13 11:50:48 UTC


Attachments (Terms of Use)

Description Tim Waugh 2009-08-13 11:40:30 UTC
Description of problem:
After fixing PolicyKit bug #517257, virt-manager now connects successfully when I am logged in at the console as a non-root user.  Clicking New to create a new guest does not let me do so, however.  The New VM dialog only allows me to enter a name, and to press Cancel.

Version-Release number of selected component (if applicable):
virt-manager-0.8.0-1.fc12

How reproducible:
100%

Steps to Reproduce:
1.Click New
  
Actual results:
Dialog as described.

Additional info:
Running 'virt-manager --debug' gives this output when trying to add a new guest:

2009-08-13 12:38:59,730 (virt-manager:148): Application startup
2009-08-13 12:39:00,338 (netdevhelper:81): Bonding masters are: []
2009-08-13 12:39:00,347 (netdevhelper:176): Adding net device tun0 00:00:00:00:00:00 /sys/class/net/tun0 (bridge: None)
2009-08-13 12:39:00,355 (netdevhelper:176): Adding net device virbr0 be:b6:22:ff:ff:ff /sys/class/net/virbr0 (bridge: None)
2009-08-13 12:39:00,364 (netdevhelper:176): Adding net device lo 00:00:00:00:00:00 /sys/class/net/lo (bridge: None)
2009-08-13 12:39:00,372 (netdevhelper:176): Adding net device eth0 00:13:72:ff:ff:ff /sys/class/net/eth0 (bridge: None)
2009-08-13 12:39:00,394 (engine:112): About to connect to uris ['qemu:///system']
/usr/share/virt-manager/virtManager/manager.py:152: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  self.window = gtk.glade.XML(config.get_glade_dir() + "/vmm-manager.glade", "vmm-manager", domain="virt-manager")
2009-08-13 12:39:00,591 (engine:369): window counter incremented to 1
2009-08-13 12:39:00,669 (connection:346): Scheduling background open thread for qemu:///system
2009-08-13 12:39:00,670 (connection:461): Background thread is running
2009-08-13 12:39:00,674 (connection:357): Doing policykit for org.libvirt.unix.manage
2009-08-13 12:39:01,177 (connection:501): Background open thread complete, scheduling notify
2009-08-13 12:39:01,178 (connection:506): Notifying open result
2009-08-13 12:39:01,180 (connection:513): qemu:///system capabilities:
<capabilities>

  <host>
    <cpu>
      <arch>x86_64</arch>
    </cpu>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>tcp</uri_transport>
      </uri_transports>
    </migration_features>
    <topology>
      <cells num='1'>
        <cell id='0'>
          <cpus num='2'>
            <cpu id='0'/>
            <cpu id='1'/>
          </cpus>
        </cell>
      </cells>
    </topology>
    <secmodel>
      <model>selinux</model>
      <doi>0</doi>
    </secmodel>
  </host>

</capabilities>

2009-08-13 12:39:02,966 (create:332): Error determining default hypervisor
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 330, in set_conn_state
    self.change_caps()
  File "/usr/share/virt-manager/virtManager/create.py", line 695, in change_caps
    arch=arch)
  File "/usr/lib/python2.6/site-packages/virtinst/CapabilitiesParser.py", line 421, in guest_lookup
    {'virttype' : osstr, 'arch' : archstr})
ValueError: Host does not support any virtualization options 
2009-08-13 12:39:05,408 (engine:373): window counter decremented to 0
2009-08-13 12:39:05,421 (engine:381): Exiting app normally.

Comment 1 Tim Waugh 2009-08-13 11:50:48 UTC
Oh, never mind, I didn't have qemu installed.

For some reason it wasn't showing the dialog telling me this until after I played around with adding new connections from the menu bar.


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