Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1146779[details]
gdb backtrace
Description of problem:
As subject
Version-Release number of selected component (if applicable):
libvirt-0.10.2-60.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.491.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. prepart a running guest without snapshot:
# virsh list
Id Name State
----------------------------------------------------
199 repeat running
# virsh snapshot-list repeat
Name Creation Time State
------------------------------------------------------------
2.Run the following script on two terminials, which do snapshot operations parallelly:
#!/bin/bash -x
DOM=repeat
VM_IP=192.168.122.233
for i in {1..1000};do
SNAP=`virsh snapshot-create $DOM|grep -o '[0-9]*'`
virsh snapshot-dumpxml $DOM $SNAP > /tmp/$SNAP.xml
virsh snapshot-create $DOM --redefine /tmp/$SNAP.xml --current
ssh root@$VM_IP lsblk
if [ $? -ne 0 ];then
ssh root@$VM_IP lsblk
ping $VM_IP -c 4
wall BUGS
echo $i BUGS
break
fi
virsh snapshot-delete $DOM $SNAP
done
When libvirtd SIGSEGV, term1 running at :
+ for i in '{1..1000}'
++ virsh snapshot-create repeat
++ grep -o '[0-9]*'
error: End of file while reading data: Input/output error
error: One or more references were leaked after disconnect from the hypervisor
error: Failed to reconnect to the hypervisor
term2 running at:
+ for i in '{1..1000}'
++ virsh snapshot-create repeat
++ grep -o '[0-9]*'
error: End of file while reading data: Input/output error
error: One or more references were leaked after disconnect from the hypervisor
error: Failed to reconnect to the hypervisor
Actual results:
As step2
Expected results:
Snapshot operation should add lock to avoid parallel operations.
Additional info:
backtrace info is in attachment.
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.
https://rhn.redhat.com/errata/RHBA-2017-0682.html
Created attachment 1146779 [details] gdb backtrace Description of problem: As subject Version-Release number of selected component (if applicable): libvirt-0.10.2-60.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.491.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. prepart a running guest without snapshot: # virsh list Id Name State ---------------------------------------------------- 199 repeat running # virsh snapshot-list repeat Name Creation Time State ------------------------------------------------------------ 2.Run the following script on two terminials, which do snapshot operations parallelly: #!/bin/bash -x DOM=repeat VM_IP=192.168.122.233 for i in {1..1000};do SNAP=`virsh snapshot-create $DOM|grep -o '[0-9]*'` virsh snapshot-dumpxml $DOM $SNAP > /tmp/$SNAP.xml virsh snapshot-create $DOM --redefine /tmp/$SNAP.xml --current ssh root@$VM_IP lsblk if [ $? -ne 0 ];then ssh root@$VM_IP lsblk ping $VM_IP -c 4 wall BUGS echo $i BUGS break fi virsh snapshot-delete $DOM $SNAP done When libvirtd SIGSEGV, term1 running at : + for i in '{1..1000}' ++ virsh snapshot-create repeat ++ grep -o '[0-9]*' error: End of file while reading data: Input/output error error: One or more references were leaked after disconnect from the hypervisor error: Failed to reconnect to the hypervisor term2 running at: + for i in '{1..1000}' ++ virsh snapshot-create repeat ++ grep -o '[0-9]*' error: End of file while reading data: Input/output error error: One or more references were leaked after disconnect from the hypervisor error: Failed to reconnect to the hypervisor Actual results: As step2 Expected results: Snapshot operation should add lock to avoid parallel operations. Additional info: backtrace info is in attachment.