Bug 484369
Summary: | issuing eject on cdrom device does not update image status in machine details | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Karel Volný <kvolny> |
Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | xen-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-13 16:01:35 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
Karel Volný
2009-02-06 14:41:01 UTC
The problem with this, is that the hypervisor would need to be told by the VM that the media was ejected from within the VM. As far as I know there is no mechanism for this to be done, and would likely be non trivial, maybe even impossible with an unmodified FV OS. Communication is largely one-way: virt-manager/libvirt/xen tells the VM what it's hardware did (disk added/removed, media ejected/inserted), not the other way around. As far as I know, this type of stuff isn't even implemented in upstream xen, so it's out of scope for RHEL5. Closing as WONTFIX. |