Hide Forgot
Description of problem: libvirtd crash on domblkinfo. # pgrep libvirtd 19191 # virsh -r domblkinfo 1 vda error: End of file while reading data: Input/output error # pgrep libvirtd 20472 No core-dump, nothing in logs. Version-Release number of selected component (if applicable): libvirt-0.9.4-10.el6.x86_64 How reproducible: 100%
Worked on libvirt-0.9.4-7.el6.x86_64
I suspect my snapshot patches may be involved; in particular, my guess is this upstream commit: commit 89b6284fd94ce5b13ee6b002f9167f5d9074aa7a Author: Eric Blake <eblake> Date: Fri Aug 19 20:38:36 2011 -0600 snapshot: also support disks by path I got confused when 'virsh domblkinfo dom disk' required the path to a disk (which can be ambiguous, since a single file can back multiple disks), rather than the unambiguous target device name that I was using in disk snapshots. So, in true developer fashion, I went for the best of both worlds - all interfaces that operate on a disk (aka block) now accept either the target name or the unambiguous path to the backing file used by the disk.
yup seems to be an uninitialized disk variable should be easy to get fixed Daniel
Upstream patch proposed: https://www.redhat.com/archives/libvir-list/2011-September/msg00379.html
Moving to POST: http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-September/msg00286.html
Reproduce this issue with libvirt-0.9.4-10.el6.x86_64. Verified this issue with: libvirt-0.9.4-11.el6.x86_64 kernel-2.6.32-193.el6.x86_64 qemu-kvm-0.12.1.2-2.185.el6.x86_64 # pgrep libvirtd 27271 # virsh -r domblkinfo 15 vda Capacity: 8589934592 Allocation: 8589938688 Physical: 8589938688 # pgrep libvirtd 27271 So change the status to 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/RHBA-2011-1513.html