This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] crashes

I get nothing on the console, just a complete hang with 'noreboot' specified. It actually hangs now when idle.

From: James Harper
Sent: Mon 2/08/2004 10:26 AM
To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Cc: Ian Pratt
Subject: RE: [Xen-devel] crashes

it's definitely rebooting fairly shortly after i start testing it with disk and network activity. I've added noreboot and will inspect the console when it crashes next.

From: James Harper
Sent: Mon 2/08/2004 9:37 AM
To: Ian Pratt
Cc: Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] crashes

Last night I tried a bk pull and noticed some errors which meant nothing was applying, so I was missing a few changesets. I cloned a brand new tree and built a new set of images, and now i'm back to having it spontaneously reboot with no error messages.

From: Ian Pratt
Sent: Sat 31/07/2004 9:48 PM
To: James Harper
Cc: Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxxxx; Ian.Pratt@xxxxxxxxxxxx
Subject: Re: [Xen-devel] crashes

> It looked like everything was okay except for these messages in DOM0:
> (file=main.c, line=270) Failed MMU update transferring to DOM1
> (file=main.c, line=270) Failed MMU update transferring to DOM1
> but then I tried to start another domain and got this:
> Using config file /etc/xen/mail2
> Error: Internal Server Error
> so it looks like something is still wrong somewhere...

Is this with or without the 'better blk dev fix' changeset backed
The "Failed MMU update" messages are very interesting, and I've
never seen them before -- xen is refusing to transfer the page to
dom1 for some reason. Please can you try doing the same with a
debug=y build of Xen. Xen should tell us a bit more about why
it's refusing the request. 

What workload are you running when this happens? You seem to have
a real talent for provoking hard to reproduce bugs ;-)

It might be moderately interesting to see the traceback from
xend to see which stage of creating the new domain failed.

Further, once it gets in to this state, it would be good to try
shuting down or destroying the other domains one by one, doing an
'xm list' after each stage. If one of the domains hangs around
after a 'destroy' it's a sign there's been an inconsistency. 

<Prev in Thread] Current Thread [Next in Thread>