I volunteer for a small charity that provides hospital radio, and I'm in the process of upgrading their infrastructure to something more this decade than last. I'm coming from relatively good experience on PVE <= 3.4, but 4.0 seems to be beating me. This should "just work"? But it doesn't... and I've been banging my head on the desk for the last 4 hours trying various things. Any help appreciated.
All of the network is on 192.168.0.0/24. Client PC's, Proxmox host, and VM's. All connected via a Cisco Gigabit switch (managed, but all management 'off' ... just in dumb unmanaged switch mode). The router for the subnet is 192.168.0.1 out to the internet. eth0 and eth1 are bonded, and this works fine, too.
cat /proc/net/bonding/bond0
pveversion -v
/etc/network/interfaces
Proxmox itself (192.168.0.210): Can access the local network and internet, and can ping all VM's.
OpenMediaVault KVM (192.168.0.213): as above.
lxc LEMP stack (192.168.0.212): as above.
Windows 7 Pro (192.168.0.100): No local network, no internet. Can ping itself and Proxmox IP only. Also cannot ping other VM's.
What magic am I missing here? The OpenMediaVault install went flawlessly, and the same details were provided for the Windows 7 VM (excepting the IP address of course), and that isn't working at all.
Windows 7 is using virtio, just as the OpenMediaVault install is. Drivers installed and working fine (allegedly). Even tried switching to E1000 just to disprove to myself that it wasn't driver-related, but no change.
Any help really, really, appreciated
Proxmox to router:
OpenMediaVault KVM to router:
Windows to router:
No easy way to copy and paste this one but essentially 100% packet loss with 192.168.0.100: Destination host unreachable.
Yet pinging the Proxmox host or itself works fine, but no other VM's, or anything else on the network or the internet.
All of the network is on 192.168.0.0/24. Client PC's, Proxmox host, and VM's. All connected via a Cisco Gigabit switch (managed, but all management 'off' ... just in dumb unmanaged switch mode). The router for the subnet is 192.168.0.1 out to the internet. eth0 and eth1 are bonded, and this works fine, too.
cat /proc/net/bonding/bond0
Code:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:23:7d:5b:ae:ae
Slave queue ID: 0
Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:23:7d:5b:ae:ac
Slave queue ID: 0pveversion -v
Code:
proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve)
pve-manager: 4.0-48 (running version: 4.0-48/0d8559d0)
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-22
qemu-server: 4.0-30
pve-firmware: 1.1-7
libpve-common-perl: 4.0-29
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-25
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-9
pve-container: 1.0-6
pve-firewall: 2.0-12
pve-ha-manager: 1.0-9
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.3-1
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
criu: 1.6.0-1
zfsutils: 0.6.5-pve4~jessie/etc/network/interfaces
Code:
auto lo
iface lo inet loopback
#auto eth0
#iface eth0 inet manual
#auto eth1
#iface eth1 inet manual
auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_miimon 100
bond-mode balance-rr
# bond-lacp-rate 0
auto vmbr0
iface vmbr0 inet static
address 192.168.0.210
netmask 255.255.255.0
gateway 192.168.0.1
bridge_ports bond0
bridge_stp off
bridge_fd 0Proxmox itself (192.168.0.210): Can access the local network and internet, and can ping all VM's.
OpenMediaVault KVM (192.168.0.213): as above.
lxc LEMP stack (192.168.0.212): as above.
Windows 7 Pro (192.168.0.100): No local network, no internet. Can ping itself and Proxmox IP only. Also cannot ping other VM's.
What magic am I missing here? The OpenMediaVault install went flawlessly, and the same details were provided for the Windows 7 VM (excepting the IP address of course), and that isn't working at all.
Windows 7 is using virtio, just as the OpenMediaVault install is. Drivers installed and working fine (allegedly). Even tried switching to E1000 just to disprove to myself that it wasn't driver-related, but no change.
Any help really, really, appreciated
Proxmox to router:
Code:
root@proxmox0:/etc/vz# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.892 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.897 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.918 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 0.892/1.062/1.544/0.280 msOpenMediaVault KVM to router:
Code:
root@fileserver:~# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_req=1 ttl=64 time=1.60 ms
64 bytes from 192.168.0.1: icmp_req=2 ttl=64 time=1.07 ms
64 bytes from 192.168.0.1: icmp_req=3 ttl=64 time=1.06 ms
64 bytes from 192.168.0.1: icmp_req=4 ttl=64 time=1.10 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 1.061/1.212/1.605/0.229 msWindows to router:
No easy way to copy and paste this one but essentially 100% packet loss with 192.168.0.100: Destination host unreachable.
Yet pinging the Proxmox host or itself works fine, but no other VM's, or anything else on the network or the internet.
Last edited:
