WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [HVM]xm-test: HANG during enforce_dom0_cpus

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [HVM]xm-test: HANG during enforce_dom0_cpus
From: Rick Gonzalez <rcgneo@xxxxxxxxxx>
Date: Sun, 23 Jul 2006 21:57:29 -0500
Delivery-date: Sun, 23 Jul 2006 19:58:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.4 (Windows/20060516)

I see this problem in 32bit and 64bit. I start xmtest and everything is fine until it gets to enforce_dom0_cpus test case. xm-test just hangs during that test for ever. I enabled debug in Console.py and I get the following output after doing Ctrl-c:

[dom0] Running `/etc/init.d/xend start'
Traceback (most recent call last):
 File "./01_enforce_dom0_cpus_basic_pos.test", line 76, in ?
   status = restartXend()
File "/usr/xen/xen-unstable.hg/tools/xm-test/lib/XmTestLib/Xm.py", line 207, in restartXend
   status, output = traceCommand("/etc/init.d/xend start")
File "/usr/xen/xen-unstable.hg/tools/xm-test/lib/XmTestLib/Test.py", line 99, in traceCommand
   status, output = commands.getstatusoutput(command)
 File "/usr/lib64/python2.3/commands.py", line 59, in getstatusoutput
   tmp = pipe.read()
KeyboardInterrupt
FAIL: 01_enforce_dom0_cpus_basic_pos.test
===================
1 of 1 tests failed
===================
make[2]: *** [check-TESTS] Error 1
make[1]: *** [check-am] Interrupt
make: *** [check-recursive] Interrupt


It seems to be hanging in "pipe.read()" code. It seems to be waiting for something that never happens. It gets in this state after changing the vcpus to 1. The system is fine not crashing or anything like that. dmesg contains the following info:

Breaking affinity for irq 281
Breaking affinity for irq 282
Breaking affinity for irq 283
Breaking affinity for irq 284
Breaking affinity for irq 285
Breaking affinity for irq 286
Breaking affinity for irq 287
Breaking affinity for irq 288
Breaking affinity for irq 289
Breaking affinity for irq 290
Breaking affinity for irq 291
Breaking affinity for irq 292
Breaking affinity for irq 293
Breaking affinity for irq 294
Breaking affinity for irq 295
Breaking affinity for irq 296
Breaking affinity for irq 297
Breaking affinity for irq 298
Breaking affinity for irq 299
Breaking affinity for irq 300
Breaking affinity for irq 301
Breaking affinity for irq 302
Breaking affinity for irq 303


Any ideas?




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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [HVM]xm-test: HANG during enforce_dom0_cpus, Rick Gonzalez <=