From: Thomas Huth <1626596@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1626596] Re: Lockup with vhost network
Date: Thu, 12 Nov 2020 13:12:10 -0000 [thread overview]
Message-ID: <160518673044.28685.9751325605920202665.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20160922144807.17427.95239.malonedeb@wampee.canonical.com
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
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:
Incomplete
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
next prev parent reply other threads:[~2020-11-12 13:26 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 ` Thomas Huth [this message]
2021-01-12 4:17 ` [Bug 1626596] " Launchpad Bug Tracker
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=160518673044.28685.9751325605920202665.malone@chaenomeles.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.