On 11/2/2018 2:45 PM, Chris Friesen wrote:
On 11/2/2018 11:51 AM, Dr. David Alan Gilbert wrote:
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
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
On 11/2/2018 1:51 AM, Alex Bennée wrote:
Chris Friesen writes:
Hi all,
I have an odd situation which occurs very infrequently and I'm hoping
to get some advice on how to debug. Apologies for the length of this
message, I tried to include as much potentially useful information as
possible.
* Chris Friesen (chris.frie...@windriver.com) wrote:
> On 11/2/2018 10:55 AM, Alex Bennée wrote:
> >
> > Chris Friesen writes:
> > > Given the "not initialized" message on the console, I wasn't sure
> > > whether the kernel had even started yet.
> >
> > There will be a lot that happens between
On 11/2/2018 10:55 AM, Alex Bennée wrote:
Chris Friesen writes:
Given the "not initialized" message on the console, I wasn't sure
whether the kernel had even started yet.
There will be a lot that happens between the kernel decompressing and
some sort of video hardware output being started.
Chris Friesen writes:
> On 11/2/2018 1:51 AM, Alex Bennée wrote:
>>
>> Chris Friesen writes:
>>
>>> Hi all,
>>>
>>> I have an odd situation which occurs very infrequently and I'm hoping
>>> to get some advice on how to debug. Apologies for the length of this
>>> message, I tried to include
Chris Friesen writes:
> Hi all,
>
> I have an odd situation which occurs very infrequently and I'm hoping
> to get some advice on how to debug. Apologies for the length of this
> message, I tried to include as much potentially useful information as
> possible.
>
> In the context of an
Hi all,
I have an odd situation which occurs very infrequently and I'm hoping to
get some advice on how to debug. Apologies for the length of this
message, I tried to include as much potentially useful information as
possible.
In the context of an OpenStack compute node I have a qemu guest
