This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] VMX device models not getting created anymore?

To: Mike Wray <mike.wray@xxxxxx>
Subject: Re: [Xen-devel] VMX device models not getting created anymore?
From: Arun Sharma <arun.sharma@xxxxxxxxx>
Date: Thu, 16 Jun 2005 10:35:41 -0700
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 16 Jun 2005 17:34:51 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42B13EC8.3090008@xxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D2821A6@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <42B03B76.7010701@xxxxxx> <42B060BA.3020404@xxxxxxxxx> <42B13EC8.3090008@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
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.

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.


Xen-devel mailing list