qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Guest unresponsive after Virtqueue size exceeded error


From: Fernando Casas Schössow
Subject: Re: [Qemu-devel] Guest unresponsive after Virtqueue size exceeded error
Date: Wed, 21 Jun 2017 12:19:11 +0000

Hi Ladi,

Sorry for the delay in my reply.
I will leave the host kernel alone for now then.
For the last 15 hours or so I'm running memtest86+ on the host. So far so good. 
Two passes no errors so far. I will try to leave it running for at least 
another 24hr and report back the results. Hopefully we can discard the memory 
issue at hardware level.

Regarding KSM, that will be the next thing I will disable if after removing the 
balloon device guests still crash.

About leaving a guest in a failed state for you to debug it remotely, that's 
absolutely an option. We just need to coordinate so I can give you remote 
access to the host and so on. Let me know if any preparation is needed in 
advance and which tools you need installed on the host.

Once I again I would like to thank you for all your help and your great 
disposition!

Cheers,

Fer

On mar, jun 20, 2017 at 9:52 , Ladi Prosek <address@hidden> wrote:
The host kernel is less likely to be responsible for this, in my opinion. I'd 
hold off on that for now.
And last but not least KSM is enabled on the host. Should I disable it?
Could be worth the try.
Following your advice I will run memtest on the host and report back. Just as a 
side comment, the host is running on ECC memory.
I see. Would it be possible for you, once a guest is in the broken state, to 
make it available for debugging? By attaching gdb to the QEMU process for 
example and letting me poke around it remotely? Thanks!



reply via email to

[Prev in Thread] Current Thread [Next in Thread]