http://bugzilla.opensuse.org/show_bug.cgi?id=911036 Bug ID: 911036 Summary: virt-manager clone vm fails Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: admin@inbox-online.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36 Build Identifier: When trying to clone VM with virt-manager qemu-img crashes with "unexpected fatal signal 6: *** stack smashing detected ***: /usr/bin/qemu-img terminated" Reproducible: Always Steps to Reproduce: 1. Create VM with qcow2 hard drive within virt-manager 2. Try to clone the VM within virt-manager Actual Results: qemu-img crashes with "unexpected fatal signal 6: *** stack smashing detected ***: /usr/bin/qemu-img terminated" Expected Results: virt-manager should create a VM clone Error creating virtual machine clone 'StackController': internal error: Child process (/usr/bin/qemu-img convert -f qcow2 -O qcow2 -o nocow=on,compat=1.1,lazy_refcounts /var/lib/libvirt/images/StackClean/disk0.qcow2 /var/lib/libvirt/images/StackClean/disk0-clone.qcow2) unexpected fatal signal 6: *** stack smashing detected ***: /usr/bin/qemu-img terminated ======= Backtrace: ========= /lib64/libc.so.6(+0x730bf)[0x7f5f5136b0bf] /lib64/libc.so.6(__fortify_fail+0x37)[0x7f5f513edc67] /lib64/libc.so.6(__fortify_fail+0x0)[0x7f5f513edc30] /usr/bin/qemu-img(+0x91df8)[0x7f5f530f9df8] /usr/bin/qemu-img(+0x2feca)[0x7f5f53097eca] /usr/bin/qemu-img(bdrv_create+0x67)[0x7f5f53098767] /usr/bin/qemu-img(bdrv_create_file+0x49)[0x7f5f53098d09] /usr/bin/qemu-img(+0x78ea3)[0x7f5f530e0ea3] /usr/bin/qemu-img(+0x2feca)[0x7f5f53097eca] /usr/bin/qemu-img(+0x65afa)[0x7f5f530cdafa] /lib64/libc.so.6(+0x45fd0)[0x7f5f5133dfd0] ======= Memory map: ======== 7f5f48000000-7f5f48022000 rw-p 00000000 00:00 0 7f5f48022000-7f5f4c000000 ---p 00000000 00:00 0 7f5f4cf7e000-7f5f4d17f000 rw-p 00000000 00:00 0 7f5f4d17 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/clone.py", line 823, in _async_clone self.clone_design.start_duplicate(meter) File "/usr/share/virt-manager/virtinst/cloner.py", line 442, in start_duplicate dst_dev.setup(meter=meter) File "/usr/share/virt-manager/virtinst/devicedisk.py", line 816, in setup volobj = self._storage_creator.create(meter) File "/usr/share/virt-manager/virtinst/diskbackend.py", line 352, in create return self._vol_install.install(meter=progresscb) File "/usr/share/virt-manager/virtinst/storage.py", line 733, in install vol = self.pool.createXMLFrom(xml, self.input_vol, cloneflags) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3066, in createXMLFrom if ret is None:raise libvirtError('virStorageVolCreateXMLFrom() failed', pool=self) libvirtError: internal error: Child process (/usr/bin/qemu-img convert -f qcow2 -O qcow2 -o nocow=on,compat=1.1,lazy_refcounts /var/lib/libvirt/images/StackClean/disk0.qcow2 /var/lib/libvirt/images/StackClean/disk0-clone.qcow2) unexpected fatal signal 6: *** stack smashing detected ***: /usr/bin/qemu-img terminated ======= Backtrace: ========= /lib64/libc.so.6(+0x730bf)[0x7f5f5136b0bf] /lib64/libc.so.6(__fortify_fail+0x37)[0x7f5f513edc67] /lib64/libc.so.6(__fortify_fail+0x0)[0x7f5f513edc30] /usr/bin/qemu-img(+0x91df8)[0x7f5f530f9df8] /usr/bin/qemu-img(+0x2feca)[0x7f5f53097eca] /usr/bin/qemu-img(bdrv_create+0x67)[0x7f5f53098767] /usr/bin/qemu-img(bdrv_create_file+0x49)[0x7f5f53098d09] /usr/bin/qemu-img(+0x78ea3)[0x7f5f530e0ea3] /usr/bin/qemu-img(+0x2feca)[0x7f5f53097eca] /usr/bin/qemu-img(+0x65afa)[0x7f5f530cdafa] /lib64/libc.so.6(+0x45fd0)[0x7f5f5133dfd0] ======= Memory map: ======== 7f5f48000000-7f5f48022000 rw-p 00000000 00:00 0 7f5f48022000-7f5f4c000000 ---p 00000000 00:00 0 7f5f4cf7e000-7f5f4d17f000 rw-p 00000000 00:00 0 7f5f4d17 -- You are receiving this mail because: You are on the CC list for the bug.