From: Launchpad Bug Tracker <1626596@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1626596] Re: Lockup with vhost network
Date: Tue, 12 Jan 2021 04:17:25 -0000 [thread overview]
Message-ID: <161042504595.10246.371068433228056957.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20160922144807.17427.95239.malonedeb@wampee.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
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:
Expired
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=scsi -device scsi-hd,drive=hd -drive
if=none,id=hd,cache=writeback,aio=native,format=raw,file=xxxx.img,discard=unmap
,detect-zeroes=unmap -device virtio-net-pci,netdev=net0,mac=xxxx
-netdev tap,vhost=on,id=net0,script=xxxx.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
prev parent reply other threads:[~2021-01-12 4:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 14:48 [Qemu-devel] [Bug 1626596] [NEW] Lockup with vhost network rm
2020-11-12 13:12 ` [Bug 1626596] " Thomas Huth
2021-01-12 4:17 ` Launchpad Bug Tracker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161042504595.10246.371068433228056957.malone@loganberry.canonical.com \
--to=1626596@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.