[Xen-bugs] [Bug 709] [XEN-HVM] xm-test hangs during enforce_dom0_cpus test

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=709





------- Comment #5 from ricardoz@xxxxxxxxxx  2006-07-26 15:22 -------
Harry,

   I have been looking at the problem more. I have discovered that after
running xm-test and hanging on the enforce test case there is a <defunct>
shell. Here is the output:

"ps -ef"

root      5241  5025  0 16:52 ttyS0    00:00:00 -bash
root      5276     1  0 16:52 ?        00:00:00 xenstored
--pid-file=/var/run/xe
root      5282     1  0 16:52 ?        00:00:00 xenconsoled
root      5660  4586  0 16:53 ?        00:00:00 in.telnetd:
sig-9-76-210-58.mts.
root      5661  5660  0 16:53 ?        00:00:00 login -- root
root      5662  5661  0 16:53 pts/0    00:00:00 -bash
root      5692  5662  0 16:53 pts/0    00:00:00 screen
root      5693  5692  0 16:53 ?        00:00:00 SCREEN
root      5694  5693  0 16:53 pts/1    00:00:00 /bin/bash
root      5746  4586  0 17:05 ?        00:00:00 in.telnetd:
sig-9-76-210-58.mts.
root      5747  5746  0 17:05 ?        00:00:00 login -- root
root      5748  5747  0 17:05 pts/2    00:00:00 -bash
root      5778  5694  0 17:05 pts/1    00:00:00 make check
root      5779  5778  0 17:05 pts/1    00:00:00 /bin/sh -c failcom='exit 1'; 
fo
root      5783  5779  0 17:05 pts/1    00:00:00 make check-am
root      5784  5783  0 17:05 pts/1    00:00:00 make check-TESTS
root      5785  5784  0 17:05 pts/1    00:00:00 /bin/sh -c failed=0; all=0;
xfai
root      5786  5785  0 17:05 pts/1    00:00:00 /usr/bin/python
./01_enforce_dom
root      5827  5786  0 17:05 pts/1    00:00:00 [sh] <defunct>
root      5836     1  0 17:05 pts/1    00:00:00 blktapctrl
root      5838     1  0 17:05 ?        00:00:00 python /usr/sbin/xend start
root      5841  5838  0 17:05 ?        00:00:00 python /usr/sbin/xend start

I then went ahead and killed that process and the following happened:

"kill -9 5786":

/bin/sh: line 1:  5786 Killed                  PYTHONPATH=:../../lib
RD_PATH=../../ramdisk ${dir}$tst
FAIL: 01_enforce_dom0_cpus_basic_pos.test
===================
1 of 1 tests failed
===================
make[2]: *** [check-TESTS] Error 1
make[2]: Leaving directory
`/usr/xen/xen-unstable.hg/tools/xm-test/tests/enforce_dom0_cpus'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory
`/usr/xen/xen-unstable.hg/tools/xm-test/tests/enforce_dom0_cpus'
make: *** [check-recursive] Error 1


So the test finished with errors. OK, next I ran "vcpu-set 0 16" to get my
processors back and rerun the test. After that, the test case runs fine. Just
by reruning it. So, something happens when I kill that <defunct> process that
fixes the problem. I am not sure what it is.

I am attaching a text file that shows the test to completion.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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