Bug 476093 - detaching block devices malfunction if the device is in use by the guest.
detaching block devices malfunction if the device is in use by the guest.
Status: CLOSED DUPLICATE of bug 484110
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Michal Novotny
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2008-12-11 16:39 EST by Gurhan Ozen
Modified: 2014-02-02 17:36 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-05 07:35:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gurhan Ozen 2008-12-11 16:39:32 EST
Description of problem:
When detaching a device from a guest when the device is in use by the guest, xen detaches it nonetheless and removes it from the guest domain's info even though the device lives on the guest causing the subsequent block attach/detach commands to be in disarray.

Version-Release number of selected component (if applicable):
# rpm -qa | grep xen 

How reproducible:

Steps to Reproduce:
1. Install a guest, attach a device.
2. Go to the guest and format and mount the device
3. In dom0 detach the device. Both xm and virsh detaching operations return ok and the device is removed from the guest's disk list.
4. Go back to guest and do /proc/partitions
Actual results:
dom0 thinks that the device is detached from the guest and removes the device from the guest configuration even though the device is there in the guest.

Expected results:
detach operations should return error if the device is in use by the guest.

Additional info:
Comment 2 Michal Novotny 2009-03-05 07:35:33 EST
Well, returning error when xend is unable to detach the device is not possible but except showing this error message it works fine with patch for BZ #484110.

*** This bug has been marked as a duplicate of bug 484110 ***

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