Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 170688

Issue with openvz, direct access to network device and vlans

$
0
0
Dear All,


I am using the following command to move a phyiscal Ethernet device from the host to a container.


vzctl set <CTID> --netdev_add ethx --save


x = host Ethernet interface, i.e. eth7


This works well and I can see the device directly in the container.


However, I am unable to assign vlans to the device.


I have tried using the debian-6.0-standard_6.0.6_i386.tar.gz and debian-6-turnkey-core_12-1_i386.tar.gz templates.


On the CT's I have installed vlan support with apt-get install vlan.


When I try to initialise a vlan interface on the physical device (which I moved from the host to the CT, I get the following error message)



WARNING: Could not open /proc/net/vlan/config. Maybe you need to load the 8021q module, or maybe you are not using PROCFS??
ERROR: trying to add VLAN #103 to IF -:eth7:- error: Package not installed
Failed to bring up eth7.103.


When I check on both templates I see that /proc/net/vlan does not exist.



So I decided to check the host (Proxmox 2.3-13) and discovered /proc/net/vlan was missing, even though the vlan package is installed.



So I ran modprob 8011q on the host and /proc/net/vlan/config appeared on the host and CT's.



I can now bring up a vlan interface inside a CT, but get a strange error message:-



Added VLAN with VID == 103 to IF -:eth7:-

Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config

ERROR: trying to add VLAN #103 to IF -:eth7:- error: File exists


Should I be worried about this? Why does Proxmox not load the 8011q module when it boots?



Should I add modprobe 8011q to /etc/modprobe.d/xxxxx.conf on the host?

xxxxx = a file name of my choosing.

Viewing all articles
Browse latest Browse all 170688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>