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

Re: [Xen-devel] domU guest for xcp 0.1.1

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Wed, 31 Mar 2010 16:23:51 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 31 Mar 2010 16:24:42 -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:received:message-id:subject:from:to:cc:content-type; bh=W5s2iMESgn3/3Ckw3TGztl5B3PnK8R7A91u+A++gUcQ=; b=kRogk0HxUDpbO7THCi5mwQdjwyzqgfiMcmeDZeqMU8XOfrUyJctJTKBCJcN9EJBYnO enqbBAcqaqAQg8B5fNqkhThWZssYRNAiRnJ/T6POs783h/cz2HOEDMpJtx5fUjD1nKP5 JHOyxP7Vi2a4mIFRFthB2Bms4HDgdu/6N6kVc=
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; b=fXb6D+6UbBVQN+kaT4M60WmisuGf7AVxKW7EibkX1F+za8e8Q+31kD8NAIFQMNOr6v nwg/nUxkaUQCARbyJLH4nBJXqDeV+5Yoh8LPgFRCh5uCwaa8wUrCj2V/VKhWTQk7eiqR jMTCmkwZ/63OEj43vdz6NilHTdDhpIIHVaIUE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1268725069.8652.4179.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <29b32d341003120910l5340bc01tcada3ca2adbaf763@xxxxxxxxxxxxxx> <1056770753.20100314215224@xxxxxxxxxxxxxx> <29b32d341003141840x5a55e74sfb2eda56005e4f84@xxxxxxxxxxxxxx> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@xxxxxxxxxxxxxx> <1268642688.8652.2792.camel@xxxxxxxxxxxxxxxxxxxxx> <29b32d341003150642o4e2620edsf154b19d78aa7f42@xxxxxxxxxxxxxx> <1268660645.10129.25070.camel@xxxxxxxxxxxxxxxxxxxxxx> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@xxxxxxxxxxxxxx> <29b32d341003151904m2a992be5s74697d6047b864c6@xxxxxxxxxxxxxx> <1268725069.8652.4179.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

The NIC will remain bound to the pciback driver until you explicitly
unbind it and rebind to another driver in domain 0 and won't be
available until you do this. You can rebind the driver echo'ing the PCI
BDF of the device into the "unbind" and "bind" nodes under the
appropriate drivers in sysfs. e.g. for pcidev=0000:00:08.0:

echo -n "$pcidev" > /sys/bus/pci/devices/"$pcidev"/driver/unbind
echo -n "$pcidev" > /sys/bus/pci/drivers/$mydriver/bind


Hi Ian,

Currently, I have to reboot dom0 when I use

xe vm-param-set uuid=<vm-uuid> other-config:pci=<pci-bfd>  for pci passthrough. 

I looked at above bind/unbind files and they are present in /sys/bus/pci/drivers/<driver_name>/. Currently my driver is not loaded in dom0(not intended to load in dom0 due to passthrough) so I don't think I need to unbind. I did echo -n $pcidev > /sys/bus/pci/drivers/pciback/bind and I get

-bash: echo: write error: No such device

Currently, only way passthrough is enabled in domU is reboot of dom0 and domU after xe vm-param-set...

Kindly let me know if there is a way to avoid reboot.

Thanks


 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>