From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52018) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eyDbq-0001ZL-Ql for qemu-devel@nongnu.org; Tue, 20 Mar 2018 05:31:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eyDbk-0003AO-Ob for qemu-devel@nongnu.org; Tue, 20 Mar 2018 05:31:10 -0400 Received: from indium.canonical.com ([91.189.90.7]:51116) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eyDbk-00039L-Hk for qemu-devel@nongnu.org; Tue, 20 Mar 2018 05:31:04 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1eyDbi-0006hx-SL for ; Tue, 20 Mar 2018 09:31:03 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id D49892E80CD for ; Tue, 20 Mar 2018 09:31:02 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 20 Mar 2018 09:18:00 -0000 From: =?utf-8?b?5p2O56mX5oGS?= <1754542@bugs.launchpad.net> Reply-To: Bug 1754542 <1754542@bugs.launchpad.net> Sender: bounces@canonical.com References: <152056405865.7543.8980677605113063936.malonedeb@wampee.canonical.com> Message-Id: <152153748011.15312.10257450750410289981.malone@chaenomeles.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org It is my trace event file. I read it many times, but still can't find the cause of the error. I just found after colo_vm_state_change ide_reset and ps2_kbd_reset ... ** Attachment added: "trace-pvm.log" https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5084770/+files/= trace-pvm.log -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1754542 Title: colo: vm crash with segmentation fault Status in QEMU: New Bug description: I use Arch Linux x86_64 Zhang Chen's(https://github.com/zhangckid/qemu/tree/qemu-colo-18mar10) Following document 'COLO-FT.txt', I test colo feature on my hosts I run this command Primary: sudo /usr/local/bin/qemu-system-x86_64 -enable-kvm -m 2048 -smp 2 -qmp st= dio -name primary \ -device piix3-usb-uhci \ -device usb-tablet -netdev tap,id=3Dhn0,vhost=3Doff \ -device virtio-net-pci,id=3Dnet-pci0,netdev=3Dhn0 \ -drive if=3Dvirtio,id=3Dprimary-disk0,driver=3Dquorum,read-pattern=3Dfifo= ,vote-threshold=3D1,\ children.0.file.filename=3D/var/lib/libvirt/images/1.raw,\ children.0.driver=3Draw -S Secondary: sudo /usr/local/bin/qemu-system-x86_64 -enable-kvm -m 2048 -smp 2 -qmp st= dio -name secondary \ -device piix3-usb-uhci \ -device usb-tablet -netdev tap,id=3Dhn0,vhost=3Doff \ -device virtio-net-pci,id=3Dnet-pci0,netdev=3Dhn0 \ -drive if=3Dnone,id=3Dsecondary-disk0,file.filename=3D/var/lib/libvirt/im= ages/2.raw,driver=3Draw,node-name=3Dnode0 \ -drive if=3Dvirtio,id=3Dactive-disk0,driver=3Dreplication,mode=3Dsecondar= y,\ file.driver=3Dqcow2,top-id=3Dactive-disk0,\ file.file.filename=3D/mnt/ramfs/active_disk.img,\ file.backing.driver=3Dqcow2,\ file.backing.file.filename=3D/mnt/ramfs/hidden_disk.img,\ file.backing.backing=3Dsecondary-disk0 \ -incoming tcp:0:8888 Secondary: {'execute':'qmp_capabilities'} { 'execute': 'nbd-server-start', 'arguments': {'addr': {'type': 'inet', 'data': {'host': '192.168.0.34',= 'port': '8889'} } } } {'execute': 'nbd-server-add', 'arguments': {'device': 'secondary-disk0', = 'writable': true } } Primary: {'execute':'qmp_capabilities'} { 'execute': 'human-monitor-command', 'arguments': {'command-line': 'drive_add -n buddy driver=3Dreplication,= mode=3Dprimary,file.driver=3Dnbd,file.host=3D192.168.0.34,file.port=3D8889,= file.export=3Dsecondary-disk0,node-name=3Dnbd_client0'}} { 'execute':'x-blockdev-change', 'arguments':{'parent': 'primary-disk0', = 'node': 'nbd_client0' } } { 'execute': 'migrate-set-capabilities', 'arguments': {'capabilities': [ {'capability': 'x-colo', 'state': t= rue } ] } } { 'execute': 'migrate', 'arguments': {'uri': 'tcp:192.168.0.34:8888' } } And two VM with cash Primary: {"timestamp": {"seconds": 1520763655, "microseconds": 511415}, "event": "= RESUME"} [1] 329 segmentation fault sudo /usr/local/bin/qemu-system-x86_64 -bo= ot c -enable-kvm -m 2048 -smp 2 -qm Secondary: {"timestamp": {"seconds": 1520763655, "microseconds": 510907}, "event": "= RESUME"} [1] 367 segmentation fault sudo /usr/local/bin/qemu-system-x86_64 -bo= ot c -enable-kvm -m 2048 -smp 2 -qm To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1754542/+subscriptions