From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Sharma Subject: Re: VMX device models not getting created anymore? Date: Fri, 17 Jun 2005 13:17:42 -0700 Message-ID: <42B32FE6.2090308@intel.com> References: <42B03B76.7010701@hp.com> <42B060BA.3020404@intel.com> <42B13EC8.3090008@hp.com> <42B1B86D.6090503@intel.com> <42B2CB0B.1000502@hp.com> <42B3246E.3000706@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: <42B3246E.3000706@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: Mike Wray Cc: Ian Pratt , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Arun Sharma wrote: > 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: > > [2005-06-17 12:06:07 xend] INFO (channel:32) created event channel: > [..] > > Things get more interesting, because self.device_channel['port1'] for > the second channel returns 19 instead of 20. > This statement is not true. I got confused because the only the first event channel shows up in xm list --long. The real issue is the hard coding in: xen/include/public/io/ioreq.h: #define IOPACKET_PORT 2 This was true before your changes went in. After your changes, xen started sending IOPACKET events on: but the user space device models were listening on: However, if I subtract -1, everything magically works :) I think the quick fix is to redefine IOPACKET_PORT to be 3. Will send a patch to remove the hard coding ASAP. -Arun