From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A5C7FC432C0 for ; Wed, 27 Nov 2019 02:52:29 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7A03320722 for ; Wed, 27 Nov 2019 02:52:29 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7A03320722 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bugs.launchpad.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:60732 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZnRM-0000Qy-NS for qemu-devel@archiver.kernel.org; Tue, 26 Nov 2019 21:52:28 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:54556) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZnPq-00080G-Lf for qemu-devel@nongnu.org; Tue, 26 Nov 2019 21:50:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZnPp-000720-BU for qemu-devel@nongnu.org; Tue, 26 Nov 2019 21:50:54 -0500 Received: from indium.canonical.com ([91.189.90.7]:47878) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iZnPp-00071X-5z for qemu-devel@nongnu.org; Tue, 26 Nov 2019 21:50:53 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1iZnPm-0000o6-LO for ; Wed, 27 Nov 2019 02:50:50 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 4B9532E80CC for ; Wed, 27 Nov 2019 02:50:50 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 27 Nov 2019 02:38:21 -0000 From: lee <1754542@bugs.launchpad.net> To: qemu-devel@nongnu.org X-Launchpad-Notification-Type: bug X-Launchpad-Bug: product=qemu; status=Fix Released; importance=Undecided; assignee=None; X-Launchpad-Bug-Tags: colo X-Launchpad-Bug-Information-Type: Public X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Bug-Commenters: chao.wang lisuiheng zhangckid X-Launchpad-Bug-Reporter: lee (lisuiheng) X-Launchpad-Bug-Modifier: lee (lisuiheng) References: <152056405865.7543.8980677605113063936.malonedeb@wampee.canonical.com> Message-Id: <157482230188.6492.6320869898088738043.malone@gac.canonical.com> Subject: [Bug 1754542] Re: colo: vm crash with segmentation fault X-Launchpad-Message-Rationale: Subscriber (QEMU) @qemu-devel-ml X-Launchpad-Message-For: qemu-devel-ml Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="c597c3229eb023b1e626162d5947141bf7befb13"; Instance="production-secrets-lazr.conf" X-Launchpad-Hash: e82a3b42a6c106c3f425351cafa5861356aa480f X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 91.189.90.7 X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Bug 1754542 <1754542@bugs.launchpad.net> Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" Hi Zhang Chen , I try colo follow https://wiki.qemu.org/Features/COLO. It work well. But disk performance slow. Only host performance 10%. = Can virtio blk supported by current colo? Or is there any other way to improve disk performance. Thanks Zhang Chen -- = 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: Fix Released 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