Bug 737851
| Summary: | Disconnecting cdrom image fail | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Miroslav Rezanina <mrezanin> |
| Component: | xen | Assignee: | Miroslav Rezanina <mrezanin> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.8 | CC: | gcosta, hjiang, juzhang, leiwang, llim, mkenneth, mshao, pbonzini, qguan, quintela, qwan, rhod, rwu, virt-maint, xen-maint, xfu, ydu |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | xen-3.0.3-135.el5 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 645266 | Environment: | |
| Last Closed: | 2012-02-21 05:56:05 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 699611 | ||
|
Comment 1
Miroslav Rezanina
2011-09-13 09:19:58 UTC
Fix built into xen-3.0.3-135.el5 Verified with xen-3.0.3-135.el5.
With the xen <= -134, there is error message prompt when try to disconnect the cdrom device in virt-manager:
Error Removing CDROM: Requeseted operation is not valid:
Xm driver only supports modifying persistent config.
And xend raise the error as following:
...
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1573, in reconfigureDevice
return self.getDeviceController(deviceClass).reconfigureDevice(
File "/usr/lib64/python2.4/site-packages/xen/xend/server/blkif.py", line 130, in reconfigureDevice
raise VmError("Can't read disk file %s" % new_back['params'])
VmError: Can't read disk file
After update to xen-3.0.3-135.el5, there is no issue with disconnecting cdrom device.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0160.html |