http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=824
Summary: Incorrect PTY returned when querying for console for
running DomU in python wrappers
Product: Xen
Version: unstable
Platform: x86
OS/Version: Linux-2.6
Status: NEW
Severity: normal
Priority: P2
Component: Tools
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: derek@xxxxxxxxxxx
Xen version: 3.0.3 32 bit from tarball
OS Version: Fedora Core 6 (with stock Xen ripped out)
Platform: Pentium D 3.2 stepping 2 with 8G on PAE kernel tarball.
Extra: Built an initrd after xen install, starting domains programmatically
using xen.xm.main(['foo', 'create', configFile])
Same code runs no issue on Fedora Core 4, Xen 3.0.1
I am running into a bug which looks like an off by one, but is kind of
inconsistent, when I query xen.lowlevel.xs socket for the console associated to
a given domain id. Inconsistent results (usually, but not always, the PTY
returned is the actual pty + 1). This is hard to replicate too, as it only
seems to happen occasionally for me (happened all day yesterday, but not for a
week before that). Dom0 reboots seem to fix it too.
Code:
DomUID=44 #For example. The id of the dom. From xm list
import xen.lowlevel.xs as xs
sock=xs.xs()
trans=sock.transaction_start()
path=sock.get_domain_path(DomUID)
pty=sock.read(trans,path+'/console/tty')
print "PTY RETURNED IS:",pty
sock.transaction_end(trans)
Large numbers of domains starting and stopping seem to trigger the bug (ie, a
dozen or so DomUs, starting and stopping out of order).
If I am missing some best practice for querying the correct pty, please feel
free to let me know both that I am an idiot, and the correct method ;)
Thanks!
--
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
|
Home