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 661272[details]
the guest's xml
Description of problem:
The guest will be destroyed when Fail to create snapshot for running guest which the image file is on the NFS storage
Version-Release number of selected component (if applicable):
libvirt-0.10.2-11.el6.x86_64
kernel-2.6.32-343.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.337.el6.x86_64
How reproducible:
80%
Steps to Reproduce:
1. Mount an NFS to local directory
# mount nfs-sever-ip:/vol/S3/libvirtmanual /mnt -o vers=3
2. Create a guest which the image file testkkk.img is on the NFS storage and format is qcow2.
# qemu-img info /mnt/testkkk.img
image: /mnt/testkkk.img
file format: qcow2
virtual size: 7.8G (8388608000 bytes)
disk size: 4.0G
cluster_size: 65536
3. create snapshot for the guest while the guest start completely
# virsh list
Id Name State
----------------------------------------------------
9 testkkk running
# virsh snapshot-create-as testkkk snap2
error: Unable to read from monitor: Connection reset by peer
: Connection reset by peer
# virsh list
Id Name State
----------------------------------------------------
#
Actual results:
fail to create snapshot for running guest, besides, the guest will be destroyed by this operation
Expected results:
scucceed to create snapshot for running guest and the guest should still be running state after creating snapshot.
Additional info:
libvirtd.log
2012-12-11 03:48:41.754+0000: 24049: error : qemuMonitorIORead:513 : Unable to read from monitor: Connection reset by peer
2012-12-11 03:48:41.754+0000: 24049: debug : qemuMonitorIO:646 : Error on monitor Unable to read from monitor: Connection reset by peer
Can not reproduce this issue on the rhel6.5 host according to the comment 0 steps.
Tried 8 times and the internal snapshots can be created successfully.
Host:
kernel-2.6.32-382.el6.x86_64
qemu-kvm-0.12.1.2-2.374.el6.x86_64
Created attachment 661272 [details] the guest's xml Description of problem: The guest will be destroyed when Fail to create snapshot for running guest which the image file is on the NFS storage Version-Release number of selected component (if applicable): libvirt-0.10.2-11.el6.x86_64 kernel-2.6.32-343.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.337.el6.x86_64 How reproducible: 80% Steps to Reproduce: 1. Mount an NFS to local directory # mount nfs-sever-ip:/vol/S3/libvirtmanual /mnt -o vers=3 2. Create a guest which the image file testkkk.img is on the NFS storage and format is qcow2. # qemu-img info /mnt/testkkk.img image: /mnt/testkkk.img file format: qcow2 virtual size: 7.8G (8388608000 bytes) disk size: 4.0G cluster_size: 65536 3. create snapshot for the guest while the guest start completely # virsh list Id Name State ---------------------------------------------------- 9 testkkk running # virsh snapshot-create-as testkkk snap2 error: Unable to read from monitor: Connection reset by peer : Connection reset by peer # virsh list Id Name State ---------------------------------------------------- # Actual results: fail to create snapshot for running guest, besides, the guest will be destroyed by this operation Expected results: scucceed to create snapshot for running guest and the guest should still be running state after creating snapshot. Additional info: libvirtd.log 2012-12-11 03:48:41.754+0000: 24049: error : qemuMonitorIORead:513 : Unable to read from monitor: Connection reset by peer 2012-12-11 03:48:41.754+0000: 24049: debug : qemuMonitorIO:646 : Error on monitor Unable to read from monitor: Connection reset by peer