KVM networking on OVH

D

djdiez

Guest
I solved this! thank you all!
----------------------------------------
Hello,
this is an OVH desperated user. I was really amazed wen i discovered proxmox ve and it's powerful web interface to manage the virtual machines, so I decided to set up a server with this distribution.
After reading some posts in this forum I know that OVH uses a customized and not-supported version of pve, but I'm really tired of the try->error method and i don't post asking for official support, only for someone who can show me the light, because i know i misunderstood anything in the setup of my system.

I want to create 2 virtual machines (Windows 2003 KVM and 1 Debian), by now i'm with the KVM.

I read the Fridu's guide (http://www.fridu.org/hosting/52-openvz-virtualization) and i'd like something like this, but i'm starting with a simpler config and these are the steps I tried.

----------------------

  1. Connect to my brand-new-server
  2. Config failover IPs in /etc/network/interfaces following the ovh guide
    Default config:
    Code: 
    auto eth0
iface eth0 inet static
    address 91.121.X.Y
    netmask 255.255.255.0
    network 91.121.X.0
    broadcast 91.121.X.255
    gateway 91.121.X.254
auto vmbr0
iface vmbr0 inet static
    address 91.121.X.Y
    netmask 255.255.255.0
    post-up /etc/pve/kvm-networking.sh
    bridge_ports dummy0
    bridge_stp off
    bridge_fd 0
    Added by me
    Code: 
    auto eth0:0
iface eth0:0 inet static
    address 94.23.Z.W
    netmask 255.255.255.255
    network 94.23.Z.0
    broadcast 94.23.Z.W
auto eth0:1
iface eth0:1 inet static
    address 94.23.Z.V
    netmask 255.255.255.255
    network 94.23.Z.0
    broadcast 94.23.Z.V
    Result:
    Code: 
    # ifconfig
dummy0    Link encap:Ethernet  HWaddr 22:f6:25:99:f8:22  
          inet6 addr: ---
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:678 (678.0 B)

eth0      Link encap:Ethernet  HWaddr 00:1c:XX:XX:XX:XX  
          inet addr:91.121.X.Y  Bcast:91.121.X.255 Mask:255.255.255.0
          inet6 addr: ---
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:21356 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22869 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1920018 (1.8 MiB)  TX bytes:3783647 (3.6 MiB)

eth0:0    Link encap:Ethernet  HWaddr 00:1c:XX:XX:XX:XX 
          inet addr:94.23.Z.W  Bcast:94.23.Z.W  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth0:1    Link encap:Ethernet  HWaddr 00:1c:XX:XX:XX:XX  
          inet addr:94.23.Z.V  Bcast:94.23.Z.V  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6245 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6245 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1661077 (1.5 MiB)  TX bytes:1661077 (1.5 MiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmbr0     Link encap:Ethernet  HWaddr 22:f6:25:99:f8:22  
          inet addr:91.121.X.Y  Bcast:91.121.X.255  Mask:255.255.255.0
          inet6 addr: -- eliminado --
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)
  3. Config the fail-over routes

    Code: 
    # ip route add 94.23.Z.W dev vmbr0
# ip route add 94.23.Z.V dev vmbr0
  4. Creation of KVM and and installation of Windows2003 over it.
    Code: 
    /etc/qemu-server# cat 101.conf
ostype: w2k3
memory: 4096
onboot: 1
name: win2003
ide2: none,media=cdrom
smp: 2
bootdisk: scsi0
scsi0: vm-101-disk.qcow2
description: Windows 2003
vlan0: rtl8139=11:11:11:11:01:01
  5. Config of failover-lp 94.23.Z.W on Windows 2003, netmask 255.255.255.0, gateway 94.23.Z.W
  6. Regedit of the netmask (SubnetMask key) to 255.255.255.255
    38982290.png


Tests over host:
Code: 
# brctl  showmacs vmbr0
port no    mac addr        is local?    ageing timer
  2    00:ff:af:c7:a2:32    yes           0.00
  1    22:f6:25:99:f8:22    yes           0.00

# # arp -a -n
? (91.121.X.251) at 00:1E:--:--:--:75 [ether] on eth0
? (91.121.X.250) at 00:1E:--:--:--:85 [ether] on eth0
? (91.121.X.254) at 00:00:--:--:AC:01 [ether] on eth0

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
94.23.Z.W    0.0.0.0         255.255.255.255 UH    0      0        0 vmbr0
94.23.Z.V    0.0.0.0         255.255.255.255 UH    0      0        0 vmbr0
91.121.X.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
91.121.X.0    0.0.0.0         255.255.255.0   U     0      0        0 vmbr0
0.0.0.0         91.121.X.254  0.0.0.0         UG    0      0        0 eth0
Tests over KVM (Win2003)
Code: 
>arp -a 
No se encontraron entradas ARP
(not arp entries found)

