RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1097227 - VM migration in RHEV environment failed due to libvirt error "Failed to inquire lock: No such process"
Summary: VM migration in RHEV environment failed due to libvirt error "Failed to inqui...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Martin Kletzander
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1088034
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-13 12:14 UTC by Chris Pelland
Modified: 2018-12-05 18:33 UTC (History)
13 users (show)

Fixed In Version: libvirt-0.10.2-29.el6_5.8
Doc Type: Bug Fix
Doc Text:
Cause: Libvirt was not checking whether QEMU domain process is registered when using sanlock. Consequence: When VDSM was updated, set up sanlock for the host and libvirt and restarted libvirt daemon, any domain that was before the sanlock configuration and daemon restart could not have been migrated. Fix: Libvirt is now checking whether QEMU domain process is registered on sanlock or not before working with it. Result: Migration works in scenario described above.
Clone Of:
Environment:
Last Closed: 2014-05-27 16:27:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0560 0 normal SHIPPED_LIVE Moderate: libvirt security and bug fix update 2014-05-27 20:25:33 UTC

Description Chris Pelland 2014-05-13 12:14:19 UTC 
This bug has been copied from bug #1088034 and has been proposed
to be backported to 6.5 z-stream (EUS).
Comment 6 zhenfeng wang 2014-05-15 08:51:05 UTC 
I can reproduce this bug with the libvirt-0.10.2-29.el6_5.7.x86_64 with the pure libvirt env

steps
1. start a guest with default configuration, that means with sanlock disabled.

2. enable sanlock by edit qemu.conf:
lock_manager = "sanlock"

and edit qemu-sanlock.conf:
auto_disk_leases = 0
require_lease_for_disks = 0

3. restart libvirtd.

4. do migrate for the guest:
# virsh migrate rhel651 qemu+ssh://$target_ip/system --verbose 
error: Failed to inquire lock: No such process

verify this bug with libvirt-0.10.2-29.el6_5.8

1.Retest the step4 with libvirt-0.10.2-29.el6_5.8, the guest can be migrated successfully
# virsh migrate rhel651 qemu+ssh://$target_ip/system --verbose
Migration: [100 %]

2.Migrate the guest back to the source, will fail to migrate, this was the expect result since we didn't configure the proper sanlock in the source
# virsh migrate --live rhel651 qemu+ssh://$source_ip/system --verbose
root@source_ip's password: 
error: Child quit during startup handshake: Input/output error

3.Configure the proper sanlock in the source, then re-migrate the guest back to the target, the guest can be migrated successfully

# getsebool -a | grep sanlock
sanlock_use_fusefs --> off
sanlock_use_nfs --> on
sanlock_use_samba --> off
virt_use_sanlock --> on

#cat /etc/libvirt/qemu.conf
lock_manager = "sanlock"

# tail -5 /etc/libvirt/qemu-sanlock.conf 
user = "sanlock"
group = "sanlock"
host_id = 1
auto_disk_leases = 1
disk_lease_dir = "/var/lib/libvirt/sanlock"

#service wdmd start
#service sanlock start

#service libvirtd restart

# virsh migrate --live rhel651 qemu+ssh://$source_ip/system --verbose
root@$source_ip's password: 
Migration: [100 %]

Base the upper steps mark this bug verified
Comment 8 errata-xmlrpc 2014-05-27 16:27:18 UTC 
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/RHSA-2014-0560.html
Note You need to log in before you can comment on or make changes to this bug.