I had similar experience - ext4_multi_mount_protect error and some of the containers couldn't start. What fixed the problem was running filesystem check on each container with
Sorry, I don't undestand what do you mean by
To be more clear, I have one public IP - 1.1.1.1 and containers with 10.0.0.X and I am forwarding 1.1.1.1:80 to 10.0.0.1:80 for example.
I have tried "Routed Configuration" from http://pve.proxmox.com/wiki/Network_Model but result is the same.
Hello Udo,
Probably you are right. Here is my /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 1.1.1.1
netmask 255.255.255.240
gateway 2.2.2.2
post-up echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
auto vmbr0...
I have installed Proxmox 3.1 and OpenVZ container with apache. I have redirected traffic on port 80 to that instance with
iptables -t nat -A PREROUTING -p TCP -i eth0 --dport 80 -j DNAT --to 10.0.0.3:80
When I am logged on the host or in the container and execute telnet 1.1.1.1 80 where...
As suspected the solutions is very easy from here http://pve.proxmox.com/wiki/Network_Model#Masquerading
I added following lines at the end of host's /etc/network/interfaces
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -t nat -A POSTROUTING -s '10.0.0.0/24'...
I have simple situation, but I could not get it to work.
I have one machine with Proxmox 3.1.
I have public static IP address and Proxmox host have internet connection (ping google.com works).
I need few VMs (OpenVZ, Ubuntu Server 12) which needs to connection to internet and have IP addresses...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.