From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46904) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bn5Pe-0003m9-PL for qemu-devel@nongnu.org; Thu, 22 Sep 2016 10:55:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bn5PY-0000QM-ID for qemu-devel@nongnu.org; Thu, 22 Sep 2016 10:55:45 -0400 Received: from indium.canonical.com ([91.189.90.7]:42775) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bn5PY-0000Q6-Aa for qemu-devel@nongnu.org; Thu, 22 Sep 2016 10:55:40 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1bn5PX-0005vq-HA for ; Thu, 22 Sep 2016 14:55:39 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 557B62E80CA for ; Thu, 22 Sep 2016 14:55:39 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 22 Sep 2016 14:48:07 -0000 From: rm <1626596@bugs.launchpad.net> Reply-To: Bug 1626596 <1626596@bugs.launchpad.net> Sender: bounces@canonical.com Message-Id: <20160922144807.17427.95239.malonedeb@wampee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1626596] [NEW] Lockup with vhost network List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Public bug reported: After using Qemu in this configuration successfully for quite a while, I ch= anged two things: - moved the VM from a 8-core 4GHz host to a slower 2-core 1.6 Ghz machine - upgraded qemu from 2.1 to 2.5 and almost immediately (in a couple hours) got hit with a vhost-related lockup. QEMU command line is: qemu-system-x86_64 -enable-kvm -daemonize -monitor unix:./monitor,server,nowait -cpu host -M q35 -balloon virtio -device virtio-scsi-pci,id=3Dscsi -device scsi-hd,drive=3Dhd -drive if=3Dnone,id=3Dhd,cache=3Dwriteback,aio=3Dnative,format=3Draw,file=3Dxxxx.i= mg,discard=3Dunmap ,detect-zeroes=3Dunmap -device virtio-net-pci,netdev=3Dnet0,mac=3Dxxxx -net= dev tap,vhost=3Don,id=3Dnet0,script=3Dxxxx.sh -usbdevice tablet -smp 2 -m 512 -= vnc xxxx:yz VM was running fine, except no network traffic was passed from/to it. Shutting down the VM, it hung at "Will now halt." The QEMU process was unkillable, so the only choice was to sysrq-b the entire box. dmesg with sysrq-w attached. ** Affects: qemu Importance: Undecided Status: New ** Attachment added: "dmesg with sysrq-w" https://bugs.launchpad.net/bugs/1626596/+attachment/4746283/+files/vhost= .txt -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1626596 Title: Lockup with vhost network Status in QEMU: New Bug description: After using Qemu in this configuration successfully for quite a while, I = changed two things: - moved the VM from a 8-core 4GHz host to a slower 2-core 1.6 Ghz machine - upgraded qemu from 2.1 to 2.5 and almost immediately (in a couple hours) got hit with a vhost- related lockup. QEMU command line is: qemu-system-x86_64 -enable-kvm -daemonize -monitor unix:./monitor,server,nowait -cpu host -M q35 -balloon virtio -device virtio-scsi-pci,id=3Dscsi -device scsi-hd,drive=3Dhd -drive if=3Dnone,id=3Dhd,cache=3Dwriteback,aio=3Dnative,format=3Draw,file=3Dxxxx= .img,discard=3Dunmap ,detect-zeroes=3Dunmap -device virtio-net-pci,netdev=3Dnet0,mac=3Dxxxx -netdev tap,vhost=3Don,id=3Dnet0,script=3Dxxxx.sh -usbdevice tablet -smp 2 -m 512 -vnc xxxx:yz VM was running fine, except no network traffic was passed from/to it. Shutting down the VM, it hung at "Will now halt." The QEMU process was unkillable, so the only choice was to sysrq-b the entire box. dmesg with sysrq-w attached. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1626596/+subscriptions