On Wed, 2006-05-24 at 09:46 -0600, Alex Williamson wrote:
> On Tue, 2006-05-23 at 23:48 -0600, Alex Williamson wrote:
> > It appeared to be stuck in the "-b----" state as shown by xm list,
> > but let me do some verification tomorrow. Thanks for testing this. I'm
> > running UP dom0 + 4-way SMP domU + UP domVTI on an 8 thread (4 core)
> > system. Thanks,
>
> Actually, running networking in domU concurrently accelerates the
> problem, but is not required. I hit it again with only a domVTI
> running. I'm pulling a 512MB empty file from another server and writing
> it to /dev/null using wget. At some point it just stops and xm list
> reports the domain as blocked. There's nothing in xend.log or
> xend-debug.log to indicate something went bad. The qemu-dm process has
> select listed in it's wait channel, so seems like it's ok. Thanks,
I hit this again building a kernel in a domVTI (RHEL4U3 guest). I was
only using the network for an ssh login. The build ran for a while,
consumed 3600+ seconds as reported by xm list, but is now stuck in the
blocked state. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|