From: Launchpad Bug Tracker <1888417@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1888417] Re: Latest QEMU git build on Arch linux causes PCI Passthrough host to hang on guest reboot.
Date: Wed, 07 Jul 2021 04:17:17 -0000 [thread overview]
Message-ID: <162563143733.23671.11649281791608338015.malone@loganberry.canonical.com> (raw)
In-Reply-To: 159535256686.7592.12361820079263274205.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/1888417
Title:
Latest QEMU git build on Arch linux causes PCI Passthrough host to
hang on guest reboot.
Status in QEMU:
Expired
Bug description:
Current Arch linux release, up-to-date as of 7/21/2020.
Running a windows 7 virtual machine (also happens with windows 10,
possibly more OSes), with an nvidia GTX 1060 passthrough, if the VM is
attempted to be restarted, either through the guest interface, or by
libvirt's gui interface "Virtual Machine Manager", it hangs in a
"paused" state once the VM shutsdown, and just before the reboot can
take place. A force-stop of the VM allows the VM to be properly
booted without any disk error checks, alluding to a clean shutdown,
but failed reboot. The VM can be properly shutdown using the guests
shutdown function, or the libvirt manager shutdown, without any hangs.
Reverting to Arch stable build QEMU 5.0.0-7 fixes the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1888417/+subscriptions
prev parent reply other threads:[~2021-07-07 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 17:29 [Bug 1888417] [NEW] Latest QEMU git build on Arch linux causes PCI Passthrough host to hang on guest reboot Jason
2021-05-07 4:39 ` [Bug 1888417] " Thomas Huth
2021-07-07 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=162563143733.23671.11649281791608338015.malone@loganberry.canonical.com \
--to=1888417@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).