Re: [Xen-devel] Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG

[Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx>]

On Wed, Oct 3, 2012 at 7:45 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Wed, Oct 03, 2012 at 12:21:47PM +0300, Valtteri Kiviniemi wrote:
>>    Hi,
>>
>>    I disabled NUMA and upgraded to Xen 4.2.0. Windows domU starts now fine
>>    and I cant anymore reproduce the hotplug problems. VNC output is still
>>    just black screen and it actually crashes the the whole VNC client when
>>    after a few seconds. RealVNC just shuts itself down and tightvnc crashes.
>>
>
>
> Valtteri: Can you actually paste the names of the .config options you disabled
> and got the dom0 kernel working without crashes?
>
> Maybe Konrad can comment if the current upstream dom0 kernel is supposed to 
> work
> with NUMA support enabled / compiled in?

There is a patch to actually disable it since we do not provide any
NUMA information
to the guest. And the dom0 has access to extra information (ACPI,
Northbridge, etc)
so it might think to create a NUMA topology and get it wrong.

But his dmesg did not have anything obvious related to NUMA, so  I am
perplexed that
turning that off would have made such a difference.

Valterri - if you just pass 'numa=off' on the Linux command line with
the old kernel
(the one that had the NUMA enabled) does that make it the iput issue go away?


You VNC issue .. does it work if you launch PV guests? Or is it only
for HVM guests?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel