From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Wray Subject: Re: VMX device models not getting created anymore? Date: Fri, 17 Jun 2005 14:07:23 +0100 Message-ID: <42B2CB0B.1000502@hp.com> References: <42B03B76.7010701@hp.com> <42B060BA.3020404@intel.com> <42B13EC8.3090008@hp.com> <42B1B86D.6090503@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <42B1B86D.6090503@intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Arun Sharma Cc: Ian Pratt , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Arun Sharma wrote: > Mike Wray wrote: > >>> I sent a patch: vmx-device-models-py.patch to the list to do just >>> this, but the event channel numbers seem to be off by one for some >>> reason (please see comments inside the patch). >> >> >> >> OK, I see the patch. What makes you think the event channel port >> numbers are off? Is it possible that it should be using port2 instead >> of port1? > > > If I print self.device_channel.port1 and compare it to the output of > > # xm list --long > > It's off by one and device models don't get any events from the VMX domain. 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. > > When I add the -1, things work ok i.e. device models do receive events > from the VMX domain. > > port1 = dom0 end of the event channel. That's what the device models > listen to. port2 = hypervisor/vmx domain end of the event channel. Hope this helps, Mike