OpenVZ Forum


Home » General » Support » *SOLVED* VLAN on VETH device?
*SOLVED* VLAN on VETH device? [message #6841] Mon, 25 September 2006 09:31 Go to next message
szocske is currently offline  szocske
Messages: 35
Registered: September 2006
Member
Hi!

I'd like to issue vconfig commands within a VE to set up VLANs on its veth interface. (which it beleives to be eth0.) But there is no /proc/net/vlan directory inside the VEs.
I have the 8021q module loaded in the kernel, so vconfig works fine outside, in the HW node, on the real eth0.

Is this a known limitation, a bug, or my misconfiguration?

OpenVz patch version 026test015.

[Updated on: Tue, 07 November 2006 19:42] by Moderator

Report message to a moderator

Re: VLAN on VETH device? [message #6869 is a reply to message #6841] Tue, 26 September 2006 09:00 Go to previous messageGo to next message
szocske is currently offline  szocske
Messages: 35
Registered: September 2006
Member
I'd hate to rush things guys, but this is a serious roadblock in our openVZ deplolyment. We might even consider purchasing a bunch of closedVZ licenses, if that solves this particular issue.
(hard to imageine how it could be done outside the kernel and its GPL though...)
Assuming there is no support yet:
How big of an effort would you estimate the development of VLAN support on veth devices? Is there some theoretical problem with it, or just omething noone ever bothered to do just yet?
Is it something we could undertake (and contribute back of course) or is it possible to contract you guys for such targeted development? (we are an open source shop, would prefer the feature in the OS line.)
Re: VLAN on VETH device? [message #6876 is a reply to message #6841] Tue, 26 September 2006 11:29 Go to previous messageGo to next message
Andrey Mirkin is currently offline  Andrey Mirkin
Messages: 193
Registered: May 2006
Senior Member
vlan proc entry is created only in VE0 as vlan is not virtualized, so you can't see it (/proc/net/vlan) in VE.
You can create vlan interface in VE0 and move it to VPS with help of
vzctl set --netdev_add <name>

command.


Andrey Mirkin
http://static.openvz.org/userbars/openvz-developer.png
Re: VLAN on VETH device? [message #6877 is a reply to message #6876] Tue, 26 September 2006 11:47 Go to previous messageGo to next message
szocske is currently offline  szocske
Messages: 35
Registered: September 2006
Member
Great idea, thanks.
Not the full sollution we are looking for though Smile

Is it possible to --netdev_add the same tagging interface to multiple VEs at the same time? Can they then communicate through it? Also, the packets sent out on such an interface would contain the MAC address of the real eth0, not the one assigned to the veth, right?

Anyway, we are interested in estimating the effort needed to make VLANS work from VEs: our software controls VLANs diretly with ioctrl, and we'd like to be able to run it in VEs.
Re: VLAN on VETH device? [message #6885 is a reply to message #6877] Tue, 26 September 2006 13:39 Go to previous messageGo to next message
Andrey Mirkin is currently offline  Andrey Mirkin
Messages: 193
Registered: May 2006
Senior Member
You can create VLAN in VE0 and add it to bridge with other veth devices, so VPSes which are added to this bridge will be able to communicate with each other.
See http://wiki.openvz.org/Virtual_Ethernet_device#Virtual_ether net_devices_.2B_VLAN for details.

You are right, the packets sent out on such an interface would contain the MAC address of the real eth0.

We need to analyze vlan module to estimate the time we will need to virtualize it.


Andrey Mirkin
http://static.openvz.org/userbars/openvz-developer.png
Re: VLAN on VETH device? [message #7990 is a reply to message #6885] Thu, 02 November 2006 08:59 Go to previous messageGo to next message
szocske is currently offline  szocske
Messages: 35
Registered: September 2006
Member
Andrey Mirkin wrote on Tue, 26 September 2006 09:39


We need to analyze vlan module to estimate the time we will need to virtualize it.



Hi there!

Any news on this?

We are interested in sponsoring or performing the development of vlan support on veth devices.

We migrated most of our test servers from Xen and VMware to OpenVZ in the recent months. Since we tuned the resource quotas high enough, our developers are happy with it. (well, they are happy to have more servers, and happy not to have to care what goes on below. except for vlan-related tests Smile )


Thanks for the great tool anyhow!
Re: VLAN on VETH device? [message #8041 is a reply to message #7990] Fri, 03 November 2006 16:22 Go to previous messageGo to next message
Andrey Mirkin is currently offline  Andrey Mirkin
Messages: 193
Registered: May 2006
Senior Member
Hello!

Vlan support inside VE will be available soon. I have almost finished patch. After some testing I'll put it here.


Andrey Mirkin
http://static.openvz.org/userbars/openvz-developer.png
Re: VLAN on VETH device? [message #8052 is a reply to message #8041] Fri, 03 November 2006 22:22 Go to previous messageGo to next message
szocske is currently offline  szocske
Messages: 35
Registered: September 2006
Member
Andrey Mirkin wrote on Fri, 03 November 2006 11:22


Vlan support inside VE will be available soon. I have almost finished patch. After some testing I'll put it here.


This is fantastic! We are looking forward to it. I am truly grateful for the effort.
Re: VLAN on VETH device? [message #8107 is a reply to message #8052] Tue, 07 November 2006 16:19 Go to previous messageGo to next message
Andrey Mirkin is currently offline  Andrey Mirkin
Messages: 193
Registered: May 2006
Senior Member
Hello!

The patch for 2.6.18 kernel is ready.
You can try it right now.
vlan virtualization will be available in next kernel release.


Andrey Mirkin
http://static.openvz.org/userbars/openvz-developer.png

[Updated on: Tue, 07 November 2006 16:27]

Report message to a moderator

Re: VLAN on VETH device? [message #8120 is a reply to message #8107] Wed, 08 November 2006 10:49 Go to previous messageGo to next message
szocske is currently offline  szocske
Messages: 35
Registered: September 2006
Member
Andrey Mirkin wrote on Tue, 07 November 2006 11:19

Hello!
The patch for 2.6.18 kernel is ready.
You can try it right now.



You guys are simply great. We'll give it a try as soon as we can. (resource allocation issues, both human and computational, prohibit me from trying right away, I'll probably end up compiling it over the weekend.)
Re: VLAN on VETH device? [message #8137 is a reply to message #8107] Thu, 09 November 2006 10:19 Go to previous messageGo to next message
szocske is currently offline  szocske
Messages: 35
Registered: September 2006
Member
Andrey Mirkin wrote on Tue, 07 November 2006 11:19

The patch for 2.6.18 kernel is ready.
You can try it right now.
vlan virtualization will be available in next kernel release.


We have it working, and see no regression in regular functionality.
/proc/net/vlan directory exists and can be populated via vconfig.

But any vlan subinterface created in one VE is visible in all (the veth device is called eth0 in all VEs)

ifconfig -a does not list "foreign" vlans.

It is not possible to create vlans with the same vlan ID in multiple VEs:

eserver25-vz6:~# vconfig add eth0 106
Added VLAN with VID == 106 to IF -:eth0:-

eserver25-vz7:~# vconfig add eth0 107
Added VLAN with VID == 107 to IF -:eth0:-

eserver25-vz6:~# vconfig add eth0 107
ERROR: trying to add VLAN #107 to IF -:eth0:- error: Invalid argument

eserver25-vz6:~# cat /proc/net/vlan/
config eth0.106 eth0.107
eserver25-vz6:~# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
eth0.106 | 106 | eth0
eserver25-vz6:~# ls /proc/net/vlan/
config eth0.106 eth0.107
eserver25-vz6:~# cat /proc/net/vlan/eth0.107
eth0.107 VID: 107 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 0
total bytes received 0
Broadcast/Multicast Rcvd 0

total frames transmitted 0
total bytes transmitted 0
total headroom inc 0
total encap on xmit 0
Device: eth0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESSS priority Mappings:


Can we have this revised please?

Editing:
Just noticed, same goes for host machine:
eserver25:~# ls /proc/net/vlan/
config eth0.106 eth0.107
eserver25:~# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD


Editing again:

And I can't shut down the VE which has a VLAN configured:

eserver25:~# vzctl stop 109
Stopping VPS ...

Message from syslogd@localhost at Thu Nov 9 11:34:37 2006 ...
localhost kernel: unregister_netdevice: waiting for eth0 to become free. Usage count = -1

Message from syslogd@localhost at Thu Nov 9 11:35:17 2006 ...
localhost last message repeated 4 times

Meanwhile, the vlans disappear from the remaining machines:

eserver25-vz6:~# ls /proc/net/vlan/
config
eserver25-vz6:~# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
eth0.106 | 106 | eth0

[Updated on: Thu, 09 November 2006 10:41]

Report message to a moderator

Re: VLAN on VETH device? [message #8158 is a reply to message #8137] Thu, 09 November 2006 16:29 Go to previous messageGo to next message
Andrey Mirkin is currently offline  Andrey Mirkin
Messages: 193
Registered: May 2006
Senior Member
Hello!

The previous patch was not full, sorry.
Please try this patch. This patch still can be not very stable, but with you help and feedback we will try to fix all issues.


Andrey Mirkin
http://static.openvz.org/userbars/openvz-developer.png
Re: *SOLVED* VLAN on VETH device? [message #8336 is a reply to message #6841] Thu, 16 November 2006 09:15 Go to previous messageGo to next message
szocske is currently offline  szocske
Messages: 35
Registered: September 2006
Member
Hi again!

Sorry for the high latency, we had to provision the new sun servers we purchased for openvz Smile

The updated patch works, we can now ping over a vlan from one VE to another. (tested within a HW node only)
Stopping VEs works fine too.

/proc/net/vlan looks funny though:
sun03:/# ls /proc/net/vlan
config eth0.42 eth0.42 eth2.42

VLAN ID 42 was configured on the veth-s of two VEs (both eth0) and the HW node eth2. Looks the same from HW node and VEs.

We'll continue testing across a switch, and with our ioctls, and report.

One more (probably unrelated) quirk:
Despite setting up /etc/hostname correctly in the VEs, when started, `hostname` returns the HW node hostname in all of them.

Better yet: issuing the hostname command within a VE to change the hostname changes it for all VEs, and the HW node as well!

Used to work fine on 2.6.16.

Debian stable + vlan-enabled kernel

[Updated on: Thu, 16 November 2006 10:00]

Report message to a moderator

Re: *SOLVED* VLAN on VETH device? [message #8361 is a reply to message #8336] Fri, 17 November 2006 09:21 Go to previous messageGo to next message
arpad is currently offline  arpad
Messages: 16
Registered: November 2006
Junior Member
Hi!

I'm working with szocske.

There is another problem with the OpenVZ maybe it's related to the hostname problem.
When I stop a running VE I got this in the dmesg:

BUG: warning at fs/proc/generic.c:916/__remove_proc_entry()
[<c01b832a>] __remove_proc_entry+0xea/0x100
[<c01b837b>] remove_proc_loc_entry+0x3b/0x50
[<c01b83ff>] remove_proc_entry+0x1f/0x60
[<f8f8c44d>] fini_ve_sysctl+0x2d/0x40 [vzmon]
[<f8f90ba2>] env_cleanup+0xf2/0x1a0 [vzmon]
[<f8f90ce6>] vzmond_helper+0x46/0x60 [vzmon]
[<f8f90ca0>] vzmond_helper+0x0/0x60 [vzmon]
[<c01012f5>] kernel_thread_helper+0x5/0x10

We are using Debian patched kernels (it's our company policy) and the basic Debian patch-remade-2.6.18-openvz-debian patch for OpenVZ. We applied yours new VLAN patch too.

I hope it helps. If you need we can compile a pure Vanilla kernel for debug purposes.

Thanks for any help!
Re: *SOLVED* VLAN on VETH device? [message #8556 is a reply to message #8361] Fri, 24 November 2006 08:28 Go to previous messageGo to next message
arpad is currently offline  arpad
Messages: 16
Registered: November 2006
Junior Member
Hi!

I'm here again. We compiled a vanilla 2.6.18 kernel with patch-ovz028test005.1-combined and the patch you generously provided for VLAN. The only problem was that one file had moved to another directory so I had to rewrite its location in the patch.
The 802.1Q tagging seems to work but after one day usage we noticed that our functional testing not running anymore because the ssh daemon running in the VE randomly dropped the connections. I looked into the logs but found nothing relevant. I checked the quotas but none of them was violated.
So if you have any ideas I will be very happy. We need to use 802.1Q for our tests and we must keep running another machine with Xen just for this.
Thanks,

Arpad
Re: *SOLVED* VLAN on VETH device? [message #8558 is a reply to message #8556] Fri, 24 November 2006 12:54 Go to previous messageGo to next message
Andrey Mirkin is currently offline  Andrey Mirkin
Messages: 193
Registered: May 2006
Senior Member
Vlan virtualization will be available in 2.6.18-028test006 kernel.

Andrey Mirkin
http://static.openvz.org/userbars/openvz-developer.png
Re: *SOLVED* VLAN on VETH device? [message #8559 is a reply to message #8558] Fri, 24 November 2006 13:34 Go to previous messageGo to next message
szocske is currently offline  szocske
Messages: 35
Registered: September 2006
Member
Hi!

Arpad and I are working together on putting your diff-net-vlan-virt patch to testing.
Are you saying we should wait for 2.6.18-028test006 and report issues only with that version?

[Updated on: Fri, 24 November 2006 13:41]

Report message to a moderator

Re: *SOLVED* VLAN on VETH device? [message #8560 is a reply to message #8559] Fri, 24 November 2006 14:10 Go to previous message
Andrey Mirkin is currently offline  Andrey Mirkin
Messages: 193
Registered: May 2006
Senior Member
You can wait for 2.6.18-028test006 kernel or can use new patch from git: http://git.openvz.org/?p=linux-2.6.18-openvz;a=commit;h=f629dec5ea2d32d05ccedcb96c47e41971b6200c

Andrey Mirkin
http://static.openvz.org/userbars/openvz-developer.png
Previous Topic: Recompile kernel, howto
Next Topic: Networking issue with FC4
Goto Forum:
  


Current Time: Sat Jul 27 19:23:51 GMT 2024

Total time taken to generate the page: 0.02726 seconds