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/
Home Products Support Community News


[Xen-bugs] [Bug 709] New: [XEN-HVM] xm-test hangs during enforce_dom0_cp

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 709] New: [XEN-HVM] xm-test hangs during enforce_dom0_cpus test
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 25 Jul 2006 08:10:19 -0700
Delivery-date: Tue, 25 Jul 2006 08:11:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: [XEN-HVM] xm-test hangs during enforce_dom0_cpus test
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: HVM
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ricardoz@xxxxxxxxxx
                CC: niv@xxxxxxxxxx, pl@xxxxxxxxxx, dbarrera@xxxxxxxxxx,

dom0 OS: sles9-sp3
system: x460
cpus: 4 dual core (VTI)

Problem Description:

I downloaded the latest xen-unstable tree and compiled it and rebooted system.
After the reboot, I went ahead and started an HVM xm-test run. Everything
looked good when it started. After 1hr or so, I checked back on my test run and
found out that it is getting stuck in the enforce_dom0_cpus test. This happens
in both 32bit and 64bit.

I added debug flag to xm-test ( Console.py ) to get more info about it and
found the following:

NOTE: I had to Ctrl-c out of the test to get the debug info.

[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()
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 

I tracked it down to a piece of code in commands.py from python package. Here
is the piece of code it is getting stuck in:

def getstatusoutput(cmd):
    """Return (status, output) of executing cmd in a shell."""
    import os
    pipe = os.popen('{ ' + cmd + '; } 2>&1', 'r')
    text = pipe.read()    <------------------------------------- HERE
    sts = pipe.close()
    if sts is None: sts = 0
    if text[-1:] == '\n': text = text[:-1]
    return sts, text

Execution does not go past that line at all. Something is blocking the

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list