From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ritu kaur <ritu.kaur.us@gmail.com>
Subject: Re: domU guest for xcp 0.1.1
Date: Wed, 31 Mar 2010 16:23:51 -0700
Message-ID: <n2l29b32d341003311623o713db6c1h6eda7b832987ff81@mail.gmail.com>
References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com>
	<1056770753.20100314215224@eikelenboom.it>
	<29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com>
	<29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com>
	<1268642688.8652.2792.camel@localhost.localdomain>
	<29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com>
	<1268660645.10129.25070.camel@zakaz.uk.xensource.com>
	<29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com>
	<29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com>
	<1268725069.8652.4179.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1753690525=="
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1268725069.8652.4179.camel@localhost.localdomain>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

--===============1753690525==
Content-Type: multipart/alternative; boundary=000e0cd1708ef7a56204832109c8

--000e0cd1708ef7a56204832109c8
Content-Type: text/plain; charset=ISO-8859-1

> 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

--000e0cd1708ef7a56204832109c8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); paddin=
g-left: 1ex;">
The NIC will remain bound to the pciback driver until you explicitly<br>
unbind it and rebind to another driver in domain 0 and won&#39;t be<br>
available until you do this. You can rebind the driver echo&#39;ing the PCI=
<br>
BDF of the device into the &quot;unbind&quot; and &quot;bind&quot; nodes un=
der the<br>
appropriate drivers in sysfs. e.g. for pcidev=3D0000:00:08.0:<br>
<br>
echo -n &quot;$pcidev&quot; &gt; /sys/bus/pci/devices/&quot;$pcidev&quot;/d=
river/unbind<br>
echo -n &quot;$pcidev&quot; &gt; /sys/bus/pci/drivers/$mydriver/bind<br>
<div class=3D"im"><br></div></blockquote><div><br>Hi Ian,<br><br>Currently,=
 I have to reboot dom0 when I use <br><br>xe vm-param-set uuid=3D&lt;vm-uui=
d&gt; other-config:pci=3D&lt;pci-bfd&gt;=A0 for pci passthrough.=A0 <br><br=
>I looked at above bind/unbind files and they are present in /sys/bus/pci/d=
rivers/&lt;driver_name&gt;/. Currently my driver is not loaded in dom0(not =
intended to load in dom0 due to passthrough) so I don&#39;t think I need to=
 unbind. I did echo -n $pcidev &gt; /sys/bus/pci/drivers/pciback/bind and I=
 get <br>
<br>-bash: echo: write error: No such device<br><br>Currently, only way pas=
sthrough is enabled in domU is reboot of dom0 and domU after xe vm-param-se=
t... <br><br>Kindly let me know if there is a way to avoid reboot.<br><br>
Thanks<br><br><br>=A0<br></div></div><br>

--000e0cd1708ef7a56204832109c8--


--===============1753690525==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1753690525==--