Bug 358531 - Can't go into "Details" on a Windows virtual machine
Summary: Can't go into "Details" on a Windows virtual machine
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 7
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-10-30 16:25 UTC by sbrooks
Modified: 2008-01-22 15:38 UTC (History)
1 user (show)

Fixed In Version: 0.5.3-1.fc7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-01-22 15:38:26 UTC

Attachments (Terms of Use)

Description sbrooks 2007-10-30 16:25:06 UTC
Description of problem:
Cannot go into the "Details" of a Windows virtual machine.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a Windows virtual machine (I used an existing LVM volume) with a
"bridged" network card       
2. After it exists, shut it down
3. Press the "Details" button
Actual results:
The detail window does not appear.

Terminal window shows the following:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 187, in
    self.show_details(uri, uuid)
  File "/usr/share/virt-manager/virtManager/engine.py", line 270, in show_details
  File "/usr/share/virt-manager/virtManager/details.py", line 130, in __init__
  File "/usr/share/virt-manager/virtManager/details.py", line 500, in
  File "/usr/share/virt-manager/virtManager/details.py", line 507, in
  File "/usr/share/virt-manager/virtManager/details.py", line 515, in
    for disk in self.vm.get_disk_devices():
  File "/usr/share/virt-manager/virtManager/domain.py", line 469, in
    raise RuntimeError("missing source path")
RuntimeError: missing source path

Expected results:
The details window appears.

Additional info:
virsh works fine: I can start/stop/dumpxml the virtual machine.

This may have been caused by the fix for Bug 247122 (which, as I understand it,
removed "(type netfront)" from the NIC), as I was able to get into the Details
screen before I recreated the virtual machine to fix that problem.

virsh dumpxml of the virtual machine:
<domain type='xen' id='1'>
    <boot dev='hd'/>
  <clock offset='utc'/>
    <interface type='bridge'>
      <source bridge='eth0'/>
      <target dev='vif1.0'/>
      <mac address='00:16:3e:6d:f6:91'/>
      <script path='vif-bridge'/>
    <disk type='block' device='disk'>
      <driver name='phy'/>
      <source dev='/dev/VolGroup00/QuantusServerC'/>
      <target dev='hda'/>
    <disk type='block' device='disk'>
      <driver name='phy'/>
      <source dev='/dev/VolGroup00/QuantusServerData'/>
      <target dev='hdb'/>
    <disk device='cdrom'>
      <target dev='hdc'/>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='5900' keymap='en-us'/>

xm list --long of the virtual machine:
    (domid 0)
    (on_crash restart)
    (uuid 00000000-0000-0000-0000-000000000000)
    (bootloader_args )
    (vcpus 2)
    (name Domain-0)
    (on_poweroff destroy)
    (on_reboot restart)
    (bootloader )
    (maxmem 4194303)
    (memory 1816)
    (shadow_memory 0)
    (cpu_weight 256)
    (cpu_cap 0)
    (features )
    (on_xend_start ignore)
    (on_xend_stop ignore)
    (cpu_time 73.859483487)
    (online_vcpus 2)
    (image (linux (kernel ) (rtc_timeoffset 0)))
    (status 2)
    (state r-----)
    (domid 1)
    (on_crash restart)
    (uuid f5314b1f-f39f-1b55-decd-e12cd1d961bf)
    (bootloader_args )
    (vcpus 1)
    (name quantusserver)
    (on_poweroff destroy)
    (on_reboot restart)
    (bootloader )
    (maxmem 192)
    (memory 192)
    (shadow_memory 3)
    (cpu_weight 256)
    (cpu_cap 0)
    (features )
    (on_xend_start ignore)
    (on_xend_stop ignore)
    (start_time 1193760765.61)
    (cpu_time 92.710645056)
    (online_vcpus 1)
            (kernel /usr/lib/xen/boot/hvmloader)
            (acpi 1)
            (apic 1)
            (boot c)
            (device_model /usr/lib/xen/bin/qemu-dm)
            (pae 1)
            (rtc_timeoffset 0)
            (usb 1)
            (notes (SUSPEND_CANCEL 1))
    (status 2)
    (state -b----)
    (store_mfn 49150)
            (bridge eth0)
            (mac 00:16:3e:6d:f6:91)
            (script vif-bridge)
            (uuid 9b21b7f8-92d2-316a-1bc5-1ae7460c0941)
            (backend 0)
            (uname phy:/dev/VolGroup00/QuantusServerC)
            (uuid 962609b4-7dd2-ec53-cbee-0c65ffbf8336)
            (mode w)
            (dev hda:disk)
            (backend 0)
            (bootable 1)
            (uname phy:/dev/VolGroup00/QuantusServerData)
            (uuid 77e3fcae-4c72-8a24-fe7c-96272aca7c58)
            (mode w)
            (dev hdb:disk)
            (backend 0)
            (bootable 0)
            (uuid 35041ec0-cc92-bb57-e0a7-ecb2e85b49c9)
            (mode r)
            (dev hdc:cdrom)
            (backend 0)
            (bootable 0)
    (device (vkbd (backend 0)))
            (vncunused 1)
            (keymap en-us)
            (type vnc)
            (uuid 9599b891-d5cb-b683-5584-1b8fd95a06e6)

Comment 1 Cole Robinson 2008-01-10 21:51:34 UTC
I verified this issue of F7. There was a fix for this pushed upstream which we
should probably add to F7. The linked patch applies cleanly to virt-manager-0.4.0-2.


What is causing it is the cdrom disk block:

    <disk device='cdrom'>
      <target dev='hdc'/>

virt-manager didn't know how to cope with it having no <source> tag. If you
remove this block using virsh, the errors should stop.

Comment 2 sbrooks 2008-01-11 14:41:08 UTC
You're right--I removed the cdrom, and virt-manager started working again.

Comment 3 Fedora Update System 2008-01-11 22:26:43 UTC
virt-manager-0.5.3-1.fc7, gtk-vnc-0.3.2-1.fc7, python-virtinst-0.300.2-1.fc7, virt-viewer-0.0.2-1.fc7 has been pushed to the Fedora 7 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update virt-manager gtk-vnc python-virtinst virt-viewer'

Comment 4 Fedora Update System 2008-01-22 15:37:58 UTC
virt-manager-0.5.3-1.fc7, gtk-vnc-0.3.2-1.fc7, python-virtinst-0.300.2-1.fc7, virt-viewer-0.0.2-1.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.

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