Xen3 DomU spins 100% busy during console access

   On Dec 4, 10:54, david l goodrich wrote:
   > Subject: Re: Xen3 DomU spins 100% busy during
console access
   > On Mon, Dec 04, 2006 at 05:52:04PM +0100, Manuel
Bouyer wrote:
   > > On Mon, Dec 04, 2006 at 10:37:28AM -0600, david
l goodrich wrote:
   > > > > The right fix is:
   > > > > http://xenbits.xensource.com/xen-unstable.hg?cs=3D
7c994d80049c
   > > > >
   > > > > and it's part of xen-3.0.3, no patch
needed.

I see.  Thanks.  I misunderstood since DomU locked up when I
pasted large amount of data into a console recently.

   > > That would be an issue in the domU's console
code I guess. Is it a
   > > NetBSD or Linux domU ?
   > >
   > NetBSD 3.1

NetBSD 4.99.3 and NetBSD 4.99.4 too.

Oh, you are right.  It looks like DomU issue.  SUSE Linux
10.1 (2.6.16.21-0.25-xen) doesn't lock up.

-- Kazushi

> NetBSD 4.99.3 and NetBSD 4.99.4 too.
>
> Oh, you are right.  It looks like DomU issue.  SUSE
Linux
> 10.1 (2.6.16.21-0.25-xen) doesn't lock up.

And I think I mentioned this but my other domUs, using the
same xen domU 
kernel don't seem to have the issue. Well it hasn't occurred
yet during 
normal use, so I could be completely off base.

Manuel, is there something i386 specific that could cause
this? I have know 
idea how xen interfaces with a domU and what resources are
accessed.

Sarton

Hi all!

Funny, because I seem to have the same problem (Debian Sarge
as dom0 and
NetBSD 3.1 as domU). Sometimes my NetBSD domU completely
locked up. If I
remember correctly it happened whenever I performed
operations with plenty
of text output, such as a CVS update on pkgsrc or building a
package with
lots of dependencies.
Whenever the domU locked up I had to destroy it with xm
destory, because
it did not respond to anything anymore.

Yours
Lars

> NetBSD 4.99.3 and NetBSD 4.99.4 too.
>
> Oh, you are right.  It looks like DomU issue.  SUSE
Linux
> 10.1 (2.6.16.21-0.25-xen) doesn't lock up.

> NetBSD 4.99.3 and NetBSD 4.99.4 too.
>
> Oh, you are right.  It looks like DomU issue.  SUSE
Linux
> 10.1 (2.6.16.21-0.25-xen) doesn't lock up.

And I think I mentioned this but my other domUs, using the
same xen domU 
kernel don't seem to have the issue. Well it hasn't occurred
yet during 
normal use, so I could be completely off base.

Manuel, is there something i386 specific that could cause
this? I have know 
idea how xen interfaces with a domU and what resources are
accessed.

Sarton

Hi all!

Funny, because I seem to have the same problem (Debian Sarge
as dom0 and
NetBSD 3.1 as domU). Sometimes my NetBSD domU completely
locked up. If I
remember correctly it happened whenever I performed
operations with plenty
of text output, such as a CVS update on pkgsrc or building a
package with
lots of dependencies.
Whenever the domU locked up I had to destroy it with xm
destory, because
it did not respond to anything anymore.

Yours
Lars

> NetBSD 4.99.3 and NetBSD 4.99.4 too.
>
> Oh, you are right.  It looks like DomU issue.  SUSE
Linux
> 10.1 (2.6.16.21-0.25-xen) doesn't lock up.