Hi folks,
Does vifname still work the same in -unstable?
The following config file:
name = "ircd"
kernel = "/boot/vmlinuz-2.6.12.6-xenU_dnuk_1"
root = "/dev/sda1 ro"
memory = 128
disk = [ ''phy:vg00/domu_ircd_root,sda1,w'',
''phy:vg00/domu_ircd_swap,sda2,w'' ]
nics = 1
vif = [ ''mac=00:16:3e:6b:18:81, bridge=xenbr0,
vifname=vif-ircd.0'' ]
after creation results in the following in dom0:
$ sudo xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 128 1 r----- 37.0
ircd 2 128 1 -b---- 11.4
$ brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
vif0.0
vif2.0
Networking works fine, so it just looks like the vifname parameter
was ignored. Does this functionality still exist, has it changed
etc.?
Thanks,
Andy
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I haven''t had any responses to the below question, so I''m resending just in case anyone who knows the answer missed it. Basically I''m used to setting vifname in xen 2.0.x but on one server that is running -unstable from late november it seems that is ignored. Was vifname functionality removed in xen 3? On Tue, Nov 29, 2005 at 12:50:01PM +0000, Andy Smith wrote:> Hi folks, > > Does vifname still work the same in -unstable? > > The following config file: > > name = "ircd" > kernel = "/boot/vmlinuz-2.6.12.6-xenU_dnuk_1" > root = "/dev/sda1 ro" > memory = 128 > disk = [ ''phy:vg00/domu_ircd_root,sda1,w'', > ''phy:vg00/domu_ircd_swap,sda2,w'' ] > nics = 1 > vif = [ ''mac=00:16:3e:6b:18:81, bridge=xenbr0, vifname=vif-ircd.0'' ] > > after creation results in the following in dom0: > > $ sudo xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 128 1 r----- 37.0 > ircd 2 128 1 -b---- 11.4 > $ brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no peth0 > vif0.0 > vif2.0 > > Networking works fine, so it just looks like the vifname parameter > was ignored. Does this functionality still exist, has it changed > etc.? > > Thanks, > Andy_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 12/6/05, Andy Smith <andy@strugglers.net> wrote:> I haven''t had any responses to the below question, so I''m resending > just in case anyone who knows the answer missed it. > > Basically I''m used to setting vifname in xen 2.0.x but on one > server that is running -unstable from late november it seems that is > ignored. Was vifname functionality removed in xen 3? > > On Tue, Nov 29, 2005 at 12:50:01PM +0000, Andy Smith wrote: > > Hi folks, > > > > Does vifname still work the same in -unstable? > > > > The following config file: > > > > name = "ircd" > > kernel = "/boot/vmlinuz-2.6.12.6-xenU_dnuk_1" > > root = "/dev/sda1 ro" > > memory = 128 > > disk = [ ''phy:vg00/domu_ircd_root,sda1,w'', > > ''phy:vg00/domu_ircd_swap,sda2,w'' ] > > nics = 1 > > vif = [ ''mac=00:16:3e:6b:18:81, bridge=xenbr0, vifname=vif-ircd.0'' ] > > > > after creation results in the following in dom0: > > > > $ sudo xm list > > Name ID Mem(MiB) VCPUs State Time(s) > > Domain-0 0 128 1 r----- 37.0 > > ircd 2 128 1 -b---- 11.4 > > $ brctl show > > bridge name bridge id STP enabled interfaces > > xenbr0 8000.feffffffffff no peth0 > > vif0.0 > > vif2.0 > > > > Networking works fine, so it just looks like the vifname parameter > > was ignored. Does this functionality still exist, has it changed > > etc.? > > > > Thanks, > > AndyAndy, When I tried to use vifname in Xen3 I always received an error message. I just skip out the vifname statement after I realize it is of no use for what I want. I would ask you to analyse what you want. If you are going to use everything from within the domU, use eth0 and ethX inside it. They will not change. In fact, you only need to know about the vifname if you are going to use it in dom0, which is not needed in Xen3 because of the vif start scripts. Take a look at /etc/xen/scripts/vif-*, they will correctly start up you vif and bind it to the bridge you want, and turn up the vif. Good job there :) -- Bye, Fernando Maior LPIC/1(31908) LinuxCounter(391325) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Dec 06, 2005 at 11:00:34AM -0200, Fernando Maior wrote:> I would ask you to analyse what you want. If you are going to use everything > from within the domU, use eth0 and ethX inside it. They will not change. In > fact, you only need to know about the vifname if you are going to use it in > dom0, which is not needed in Xen3 because of the vif start scripts.I need to use it in dom0 to measure bandwidth used by each domU. I can''t measure anything inside a domU because that can be meddled with. I am used to doing this with xen 2.0.x and have infrastructure built around the ability to do this. :(> Take a look at /etc/xen/scripts/vif-*, they will correctly start up you vif and > bind it to the bridge you want, and turn up the vif. Good job there :)Is it possible to edit the scripts to name the vif based on the domain''s name rather than its id number (which changes)? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Take a look at /etc/xen/scripts/vif-*, they will correctly start up > > you vif and bind it to the bridge you want, and turn up the > vif. Good > > job there :) > > Is it possible to edit the scripts to name the vif based on > the domain''s name rather than its id number (which changes)?We should be passing all the variables specified in a vif stanza as environment to the hotplug script when it runs. This would make it dead easy to implement vifname in hotplug-common.sh using ''ip link set name''. Unfortunately, for no particularly good reason xend currently filters the set of strings it passes in to hotplug. Patches welcome. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>Is it possible to edit the scripts to name the vif based on the >domain''s name rather than its id number (which changes)?It looks like you can''t, here is the ''env'' output for vif-bridge script: SUBSYSTEM=xen-backend XENBUS_TYPE=vif DEVPATH=/devices/xen-backend/vif-15-0 XENBUS_FRONTEND_ID=15 script=/etc/xen/scripts/vif-bridge vif=vif15.0 PATH=/sbin:/bin:/usr/bin:/usr/sbin:/etc/xen/scripts:/bin:/sbin:/usr/sbin:/us r/bin ACTION=online PWD=/etc/hotplug LANG=POSIX XENBUS_PATH=backend/vif/15/0 XENBUS_BASE_PATH=backend/vif HOME=/ SHLVL=3 PHYSDEVDRIVER=vif PHYSDEVBUS=xen-backend SEQNUM=975 _=/usr/bin/env As far as I can understand it, the interface name is set in environment, but it looks like it''s already created before this script is invoked. I checked all other scripts and none of them seems to launch vif-bridge. So my last guess is it''s in xend python sources. I would like to name vif as I wish too, so I would be interested if anyone got a solution. Christophe PAINCHAUD _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Dec 08, 2005 at 07:43:39PM +0100, PAINCHAUD Christophe wrote:> As far as I can understand it, the interface name is set in > environment, but it looks like it''s already created before this script > is invoked. I checked all other scripts and none of them seems to > launch vif-bridge. So my last guess is it''s in xend python sources. > > I would like to name vif as I wish too, so I would be interested if > anyone got a solution.Unless another method has been provided I don''t think there is a way to easily measure the bandwidth use of a domain across restarts of the domain, without this 2.0.x feature? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users