Bug 358531
Summary: | Can't go into "Details" on a Windows virtual machine | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | sbrooks |
Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | hbrock |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 0.5.3-1.fc7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-22 15:38:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
sbrooks
2007-10-30 16:25:06 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. http://hg.et.redhat.com/virt/applications/virt-manager--devel?cs=27ad8c7fbc3e What is causing it is the cdrom disk block: <disk device='cdrom'> <target dev='hdc'/> <readonly/> </disk> 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. You're right--I removed the cdrom, and virt-manager started working again. 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' 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. |