[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [unstable-3.4.0-rc4-pre] [2.6.30-rc3-tip] Lockup when starting 192 domains


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Thomas DuBuisson <thomas.dubuisson@xxxxxxxxx>
  • Date: Fri, 15 May 2009 13:18:12 -0700
  • Delivery-date: Fri, 15 May 2009 13:18:46 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=YeEQTQeen4d2owx7EvWmwJMq9V/hGZuZvKMTmQ9f8yWqTPrr8EM9/IfZooIcECfI0K vA58Rp8IrEPRL7+rlSS7J2zdPqzfKTd9CU774hI+YQpQ6LLPFOCQ3R24xw27YFydPYTj C2HJQAST8ZSqefSg4T2+pi3sEEcckh3fCViCw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

All,
Results are based on a pull of todays xen-unstable and about a week
old pull of the xen-tip/master branch of the 2.6.30-rc3 kernel.  I've
also tested with and gotten the same results for the xen-3.3-testing
branch which was pulled some time last week.

Not sure if this is expected, but I just made a couple simple perl
scripts to start up 500 mini-os domains at 6MB each.  The machine (T61
laptop, Core 2 duo, 4GB memory) stopped responding after 192 mini-os
domains started.  By 'stopped responding' I mean the screen froze with
all the windows still displaying but no mouse or keyboard response -
also, the capslock indicator was blinking as though someone used that
as an error indicator.  Finially, I'm not sure if the issue was
triggered once the 192nd domain started or once the script tried to
start the 193rd.

If this is unexpected then I could run a couple more tests with
xen-3.3 branch or another 2.6.30 branch and open a ticket if thats
desired.

Thomas

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.