------- Comment From kurzg...@fr.ibm.com 2017-04-24 12:24 EDT------- (In reply to comment #15) > From qemu logs for lotg2 on source (lotkvm) > ============================== > 2017-04-03 10:41:08.108+0000: initiating migration > 2017-04-05 11:11:56.293+0000: initiating migration > qemu-system-ppc64: /build/qemu-yKk2Ij/qemu-2.8+dfsg/block/io.c:1514: > bdrv_co_pwritev: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed. > 2017-04-05 11:16:25.557+0000: shutting down, reason=crashed >
This would definitely help to see the stack trace (either from the core file if any or using gdb -p). > > From qemu logs for lotg2 on destination (guskvm) > ================================= > > 2017-04-05 09:53:00.040+0000: starting up libvirt version: 2.5.0, package: > 3ubuntu5 (Christian Ehrhardt <christian.ehrha...@canonical.com> Tue, 21 Mar > 2017 08:02:37 +0100), qemu version: 2.8.0(Debian 1:2.8+dfsg-3ubuntu2), > hostname: guskvm.isst.aus.stglabs.ibm.com > LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin > QEMU_AUDIO_DRV=none /usr/bin/kvm -name guest=lotg2,debug-threads=on -S > -object > secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4-lotg2/ > master-key.aes -machine pseries-zesty,accel=kvm,usb=off,dump-guest-core=off > -cpu host,compat=power8 -m 8192 -realtime mlock=off -smp > 8,maxcpus=64,sockets=8,cores=1,threads=8 -uuid > cb8f1a9a-246e-4909-b9ba-069ba55669dd -display none -no-user-config > -nodefaults -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-4-lotg2/monitor.sock, > server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc > -no-shutdown -boot strict=on -device pci-ohci,id=usb,bus=pci.0,addr=0x3 > -device spapr-vscsi,id=scsi0,reg=0x2000 -drive > file=/lotg1_2_disks/lotg2_root.qcow2,format=qcow2,if=none,id=drive-virtio- > disk0,cache=none -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0, > id=virtio-disk0,bootindex=1 -drive > file=/lotg1_2_disks/lotg2_io2.qcow2,format=qcow2,if=none,id=drive-virtio- > disk1,cache=none -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1, > id=virtio-disk1 -drive > file=/lotg1_2_disks/lotg2_io1.qcow2,format=qcow2,if=none,id=drive-virtio- > disk2,cache=none -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk2, > id=virtio-disk2 -netdev tap,fd=28,id=hostnet0 -device > virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:45:9e:88,bus=pci.0,addr=0x1, > bootindex=2 -chardev pty,id=charserial0 -device > spapr-vty,chardev=charserial0,reg=0x30000000 -incoming defer -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x2 -msg timestamp=on > char device redirected to /dev/pts/3 (label charserial0) > /build/qemu-yKk2Ij/qemu-2.8+dfsg/nbd/server.c:nbd_receive_request():L710: > read failed > /build/qemu-yKk2Ij/qemu-2.8+dfsg/nbd/server.c:nbd_receive_request():L710: > read failed > /build/qemu-yKk2Ij/qemu-2.8+dfsg/nbd/server.c:nbd_receive_request():L710: > read failed > 2017-04-05 11:16:07.871+0000: shutting down, reason=failed > 2017-04-05T11:16:07.871980Z qemu-system-ppc64: terminating on signal 15 from > pid 10337 (/usr/sbin/libvirtd) I'm wondering if the destination fails like this because the source crashed... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680162 Title: Ubuntu17.04 KVM: Non-shared migration: nbd_receive_request():L710: read failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1680162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
