Bug 993520 - Virtual machine disk locking not working with default packages
Virtual machine disk locking not working with default packages
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager (Show other bugs)
6.4
x86_64 Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: virt-mgr-maint
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-06 02:18 EDT by Pankaj
Modified: 2013-08-07 12:22 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-07 12:22:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pankaj 2013-08-06 02:18:09 EDT
Description of problem:
Virtual machine disk locking is not working with default packages.

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


How reproducible:
100%

Steps to Reproduce:
1. Create a virtual machine of any OS flavor.Power on the VM on Host1.
2. Migrate the VM to Host2 either via command line or virt-manager.
3. The VM is in power on Host2 and shutoff on Host1.
4. Power on the VM1 on Host1.


Actual results:
The VM can be powered-on on Host1 with read/write access.

Expected results:
The VM should be removed from Host1 after migration.

Additional info:
Found disk locking needs separate RPM (http://libvirt.org/locking.html). But we can not update the packages, until a bug is related and fixed to the particular package. We have to list the issue to the customer for using these packages.
How we handle this situation.
Comment 2 Dave Allan 2013-08-07 12:22:26 EDT
Bugzilla is not an avenue for support requests.  If you have a support contract with Red Hat, please contact the support organization for help with this kind of issue.

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