Multiple Ips are very confusing

[martinmuc]

Hello,
i am new to Proxmox PVE and evaluate it for our production servers in our company. I was very positive suprised and how easy it was to install and get the first machines running. Thumbs up!

But we have very big problems with configuring (public) IP-Adresses to KVM guests. We need for each guest one (or several) IP because the machines belongs to our customers.
We have tried the settings in the wiki http://pve.proxmox.com/wiki/Network_Model but these arent very useful, sorry. They stop to explain, where its get interesting.
We have tried some Blog-Entrys from Proxmox PVE users and searched the forum several hours for a solution.
We have tried to see how other hosters manage this(OVM and Hetzner) but the given howtos didn't work.
We have tried some settings from the kvm website, but they didn't work out, either.
Many guys in the forums have problems with the network settings.

In VMWare ESXi or Citrix Xenserver you can set an IP adress for a guest machine, regardless what is configured on the host. It works. Quick and easy. How does this work with an KVM Guest?

We have a very simple Network Configuration in our test network without any MAC filters or anything other that blocks. Just a normal switch to connect each other.

The Network is 192.168.0.0/24, Gateway, Nameserver is 192.168.0.1, The Proxmox PVE Server has 192.168.0.2 and the guests should have 192.168.0.x Every guest another one.

Are there some working howtos or any tipps or advices how to configure /etc/network/interfaces. Working for version 1.8
And if there is an solution does this work with the VZ Containers, too?

Thanks in advance,

Martin

 

[Porter]

The IP address for each guest is not managed by Proxmox, it only manages the virtual "hardware" that the networking stack in the guest will use to connect. For actual networking behavior, think of Proxmox in the topology as a network switch, not as a server that is hosting the guests.

The guests act as physical machines connected to the network, so you should configure IP addresses for them using DHCP on your network, or by manually configuring each guest's IP address (or addresses) within the guest itself.

 

[martinmuc]

Hi,

thank you very much! I don't know how i come to the idea to alter the default configs... perhaps i have read to much about it in the forums, and was thinking i MUST alter the default settings to get it running
I did a reinstall from the Server and all works fine

Thanks again,

Martin

 

[Simon Bouchard]

Humph, I have the same problem, installed PVE, with default configuration, then assign vmbr0 to a KVM guest ; adding an IP address to the KMV guest is ok but when I add an alias (eth0:0) within the guest, it's doest work at all.

While pinging the guest from the outside, I can see the ICMP requests with tcpdump on the guest, but no ping (on the alias). The primary IP adresses still work.

Configuration on the host
iface eth0 inet manual
auto vmbr0
iface vmbr0 inet static
address 184.107.93.x
netmask 255.255.255.224
broadcast 184.107.93.x
gateway 184.107.93.x
bridge_ports eth0
bridge_stp off
bridge_fd 0

Configuration on the guest (Ubuntu)
# The primary network interface
auto eth0
iface eth0 inet static
address 209.172.58.x
netmask 255.255.255.224
network 209.172.58.x
broadcast 209.172.58.x
gateway 209.172.58.x

# The alias
auto eth0:0
iface eth0:0 inet static
address 209.172.58.x
netmask 255.255.255.224

 

[matthew]

The IP address for each guest is not managed by Proxmox, it only manages the virtual "hardware" that the networking stack in the guest will use to connect. For actual networking behavior, think of Proxmox in the topology as a network switch, not as a server that is hosting the guests.

The guests act as physical machines connected to the network, so you should configure IP addresses for them using DHCP on your network, or by manually configuring each guest's IP address (or addresses) within the guest itself.

I think you are discussing KVM. With OpenVZ does this work the same way? On my CentOS 5.x virtual machine I see "ifcfg-venet0" and "ifcfg-venet0:0". If I add "ifcfg-venet0:1" with an additional IP and reboot the VM is that all that needs done?

Also, what do you do to prevent an OpenVZ virtual machine from using IP's its not supposed too?