Red Hat Bugzilla – Bug 845468
snapshot-list --descendants --from will core dumped
Last modified: 2013-10-20 17:45:36 EDT
Description of problem: snapshot-list --descendants --from will core dumped Version-Release number of selected component (if applicable): libvirt-0.10.0-0rc0.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.297.el6_3.x86_64 How reproducible: 100% Steps to Reproduce: 1. prepare a domain with snapshot # virsh snapshot-list q3 Name Creation Time State ------------------------------------------------------------ d1 2012-07-26 14:43:43 +0800 disk-snapshot d2 2012-07-26 14:43:49 +0800 disk-snapshot d3 2012-07-26 14:43:56 +0800 disk-snapshot s1 2012-07-26 11:06:19 +0800 running s2 2012-07-26 14:34:18 +0800 shutoff s3 2012-07-26 14:34:56 +0800 shutoff 2.# virsh snapshot-list q3 --descendants --from d1 Segmentation fault (core dumped) [root@intel-q9400-4-2 ~]# virsh snapshot-list q3 --descendants --from s1 Segmentation fault (core dumped) Actual results: as step2 Expected results: no core dumped Additional info: -- Best Regards! Wenlong Huang IRC Account: wenlong Phone: 62608117
The problem is in the RPC code that doesn't fill one of the arguments when doing the remote call. I'll post a patch soon.
Fixed upstream: commit 2b01761d5e9addaefe33b2934576836836f486e2 Author: Peter Krempa <pkrempa@redhat.com> Date: Fri Aug 3 11:45:12 2012 +0200 remote: Fill snapshot argument in remoteDomainSnapshotListAllChildren The remote driver did not fill the required snapshot parent argument in the RPC call structure that caused a client crash when trying to use this new API. Moving to POST.
Test with: libvirt-0.10.0-0rc1.el6.x86_64 [root@zhpeng ~]# virsh snapshot-list rhel63q --descendants --from d1 Name Creation Time State ------------------------------------------------------------ d2 2012-08-23 15:59:00 +0800 disk-snapshot d3 2012-08-23 15:59:02 +0800 disk-snapshot d4 2012-08-23 15:59:04 +0800 disk-snapshot snap1 2012-08-23 15:59:09 +0800 running So this is verified.
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-2013-0276.html