From: webczat <webczat_200@poczta.onet.pl>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1738507] Re: qemu sometimes stuck when booting windows 10
Date: Sat, 16 Dec 2017 01:08:50 -0000 [thread overview]
Message-ID: <151338653018.18527.15553429081686895415.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 151338646328.26229.15531211351993382335.malonedeb@wampee.canonical.com
** Attachment added: "log of libvirt's domain containing qemu command line arguments passed"
https://bugs.launchpad.net/qemu/+bug/1738507/+attachment/5023251/+files/libvirt-log.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/1738507
Title:
qemu sometimes stuck when booting windows 10
Status in QEMU:
New
Bug description:
I am using qemu-2.10.1, or actually libvirt, to create a virtual machine, running microsoft windows 10 pro operating system.
It installed fine and was actually working, however sometimes when trying to boot the vm, the whole boot process gets stuck.
For some reason, it seemed to happen only when enough physical memory is taken so that, when booting a windows vm that has 4gb of available ram, host starts swapping some other processes. It is not always happening there, but often it happens, and I do not remember seeing any case of this happening when not swapping, maybe a kind of a timing issue?
When this happens, I usually try to hard reset the machine by libvirt reset command or equivalent system_reset on qemu monitor, however the whole reset does not happen, and the command is a noop. That makes me think it is a qemu bug, not windows refusing operation. At the time of this event, qemu monitor and spice server are working correctly, are not stuck, and even doing things like system reset does not result in a monitor hang. It is also possible to quit qemu normally.
I tried to workaround the bug by guessing what may cause it. Switched from bios to uefi, changed virtio-scsi to ahci temporarily, and disabled virtio-balloon in case it would be buggy, with no visible change.
I will attach a libvirt log, because it contains qemu command line. I will also attach an example qemu backtrace.
From what i know, both vcpu threads are working normally, at least none of them is stuck in a vcpu, nor deadlocked, etc. So backtrace could be different each time I tried to get it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1738507/+subscriptions
next prev parent reply other threads:[~2017-12-16 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 1:07 [Qemu-devel] [Bug 1738507] [NEW] qemu sometimes stuck when booting windows 10 webczat
2017-12-16 1:08 ` webczat [this message]
2020-11-10 18:02 ` [Bug 1738507] " Thomas Huth
2021-01-10 4:17 ` 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=151338653018.18527.15553429081686895415.malone@chaenomeles.canonical.com \
--to=webczat_200@poczta.onet.pl \
--cc=1738507@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.