Does Xen Cloud Platform (XCP) support the notion of a driver domain? I can assign a VIF to a domain, but it seems that I can only attach that VIF to a network. What I''d like to do is attach the front-end VIF in one domain to a backend running in another domain. The second domain will control the physical interface (via PCI passthrough). This use case is easily supported using Xen + xm/xend, but I see know way to change the backend associated with a VIF in XCP using xe. Thanks! Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Sep 24, 2011 at 8:39 AM, Jason Sonnek <jsonnek@gmail.com> wrote:> > Does Xen Cloud Platform (XCP) support the notion of a driver domain? I can > assign a VIF to a domain, but it seems that I can only attach that VIF to a > network. What I''d like to do is attach the front-end VIF in one domain to a > backend running in another domain. The second domain will control the > physical interface (via PCI passthrough). This use case is easily supported > using Xen + xm/xend, but I see know way to change the backend associated > with a VIF in XCP using xe. >Looks like it is possible, just not well documented. Take a look at: http://xen.markmail.org/search/?q=from%3A%22Dave+Scott%22+driver+domains#query:from%3A%22Dave%20Scott%22%20driver%20domains+page:1+mid:muxxm2ux6kfdpsth+state:results Hope that helps. Thanks, Todd -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks, Todd! That appears to address half the problem. That parameter will (hopefully) allow me to assign a PCI device to an unprivileged driver domain; are you aware of any way to modify the configuration for a DomU so that it uses the driver domain as the backend for its virtual device instead of Dom0? In Xen, if I wanted to use domain X as the backend for a vif attached to Domain Y, for instance, I''d specify: vif = [''backend=X''] in Y''s configuration file and the network scripts would take care of the rest. AFAICT, there is no corresponding parameter for a vif in XCP/xe. Jason On Sat, Sep 24, 2011 at 5:55 PM, Todd Deshane <todd.deshane@xen.org> wrote:> On Sat, Sep 24, 2011 at 8:39 AM, Jason Sonnek <jsonnek@gmail.com> wrote: > > > > Does Xen Cloud Platform (XCP) support the notion of a driver domain? I > can > > assign a VIF to a domain, but it seems that I can only attach that VIF to > a > > network. What I''d like to do is attach the front-end VIF in one domain to > a > > backend running in another domain. The second domain will control the > > physical interface (via PCI passthrough). This use case is easily > supported > > using Xen + xm/xend, but I see know way to change the backend associated > > with a VIF in XCP using xe. > > > > Looks like it is possible, just not well documented. Take a look at: > > http://xen.markmail.org/search/?q=from%3A%22Dave+Scott%22+driver+domains#query:from%3A%22Dave%20Scott%22%20driver%20domains+page:1+mid:muxxm2ux6kfdpsth+state:results > > Hope that helps. > > Thanks, > Todd > > -- > Todd Deshane > http://www.linkedin.com/in/deshantm > http://www.xen.org/products/cloudxen.html > http://runningxen.com/ >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Sep 24, 2011 at 8:03 PM, Jason Sonnek <jsonnek@gmail.com> wrote:> > Thanks, Todd! That appears to address half the problem. That parameter will > (hopefully) allow me to assign a PCI device to an unprivileged driver > domain; are you aware of any way to modify the configuration for a DomU so > that it uses the driver domain as the backend for its virtual device instead > of Dom0? > > In Xen, if I wanted to use domain X as the backend for a vif attached to > Domain Y, for instance, I''d specify: > > vif = [''backend=X''] > > in Y''s configuration file and the network scripts would take care of the > rest. AFAICT, there is no corresponding parameter for a vif in XCP/xe. >Did you try editing /boot/extlinux.conf so that iommu=1 http://wiki.xen.org/xenwiki/Network_Throughput_Guide#head-00940a8336ae2a7108e19297f901a951dd7bf17f Can you also check the other debugging steps such as check /var/log/xensource.log, etc? The thread I previously sent you to stated that it should work for PV guests. Can you make sure that the NIC is not in use on dom0 and check to see if there are any messages in the guest log too? Thanks, Todd -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users