Subject: Re: serious glitch on a domU
To: Steven M. Bellovin <smb@cs.columbia.edu>
From: Sarton O'Brien <bsd-xen@roguewrt.org>
List: port-xen
Date: 03/20/2007 11:08:23
On Tue, 20 Mar 2007, Steven M. Bellovin wrote:
> Probably ssh, but I don't remember. However, the machine was well and
> truly dead; I couldn't ping it, it didn't respond on the console, etc.
>
> > I meant to also ask, was dom0 unresponsive or just the domu? What did
> > xm top show while this occurred etc?
>
> The dom0 and the other VMs were fine.
I only ask because there was a bug in the domu console code for some time that
caused the domu to freeze and hog the cpu until it was killed.
Some people didn't see it as you could quite often get passed the post-install
config and switch to ssh before it occurred.
More often than not it happened to me in vi. It's specific to the console
though. Someone figured a way of reproducing the symptom ...
http://mail-index.netbsd.org/port-xen/2006/12/04/0003.html
Hence the reason I asked about xm top. That would indicate if it is related at
all.
Sarton