51586299.png


I can't connect to internet from the local machine, and if i try to connect to the kvm from the host, the one who responds my pings is the own host.

I tried different setups, creating a new bridge (vmbr1) with an internal IP (192.168.1.1) and configuring the KVM network over it (from qemu-server/101.conf) and also setting the 192.168.1.2 IP on it. No ICMP ping communication over them.

Again, I know this should be OVH responsibility and i'm not posting here asking for official support, just for a friend hand which can guide me a llittle bit, because all the guides i read are making me crazy.

I can't find the tapX interfaces the ovh guide tolds me, i have a dummy0 interface wich i don't know what does, the default network setup is different in the official release, the virtualized proxmox i configured at home over vmware doesn't allow me to create KVMs (i've no intel virtualizaton)....and the worst: I think I don't really understand how the bridges work, because i didn't use them in real life and trying to understand them in a "virtual way" is being a little bit hard to me.

Please sorry of my English, sorry if this is too much text and thank you in advance.
 
Last edited by a moderator:
djdiez said:
Again, I know this should be OVH responsibility and i'm not posting here asking for official support, just for a friend hand which can guide me a llittle bit, because all the guides i read are making me crazy.
Click to expand...

Anyways, OVH support is the right place to ask. This is the wrong forum.

- Dietmar
 
I know this from the first moment and i also posted it on the ovh forums.
As some other users write, OVH is a unmanaged dedicated provider. They bring you all the info they think you need and the rest is your part.

As i know that other OVH customers using proxmox ve wrote here and maybe they can read this and help a little bit, i posted here, trying to be as much polite as i can.

Not tryng to offend you dietmar, but every message with the "OVH" word receives a rough message from you...annoyed or even angry with them?
I know is a custom kernel, but it has to be to be provided in an easy autoinstallable format. The base (and the 95%) is your fantastic software, isn't it? And I think they're, in their way, promoting pve; I wouldn't know about it if I didn't find it in the virtualization distros select of OVH.

Well, I just don't wanna troll in this post, i'm only looking for some help.
Cheers! ;)
 
djdiez said:
Not tryng to offend you dietmar, but every message with the "OVH" word receives a rough message from you...annoyed or even angry with them?
Click to expand...

We are not annoyed or angry.

But OVH has a custom network setup (bridged network does not work there). So the right place to ask network related question is OVH support.

- Dietmar
 
dietmar said:
We are not annoyed or angry.

But OVH has a custom network setup (bridged network does not work there). So the right place to ask network related question is OVH support.

- Dietmar
Click to expand...

I just want to double this: as we cannot validate and test customs setups from hosting providers we cannot give high quality support and therefore we send users to the right place where you can get the fastest solution.

(I really appreciate that you give the OVH information in the beginning of your post - we are still loosing time because others do not tell the whole story)
 
Hi, now I understand the reason you can't support the custom versions.

The main problem is that OVH documentation is insufficient and incompatible with proxmox ve wiki and docs.

I thought i can't understand bridges, but now i think that is not my fault, is the OVH setup wich is not working as expected.

Someone uses OVH proxmox 1.2 and make KVM network work?
 
Yep, the OVH guide isn't up to date :(
Use the realtek8149, no mac adress change necessary.
Just set your failover or additional ip, the default mask (255.0.0.0), the host ip for the gateway and the dns server ip.
That s all :)

After, you can download intel's driver for e1000 (http://www.proxmox.com/forum/showpost.php?p=6996&postcount=2 )
Shutdown the vm, delete the ethernet device, setup a new ethernet device e1000, restart the vm...

That's just a simple configuration but it's functional :)

A small oversight, do not forget to add the route on the host, as indicated in the ovh guide (# route on the host to verify and # ip route add VOTRE_IP_FAILOVER dev vmbr0)
 
Last edited:
flying said:
Use the realtek8149, no mac adress change necessary. Just set your failover or additional ip, the default mask (255.0.0.0), the host ip for the gateway and the dns server ip. That s all :)
Click to expand...

