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] domU guest for xcp 0.1.1

To: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Tue, 16 Mar 2010 07:37:49 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 16 Mar 2010 00:38:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <29b32d341003151904m2a992be5s74697d6047b864c6@xxxxxxxxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@xxxxxxxxxxxxxx> <112460240.20100314121540@xxxxxxxxxxxxxx> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@xxxxxxxxxxxxxx> <1056770753.20100314215224@xxxxxxxxxxxxxx> <29b32d341003141840x5a55e74sfb2eda56005e4f84@xxxxxxxxxxxxxx> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@xxxxxxxxxxxxxx> <1268642688.8652.2792.camel@xxxxxxxxxxxxxxxxxxxxx> <29b32d341003150642o4e2620edsf154b19d78aa7f42@xxxxxxxxxxxxxx> <1268660645.10129.25070.camel@xxxxxxxxxxxxxxxxxxxxxx> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@xxxxxxxxxxxxxx> <29b32d341003151904m2a992be5s74697d6047b864c6@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2010-03-16 at 02:04 +0000, Ritu kaur wrote:
> Thanks Ian and Pasi, it took me much less time than I had thought to
> fix drivers and I am able to see nic interfaces via ifconfig. I am yet
> to test ping and other stuff. Had couple of questions
> 1. I used xe vm-param-clear uuid=<uuid-of-vm> param-name=other-config
> on dom0 and rebooted domU assuming dom0 will get back pci device. It
> didn't. I had to reboot dom0 in order to unhook pci device from domU.
> Is this the way it is supposed to work? 

Aside: you need "param-key=pci" in the above or I think you will clear
all keys in other-config which is unlikely to be what you want. You
could also have used vm-param-set other-config:pci="".

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

> 2. Unrelated to pci passthrough, xen/stable code I downloaded doesn't
> seem to have netfront drivers or any front drivers, doesn't it come by
> default when you download from xen/stable?

It should do. The modules have different names though, xen-netfront and
xen-blkfront IIRC.


Xen-devel mailing list