Re: [Xen-devel] Q on vif interface creation

[ravi kerur <rkerur@xxxxxxxxx>]

Hello Pasi,


Thanks for your inputs. I do not see "xm" cmd 

-bash: xm: command not found

I do see "xe" cmd which has vif-unplug/vif-plug and vif-destroy/vif-create. I detached a vif via unplug and destroyed it. When creating a new vif, I do not see the option of vifname in it

xe help vif-create
command name            : vif-create
        reqd params     : device, network-uuid, vm-uuid
        optional params : mac, mtu
        description     : Create a VIF. Appropriate values for the device are listed in the parameter 'allowed-VIF-devices' on the VM. If specified, the MAC parameter is of the form aa:bb:cc:dd:ee:ff. If MAC is not specified the server will choose an appropriate MAC automatically.

Inputs appreciated.

Thanks
-RK

On Mon, Dec 21, 2009 at 12:34 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

On Sun, Dec 20, 2009 at 09:06:45PM -0800, ravi kerur wrote:

>    Hello,
>
>    Need inputs on creating "vif" interface with a different name i.e when a
>    domU is installed, vif<dom-id>:<intf-num> is created by default in dom0
>    and domU which then triggers xenbus state-machine and communication is
>    established. We want to change the name to be  "ncr<dom-id>:<intf-num>",
>    the reason being, we are developing our driver specific netfront and
>    netback which will monitor "ncr" to trigger xenbus state-machine. I am not
>    sure where to start in-order to make these changes. Inputs will be very
>    much appreciated.
>

Hello,

You can use the "vifname" option on the vif line.
See "xm create --help_config" for more information.

-- Pasi

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