From: Arun Sharma <arun.sharma@intel.com>
To: Mike Wray <mike.wray@hp.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: VMX device models not getting created anymore?
Date: Fri, 17 Jun 2005 12:28:46 -0700 [thread overview]
Message-ID: <42B3246E.3000706@intel.com> (raw)
In-Reply-To: <42B2CB0B.1000502@hp.com>
Mike Wray wrote:
> Compared to which field is it off by 1?
> The VMX code creates its own event channel using
> channel.eventChannel(), which will
> allocate new ports. Possibly it should be reusing the existing control
> channel port
> instead? This might account for the off-by-one as ports are allocated
> sequentially.
That seems to be the problem. If I add some logging, I see:
[2005-06-17 12:06:07 xend] INFO (channel:32) created event channel:
<EventChannel dom1:0:19 dom2:5:2>
[2005-06-17 12:06:07 xend] INFO (channel:32) created event channel:
<EventChannel dom1:0:20 dom2:5:3>
The first one is created here:
File "/usr/lib/python/xen/xend/XendDomain.py", line 276, in domain_create
dominfo = XendDomainInfo.create(self.dbmap, config)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 159, in create
vm.construct(config)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 501, in construct
self.construct_image()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 547, in
construct_image
self.create_channel()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 680, in
create_channel
self.store_channel = self.eventChannel("store_channel")
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 674, in
eventChannel
return EventChannel.restoreFromDB(db, 0, self.id)
File "/usr/lib/python/xen/xend/server/channel.py", line 59, in
restoreFromDB
evtchn = cls.interdomain(dom1, dom2, port1=port1, port2=port2)
The second is created here:
File "/usr/lib/python/xen/xend/XendDomain.py", line 276, in domain_create
dominfo = XendDomainInfo.create(self.dbmap, config)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 159, in create
vm.construct(config)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 502, in construct
self.configure()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 884, in configure
self.create_devices()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 704, in
create_devices
self.image.createDeviceModel()
File "/usr/lib/python/xen/xend/image.py", line 300, in createDeviceModel
self.device_channel = channel.eventChannel(0, self.vm.getDomain())
File "/usr/lib/python/xen/xend/server/channel.py", line 116, in
eventChannel
return EventChannel.interdomain(dom1, dom2, port1=port1, port2=port2)
Things get more interesting, because self.device_channel['port1'] for
the second channel returns 19 instead of 20.
Are there assumptions in the code that there must be only one
interdomain event channel between two domains?
-Arun
next prev parent reply other threads:[~2005-06-17 19:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 21:48 VMX device models not getting created anymore? Ian Pratt
2005-06-15 14:30 ` Mike Wray
2005-06-15 17:09 ` Arun Sharma
2005-06-16 8:56 ` Mike Wray
2005-06-16 17:35 ` Arun Sharma
2005-06-17 13:07 ` Mike Wray
2005-06-17 19:28 ` Arun Sharma [this message]
2005-06-17 20:17 ` Arun Sharma
2005-06-17 21:54 ` cannot concatenate 'str' and 'Nonetype' object with creating domain Jurgen Stroo
2005-06-17 22:16 ` Jurgen Stroo
2005-06-20 11:13 ` VMX device models not getting created anymore? Mike Wray
2005-06-21 21:01 ` Arun Sharma
2005-06-22 8:34 ` Mike Wray
2005-06-20 10:52 ` Mike Wray
-- strict thread matches above, loose matches on Subject: below --
2005-06-15 17:12 Ian Pratt
2005-06-15 18:02 ` Arun Sharma
2005-06-10 21:22 Arun Sharma
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=42B3246E.3000706@intel.com \
--to=arun.sharma@intel.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=mike.wray@hp.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.