On 19/08/2011 13:56, Konrad Rzeszutek Wilk wrote:
> On Fri, Aug 19, 2011 at 11:22:15AM +0100, Anthony Wright wrote:
>> On 03/08/2011 16:28, Konrad Rzeszutek Wilk wrote:
>>> On Fri, Jul 29, 2011 at 08:53:02AM +0100, Anthony Wright wrote:
>>>> I've just upgraded to xen 4.1.1 with a stock 3.0 kernel on dom0 (with
>>>> the vga-support patch backported). I can't get my DomU's to work due to
>>>> the phy disks and vifs timing out in DomU and looking through my logs
>>>> this morning I'm getting a consistent kernel bug report with xen
>>>> mentioned at the top of the stack trace and vifdisconnect mentioned on
>>> Yikes! Ian any ideas what to try?
>>>
>>> Anthony, can you compile the kernel with debug=y and when this happens
>>> see what 'xl dmesg' gives? Also there is also the 'xl debug-keys g' which
>>> should dump the grants in use.. that might help a bit.
>> I've compiled a 3.0.1 kernel with CONFIG_DEBUG=Y (a number of other
>> config values appeared at this point, and I took defaults for them).
>>
>> The output from /var/log/messages & 'xl dmesg' is attached. There was no
>> output from 'xl debug-keys g'.
> Ok, so I am hitting this too - I was hoping that the patch from Stefano
> would have fixed the issue, but sadly it did not.
>
> Let me (I am traveling right now) see if I can come up with an internim
> solution until Ian comes with the right fix.
>
On different hardware with the same software I'm also getting problems
starting DomUs, but this time the error is different. I've attached a
copy of the xl console output, but basically the server hang at
"Mount-cache hash table entries: 512". Again the VM is paravirtualised,
and again I get a qemu-dm process for it.

The references to this message are normally related to memory issues,
but the server has only 1000M of ram, so can't see it causing too much
of a problem.

Is this related to the other problems I'm seeing or completely separate?

thanks,

Anthony