From: Jim Fehlig <jfehlig@novell.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] fix 3.3-testing c/s 18434
Date: Wed, 08 Oct 2008 11:47:49 -0600 [thread overview]
Message-ID: <48ECF245.4080707@novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
c/s 18434 in xen-3.3-testing has a hunk that changes gatherDom() to
_gatherDom() in tools/python/xen/xend/image.py. There is no such
method, thus simple "xm list" fails
jfehlig4: # xm li
Error: _gatherDom
Usage: xm list [options] [Domain, ...]
..
Trivial fix attached. BTW, I don't see this patch in xen-unstable. Why
is this only in xen3.3-testing?
Thanks,
Jim
Signed-off-by: Jim Fehlig <jfehlig@novell.com>
[-- Attachment #2: 3.3-testing-18434-fix.patch --]
[-- Type: text/x-patch, Size: 710 bytes --]
diff -r e0e17216ba70 tools/python/xen/xend/image.py
--- a/tools/python/xen/xend/image.py Thu Oct 02 10:42:38 2008 +0100
+++ b/tools/python/xen/xend/image.py Wed Oct 08 11:39:05 2008 -0600
@@ -502,7 +502,7 @@ class ImageHandler:
if fifo_fd >= 0:
self._openSentinel(sentinel_path_fifo)
os.close(fifo_fd)
- self.pid = self.vm._gatherDom(('image/device-model-pid', int))
+ self.pid = self.vm.gatherDom(('image/device-model-pid', int))
log.debug("%s device model rediscovered, pid %s sentinel fifo %s",
name, self.pid, sentinel_path_fifo)
self.sentinel_thread = thread.start_new_thread(self._sentinel_watch,())
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2008-10-08 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 17:47 Jim Fehlig [this message]
2008-10-08 18:06 ` [PATCH] fix 3.3-testing c/s 18434 Keir Fraser
2008-10-09 22:02 ` Jim Fehlig
2008-10-10 7:49 ` Keir Fraser
2008-10-10 19:09 ` Jim Fehlig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48ECF245.4080707@novell.com \
--to=jfehlig@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.