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] sharing PCI devices ....

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] sharing PCI devices ....
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Wed, 7 Sep 2005 16:13:10 +0100
Cc: Himanshu Raj <rhim@xxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 07 Sep 2005 15:11:45 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050907134214.GF25239@xxxxxxxxxxxxx>
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: <20050907134214.GF25239@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
> A question about PCI devices. If we leave security problems aside, is it
> possible to provide access of a PCI device to 2 domains (may include dom
> 0), i.e. would current xen implementation suffice or a PCI device can only
> be used exclusively by a domain.

Not usually: devices are basically stupid and they only expect one entity to 
be talking to them.  If you get multiple domains driving a device directly 
it'll probably end in tears, although it might be amusing :-)

You've really got two choices:
1) Just assign a device to one domain at a time - maybe buy multiple devices 
to serve multiple domains.
2) Virtualise at a higher level using a backend / frontend.  e.g. the virtual 
block device, virtual net dev, virtual usb dev, etc...

What are you actually trying to achieve?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>