On 12/6/05, Andy Smith <andy@xxxxxxxxxxxxxx> 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-18.104.22.168-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
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 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 :)
Xen-users mailing list