WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: Xen 3.4 multi-function pass-through tree, isn't working.

To: Simon Horman <horms@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: Xen 3.4 multi-function pass-through tree, isn't working...
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Mon, 20 Jul 2009 15:11:29 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 20 Jul 2009 05:12:16 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0R7iz3JTXyJEtEywVpfCBiv9gf7gBZfVnWX53ogETqo=; b=ULqQdcMIrdQTbI/gA1HGnC0WIsCzIOck9CN/KQXBVGvLNcEpT1Mamwu0poWo6+Qn2k p1exlKoQLWhrkDYcIP84O3ep3gveB3aAGBT359LJu+Jz6709shuk7W5s4VBh+V0fLLAK pUWo0BmKiZJrAByTiHzq2hU8hGDREUefnFnaw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=C01Ru4qDlDG3SIqB8HVxgrgUvVx11kZqMVNNTXAPP3HFEUlqqimHdjUe/iRhyPEKw/ paUc89O7ibq+PKcdW8cTfYiI7e7APTL+u2QTwZGH862WuBppr5nFCPjq//3JQY8RMGdo KpBpaUsMdQQ/SFlmQTaegYH4ya6DnNN8SK0zA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090720120459.GA31891@xxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <8686c3cd0907200403w2a05cf1lfaf25dc8d7eb1821@xxxxxxxxxxxxxx> <20090720120459.GA31891@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
This setup worked with the plain xen 3.4 tree.
No custom stuff in /etc/xen/hvm.

I took a look at the bug, and wrote a workaround for it. Take a look,
and tell if it's ok:

diff -r 776ab1bec020 tools/python/xen/xend/server/pciif.py
--- a/tools/python/xen/xend/server/pciif.py     Sun Jul 19 11:53:11 2009 -0400
+++ b/tools/python/xen/xend/server/pciif.py     Mon Jul 20 08:17:34 2009 -0400
@@ -499,7 +499,13 @@
         num_devs = int(self.readBackend(devid, 'num_devs'))
         new_num_devs = 0
         for i in range(num_devs):
-            state = int(self.readBackend(devid, 'state-%i' % i))
+            try:
+                state = int(self.readBackend(devid, 'state-%i' % i))
+            except:
+                state = xenbusState['Unknown']
+
             if state == xenbusState['Closing']:
                 # Detach I/O resources.
                 pci_dev = parse_pci_name(self.readBackend(devid, 'dev-%i' % i))

What do u think this bug is caused from?

On Mon, Jul 20, 2009 at 3:04 PM, Simon Horman<horms@xxxxxxxxxxxx> wrote:
> On Mon, Jul 20, 2009 at 02:03:38PM +0300, Tom Rotenberg wrote:
>> Hi,
>>
>> I have cloned and compiled the latest Xen 3.4 multifunction
>> pass-through tree, you have published, and it doesn't seem to work.
>> I did the following:
>> 1. Reboot the machine
>> 2. Binded all the usb devices to pci-back, and made them all to be mmio 
>> aligned
>> 3. Run the following command:
>>  xm create /etc/xen/hvm xen_platform_pci=0  pci='00:1a.0'
>> pci='00:1a.1' pci='00:1a.2' pci='00:1a.7' pci='00:1d.0' pci='00:1d.1'
>> pci='00:1d.2' pci='00:1d.7'
>
> Hi Tom,
>
> that looks a lot like a bug to me, thanks for your comprehensive report.
> A few questions.
>
> * Does this setup work with the regular xen-3.4-testing tree?
> * Is there anything custom in /etc/xen/hvm ?
>  If so, would it be possible for you to post a copy of that
>  file to aid reproducing the problem?
>
> Thanks
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel