Re: [Xen-users] VLAN configuration

[Laurent Jouannic <laurent.jouannic@xxxxxxx>]

Hi Marc,

my /etc/network/interface is:
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet manual

auto eth1
iface eth1 inet static
       address 192.168.A.B
       netmask 255.255.255.0
       gateway 192.168.A.C


before to launch /etc/xen/scripts/vlan-network-bridge, I manually: 
ifconfig eth0 up

Thanks laurent.



Marc Patino Gómez a écrit :
> Hi Lauranet,
>
> this is my grub config:
>
> title            Xen 3.0.4 / XenLinux 2.6
> root            (hd0,0)
> kernel          /xen.gz  dom0_mem=384000
> module          /vmlinuz-2.6-xen0 root=/dev/mapper/vg00-lv00 ro  
> max_loop=255
> module          /initrd.img-2.6.16.33-xen0
>
> as you see, I have 256 loop devices. If changing this don't solve you 
> problem sent me your /etc/init.d/interfaces
>
> Regards,
>
> Marc
>
>
> Laurent Jouannic wrote:
> > Hi Marc, and thanks a lot.
> >
> > It's better now, but still strange:
> >
> > /etc/xen/scripts/vlan-network-bridge start
> > start
> > Set name-type for VLAN subsystem. Should be visible in 
> > /proc/net/vlan/config
> > Added VLAN with VID == 2 to IF -:eth0:-
> > Added VLAN with VID == 2 to IF -:eth1:-
> > ifdown: interface eth0 not configured
> > SIOCSIFNAME: Device or resource busy                                  
> >                    <=============  STRANGE
> > ifdown: interface eth0.2 not 
> > configured                                                             
> > <=============  STRANGE
> > Nothing to flush.
> > Nothing to flush.
> > Waiting for peth0.2 to negotiate link.Ignoring unknown interface 
> > eth0.2=eth0.2.   <=============  STRANGE
> > Nothing to flush.
> > Waiting for peth1 to negotiate link.
> > Link veth1 is 
> > missing.                                                   
> >                                        <=============  STRANGE
> > This may be because you have reached the limit of the number of 
> > interfaces
> > that the loopback driver supports.  If the loopback driver is a 
> > module, you
> > may raise this limit by passing it as a parameter (nloopbacks=<N>); 
> > if the
> > driver is compiled statically into the kernel, then you may set the 
> > parameter
> > using loopback.nloopbacks=<N> on the domain 0 kernel command line.
> >
> > Apparently, il seems to deal with: loopback
> > But I put:  loop max_loop=64 in /etc/modules
> >
> > Does I have to include loopback.nloopbacks in my grub.conf
> > like:
> >
> > title           Xen 3.0.3-1-i386-pae / Debian GNU/Linux, kernel 
> > 2.6.18-4-xen-686
> > root            (hd0,0)
> > kernel          /xen-3.0.3-1-i386-pae.gz dom0_mem=200000 
> > loopback.nloopbacks=64
> > module          /vmlinuz-2.6.18-4-xen-686 root=/dev/md2 ro console=tty0
> > module          /initrd.img-2.6.18-4-xen-686
> > savedefault
> >
> > I don't know howmuch nloopback I have to put,
> > is 64 ok ?
> >
> > It's dangerous to deal with kernel stuff, the machine is not in the 
> > same area....
> > Thanks. Laurent.
> >
> >
> >
> >
> >
> > Marc Patino Gómez a écrit :
> > > Hi Laurent,
> > >
> > > has you load the vlan kernel module?
> > >
> > > # lsmod | grep 8021q
> > >
> > > if not :
> > >
> > > # modprobe 8021q
> > >
> > > I hope it will help you.
> > >
> > > Marc
> > >
> > > Laurent Jouannic wrote:
> > > > Hi to the ML.
> > > >
> > > > I'm new to VLAN configuration, and combining it to XEN is a bit 
> > > > difficult.
> > > > I want to use VLAN because it's possible to "arping" from a domU to 
> > > > an other, and VLAN looks like; the only solution to prevent that.
> > > > May be I'm wrong if someone got a solution, I may be interrested. 
> > > > I've also tryed ebtables, but nothing to prevent arp question: 
> > > > who-as IP¨.
> > > > The configuration I need is:
> > > >  -------------
> > > >  |   domU      |
> > > > -| -[ dom1 ]-  |-
> > > > | -[ dom2 ]-  |
> > > >  -------------
> > > >
> > > > I want dom1 and dom2 to use eth0 and eth1, with vlan interface.
> > > >
> > > > I've tryed 
> > > > http://lists.xensource.com/archives/html/xen-users/2007-03/msg00988.html 
> > > > configuration, but I have the following error:
> > > > WARNING:  Could not open /proc/net/vlan/config.  Maybe you need to 
> > > > load the 8021q module, or maybe you are not using PROCFS??
> > > > Set name-type for VLAN subsystem. Should be visible in 
> > > > /proc/net/vlan/config
> > > > ERROR: trying to add VLAN #2 to IF -:eth0:-  error: Invalid argument
> > > > ERROR: trying to add VLAN #3 to IF -:eth0:-  error: Invalid argument
> > > >
> > > > The machine run on Debian Etch and the vlan package is intalled.
> > > >
> > > > If you have some ideas, I'm stuck!!!
> > > > Thanks.
> > > >
> > > >
> > > > Laurent.
> > > >
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users