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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|