From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Smith Subject: Re: Time stopped Date: Thu, 13 Oct 2005 12:21:55 -0700 Message-ID: <87ll0x8bos.fsf@us.ibm.com> References: <1129230385.5979.55.camel@dbarrera_tp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <1129230385.5979.55.camel@dbarrera_tp> (David F. Barrera's message of "Thu, 13 Oct 2005 14:06:25 -0500") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: David F Barrera Cc: Ian.Pratt@cl.cam.ac.uk, Xen Developers List-Id: xen-devel@lists.xenproject.org > x335b:/tmp/logs/xm-test # xm list > Name ID Mem(MiB) CPU VCPUs State Time(s) > Domain-0 0 495 - 4 r----- 96.5 > 11_create_0 73 16 3 1 -b---- 0.3 > x335b:/tmp/logs/xm-test # This is not a surprising place to fail. Test 10_create tries to create and destroy a bunch of domains really fast. That used to reboot people's machines. Test 11_create tries to create a whole bunch of concurrent DomUs, but it looks like it isn't getting very far. Does 'top' show anything (like xenconsoled) pegging the CPU, or does 'xm top' show the 11_create_0 domain taking over the system? Can you reliably put the system into this state right between tests 10_create and 11_create? -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com