I'm currently using the rtl8139, just changed the mac address to control them easier. Could that be a problem?
I can't setup this in the Win2003 machine:
IP: 94.23.Z.W ( the first fail-over IP, used in eth0:0 @ host)
GW: 91.121.X.Y ( the main IP @ host)
MASK: 255.0.0.0
DNS: 213.186.33.99 (OVH nameserver)
Because the gateway would be in a different subnet.
Using other failover IP (eth0:1 @ host) as gateway gives the same connectivity: none. The win2003 network interface seems to send packets, but not receive anything. Later, in the host, i can see the vmtab101i0 interface having some more packets in the RX packets.

flying said:
After, you can download intel's driver for e1000 (http://www.proxmox.com/forum/showpost.php?p=6996&postcount=2 )
Shutdown the vm, delete the ethernet device, setup a new ethernet device e1000, restart the vm... That's just a simple configuration but it's functional :)
Click to expand...
I'd like to have network connectivity first, the performance of e1000 is just in a second place now.

flying said:
A small oversight, do not forget to add the route on the host, as indicated in the ovh guide (# route on the host to verify and # ip route add VOTRE_IP_FAILOVER dev vmbr0)
Click to expand...
I've already done that and is detailed in the first post, this is the route result:
Code: 
# route -n
Kernel IP routing table Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
94.23.Z.W    0.0.0.0         255.255.255.255 UH    0      0        0 vmbr0
94.23.Z.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
91.121.X.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
91.121.X.0    0.0.0.0         255.255.255.0   U     0      0        0 vmbr0
0.0.0.0         91.121.X.254  0.0.0.0         UG    0      0        0 eth0
The question is: does the bridge has to be connected to the eth0 interface?

Code: 
 #brctl show
bridge name    bridge id        STP enabled    interfaces
vmbr0        8000.2af884f29d98    no        dummy0
                              vmtab101i0
 
this is my ovh custom conf (replace X.X.X.X with your value)


auto tap0
iface tap0 inet manual
tunctl_user root


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address X.X.X.X
netmask 255.255.255.0
network X.X.X.X
broadcast X.X.X.255
gateway X.X.X.X


auto vmbr0
iface vmbr0 inet static
address 192.168.49.1
netmask 255.255.255.0
network 192.168.49.0
broadcast 255.255.255.0
post-up chmod ugo+rw /dev/net/tun
bridge_ports tap0
bridge-ageing 7200
bridge-fd 0

make a iptables firewall for nat and routing with the bridge interface on 192.168.49.0 network et make nat rule ni relation.

it's works on more then 4 ovh server.
 
:( I had not seen the changes you have made...

I made this on a out of box ovh server with "ovh" poxmox 1.2

The previous installation of the server was a "proxmox ovh 0.9beta", when I wanted to re-import the KVM vm, no network...

By chance, I left the default netmask and the network was functional :eek:

I only had the route for the old kvm vm, the configuration file between 0.9 and 1.2, are a little different :)

With an openvz vm and two kvm vm :
Code: 
# ifconfig
dummy0    Link encap:Ethernet  HWaddr 52:11:f1:de:01:09
          ...

eth0      Link encap:Ethernet  HWaddr 00:19:d1:97:c5:5d
          ...

lo        Link encap:Boucle locale
          ...

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          ...

vmbr0     Link encap:Ethernet  HWaddr 52:11:f1:de:01:09
          ...

vmtab105i0 Link encap:Ethernet  HWaddr 00:ff:ed:c1:f2:46
          ...

vmtab107i0 Link encap:Ethernet  HWaddr 00:ff:6d:9c:6b:63
          ...
I can't help you to reconfigure your network configuration :(
 
Last edited:
flying: dont worry, thank you. all help is welcome.

teleadmin: thank you, i'll try your config, looks promising!
 
Finally i maked it work, using the base of teleadmin's config.

I cleared the OVH config and used a LAN IP setup on the vmbr0 interface, using an IP of the same network on the KVM machine and...voila!
I'm sure i had tested this way before and didn't get it working...maybe that time i was using the e1000 driver on win2003 withouth the official drivers and that broke all everything, but i can't remember, i tried to set it working so different ways that i'was almost jumping when i saw it working.

Thank you everyone who helped me!
 
Hi all OVH users,

the solution is pretty simple. When you follow the OVH help:

http://hilfe.ovh.de/proxmox

you will fail because of missing proxyarp support of the bridge. The following line does the magic:

echo 1 > /proc/sys/net/ipv4/conf/vmbr0/proxy_arp

Add this to: /etc/pve/kvm-networking.sh to make sure, that everything works again after a reboot.

With this simple modification OVH's help mentioned above will work.

cheers
frantek
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back