|
From: | Chris Friesen |
Subject: | Re: [Qemu-devel] strange situation, guest cpu thread spinning at ~100%, but display not yet initialized |
Date: | Fri, 2 Nov 2018 14:45:05 -0600 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 |
On 11/2/2018 11:51 AM, Dr. David Alan Gilbert wrote:
This is ringing a bell; if it's actually suck in the BIOS, then please: a) Really make sure all your vCPUs are actually pinned/free on real CPUs b) I suspect it is https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg00470.html
I'm still working on getting the BIOS logs to be emitted to file before kernel startup (I can see them later on, but not right at boot).
Will double-check the actual affinity next time I reproduce it (testcase has been going all day with no luck so far).
so the fix is Fam's 'aio: Do aio_notify_accept only during blocking aio_poll'. I see you're running the qemu-kvm-ev from centos, if I read the version tea-leaves right, then I think that patch is in the 2.10.0-21.el7_5.7.1 package I can see.
It looks like we do not have this fix in our code, will definitely be giving it a try.
Thanks, Chris
[Prev in Thread] | Current Thread | [Next in Thread] |