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-bugs

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

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 709] [XEN-HVM] xm-test hangs during enforce_dom0_cpus test
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 26 Jul 2006 11:35:48 -0700
Delivery-date: Wed, 26 Jul 2006 11:36:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-709-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
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
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=709





------- Comment #4 from harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx  2006-07-26 11:35 
-------
This isn't 100% reproduceable.  Seems to fail on the first few attepmts shortly
after boot but after a bit of playing around I had many successful attempts in
a row.

The command that is hanging is being executed without a timeout and is using a
different mechanism for executing commands than commands which are execured
with a timeout.

There was some discussion in the python docs about deadlocks caused when a
parent process is trying to read from a child process stdout when the child
process is writing to stderr.  This problem might be a similar kind of
deadlock.

On the other hand it's testing th cpu hotplug function wihch is experimental so
there might be a kernel issue.

I think it would be good to have a timeout on all commands and tried to
implement this today by reusing the existing code.

Unfortunately the existing code uses string.split() to split the command into
an argument vector and this doesn't handle arguments which are quoted strings
and some of the command lines passed to old code did have quoted strings so
this didn't work.  There doesn't seem to be a python equivalent of wordexp().

Implementing a timeout would allow the remaining tests to execute.

Need to do some more work to characterize the problem before it will be
possible to fix this failing test.


-- 
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