From: Christian Limpach <christian.limpach@gmail.com>
To: Arun Sharma <arun.sharma@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Fix TypeError when starting VMX domains
Date: Tue, 9 Aug 2005 12:00:40 +0100 [thread overview]
Message-ID: <3d8eece20508090400634ddb30@mail.gmail.com> (raw)
In-Reply-To: <42F7DEDA.4000400@intel.com>
On 8/8/05, Arun Sharma <arun.sharma@intel.com> wrote:
>
> The attached patch fixes this traceback:
When does this happen? It seems that the fix will only hide the real
cause of the failure and I'd rather fix the underlying bug. It's odd
that we have initialized the store_channel but not figured out what
the store_mfn is.
christian
> Traceback (most recent call last):
> File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 510, in construct
> self.construct_image()
> File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 574, in
> construct_image
> self.store_channel)
> File "/usr/lib/python/xen/xend/xenstore/xsobj.py", line 310, in
> introduceDomain
> log.info("DBMap>introduceDomain> %d %d %s %s" %(dom, page, evtchn,
> path))
> TypeError: int argument required
>
> --- a/tools/python/xen/xend/XendDomainInfo.py Mon Aug 8 20:22:16 2005
> +++ b/tools/python/xen/xend/XendDomainInfo.py Mon Aug 8 15:00:19 2005
> @@ -239,7 +239,7 @@
>
> self.channel = None
> self.store_channel = None
> - self.store_mfn = None
> + self.store_mfn = 0
> self.controllers = {}
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-08-09 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 22:38 [PATCH] Fix TypeError when starting VMX domains Arun Sharma
2005-08-09 11:00 ` Christian Limpach [this message]
2005-08-09 20:46 ` Arun Sharma
2005-08-09 23:42 ` Arun Sharma
2005-08-10 8:49 ` Christian Limpach
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=3d8eece20508090400634ddb30@mail.gmail.com \
--to=christian.limpach@gmail.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=arun.sharma@intel.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.