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-users

Re: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same gue

To: "Xen Users" <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] xen 3.3.0 PCI device must be co-assigned to the same guest
From: "Andy Burns" <xen.lists@xxxxxxxxxxx>
Date: Tue, 2 Sep 2008 21:22:31 +0100
Cc:
Delivery-date: Tue, 02 Sep 2008 13:23:28 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=Mg68xX5BADOgbtJ9EGzkKuT3i9nS2DTgc0kNf0iP120=; b=f/8o+5uUiq+s4fDhSPZeDq2w+pJhk30fg36WXjc1k/7+sBVSHXmrBwUcysXn1sCcuv H6zyQihSU81rhisf3Uq669hS42l/ez2F1x3ssyJz7v8d1Tr8xf6uObHuX2jNOuLwT4VG HvSzRKAd+t2UaDECc2BKKS4bGYWNJnpCGt5K4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=JVpILyldy0JlIApLp39kIPsDGCaqNsTqK915cUxdfBjGvvrqhpWZQcjDUIzTaYGNQB Gt7f+2/4DOvt8AgerBb6cvUnE9C+nZG+QMN536U2wbuUwkZXf5wbVu6SJmPLWHfv/nvQ nL0EFwv7LV3BlhvUIuzFjD35jwd4CoUs9Hpng=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49627735003F5C479100225C339F9FE0D4DF2FC824@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <b4057d410809021248h73c3a281o7065d3201576f3c@xxxxxxxxxxxxxx> <49627735003F5C479100225C339F9FE0D4DF2FC824@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
2008/9/2 Joseph L. Casale <JCasale@xxxxxxxxxxxxxxxxx>:

> Thanks for that pointer! I also have an issue with a poorly built 3.3.0!

Yes I was pleased to find it.

> Why aren't you simply generating a new initrd with a --preload=pciback?

Laziness I guess ;-)

I couldn't use pciback=blah as it's build as a module in centOS5.2
kernel, so the /sys method was a a quick way out, I was going to
blacklist the saa* drivers in modprobe.conf but never got around to
it.

> I wonder if that's not part of the issue (though that's a weird error msg).

It used to work fine on xen 3.2.0

> I expected to see that for some devices like dual/quad port nics where two
> ports share the same pci location.

Yes, I don't expect to be able to split different functions of a
single PCIID between domains!

> Keep us posted as to your success with this version of Xen...

So far so good with non-PCI passthrough domains, I'll have a play with
pv-grub on a windows domU in a while.

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