Proxmmox with OpenVZ and veth

ProgMan

New Member
Dec 6, 2011
3
0
1
Hi,

I have installed newest proxmox (1.9). I can create virtual machines using OpenVZ. I installed ubuntu 10.04 template. As a first I configured network as “venet”. All was ok. Ubuntu works. I could log in to main machine ( proxmox debian ) and individual virtual machines ( on ubuntus ) using “putty” from another computer. They worked correctly but it looks like this network model does not allow setup multiple containers which use the same ports. I noticed it while I wanted to setup apache on one Virtual Machine ubuntu1 ( port 80 ) and Ngingx (port 80) on another virtual machine ubuntu2. Conflict appeared…
To resolve this problem ( port conflicts ) I guessed that I should use “veth” model ( some information aboutnetwork models I found at: http://wiki.openvz.org/Differences_between_venet_and_veth )
I created machines, I have created bridges according to video at: http://pve.proxmox.com/wiki/Category:Video_Tutorials and I used created bridges during virtual machines creation.
My set up is 192.168.100.106 (proxmox debian), and 192.168.100.107 ( ubuntu1 ), 192.168.100.108 ( ubuntu2) using created bridges. As result while I want to log into individual ubuntu machines I am logged into main proxmox debian machine only (even if I put 192.168.100.107, 192.168.100.108 addresses to putty I am logged into main debian machine. It seems the packets are not forwarded to individual ubuntu virtual machines ). I was trying to use magic commands which I have found in internet ( especially on openVZ site ). Still the same problem appears. Can someone help me to resolve this problem and show step by step how to set up it step by step?

Cheers,
Piotr
 
They worked correctly but it looks like this network model does not allow setup multiple containers which use the same ports.
No, it's a delusion. If your machines have different IP addresses, there are no restrictions on port usage.

Please, copypaste here output of:
iptables-save
ip route show
ip addr show

from your host-machine.
 
Thanks for your response.

The problem which caused my troubleshooting is Trac and Big Blue Button ( BBB ). It looks like it happened not only to me. The problem about BBB is described here by someone another:

http://groups.google.com/group/bigbluebutton-setup/browse_thread/thread/f4e02c938844f401

cite:

"BigBlueButton uses nginx, which listens on port 80 for http access and
tunneling. As we have apache already running on the server, I needed
to configure apache to listen on a different port. To do this, edit /
etc/apache2/ports.conf and change the entry for 80 to another number,
such as 8081. Avoid using 8080 in apache as BigBlueButton uses tomcat6
which binds to that port."


I did not answer couple days because I thought I manage problem myself.
In fact, partially I did it. After thousands of tryies I managed to set up a bridged configuration.
Method? I have just setup /etc/network/interfaces as follow:
ON HOST:
Code:
# network interface settings
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address  192.168.100.106
        netmask  255.255.255.0
        gateway  192.168.100.100
        broadcast  192.168.100.255
        network 192.168.100.0

auto vmbr0
iface vmbr0 inet static
        address 192.168.100.106
        netmask 255.255.255.0
        gateway 192.168.100.100
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

ON GUEST:
Code:
auto eth0
iface eth0 inet static
        address 192.168.100.108
        netmask 255.255.255.0
        broadcast 192.168.100.255

Then I follwed the instructions:
http://wiki.openvz.org/Virtual_Ethernet_device

It Worked !!! The Problem of port conflicts dissapeared ( because of change the network model to veth as I guess).

So I have been encouraged to proxmox, I decided to try the proxmox 2.0 beta ( the official switching to it is comming soon as I understand because the old Debian will not be supported in a 2 months as far as I know ).

So I have installed it. I created the same configuration like on Proxmox 1.9 ( using venet model ). I have installed Big Blue Button software (BBB) on one virtual machine and Trac on the second one separed virtual machine successfully.
I was trying to run ( Trac and BBB-nginx www server ) both on port 80. Unfortunatelly the conflict still appears like on Proxmox 1.9. When I changed ports ( let say Trac run on port 8000 or any else ) it works great.
On this Proxmox 2.0 I could not manage to setup bridged network as well. I was trying to use manually editing host and client /etc/network/interfaces files like I did on Proxmox 1.9 wihout success. I have stayed at venet model. I am just using different ports...

I hope in some time I will manage to resolve it.

Right now, the results of the three commands ( from Proxmox 2.0 ) which you are asking for are as follows.

root@redirect:~# iptables-save
# Generated by iptables-save v1.4.8 on Sun Dec 11 23:41:50 2011
*mangle
:pREROUTING ACCEPT [108052:26828458]
:INPUT ACCEPT [84780:17339409]
:FORWARD ACCEPT [23272:9489049]
:OUTPUT ACCEPT [76508:19392871]
:pOSTROUTING ACCEPT [99780:28881920]
COMMIT
# Completed on Sun Dec 11 23:41:50 2011
# Generated by iptables-save v1.4.8 on Sun Dec 11 23:41:50 2011
*filter
:INPUT ACCEPT [84780:17339409]
:FORWARD ACCEPT [23272:9489049]
:OUTPUT ACCEPT [76508:19392871]
COMMIT
# Completed on Sun Dec 11 23:41:50 2011


root@redirect:~# ip route show
192.168.100.109 dev venet0 scope link
192.168.100.108 dev venet0 scope link
192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.106
default via 192.168.100.100 dev eth0

root@redirect:~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 00:01:2e:31:4b:d4 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.106/24 brd 192.168.100.255 scope global eth0
inet6 fe80::201:2eff:fe31:4bd4/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 1c:4b:d6:d1:c9:ef brd ff:ff:ff:ff:ff:ff
4: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/void
inet6 fe80::1/128 scope link
valid_lft forever preferred_lft forever

So I have noticed some another problems in Proxmox 2.0.
Namely:
1) The name of virtual machine created by gui can't contain '_' character.
In fact gui allows for that but if the virtual machine is run manually using vzctl start <machine id>, then error message is shown at the beggining.
2) I did not manage to setup bridged network model.
3) The result of http://wiki.openvz.org/Virtual_Ethernet_device instructions were not saved ( were missed after system reboot )

Anyway proxmox 2.0 looks promissing...

Can you advise me something?

Thanks,
ProgMan
 
I cannot say anything about ProxMox 2.0 becouse I haven't try it yet.

But I see, that on your installation, according to "ip addr show", that you have no bridge interfaces (vmbr* or br*) on your host machine. It's explicable that you can not create a bridged interface inside VE. You just have no bridges on HN to connect to.

To understand the difference between venet and veth consider that venet is a PPP tunnel from host-machine into VE, and veth is like a switch that VE is linked to.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!