VM's network stopped working

[toxiicdev]

Hello guys, It's really urgent here.

Since this night 4 AM, my VM's network stopped working.

They are all fine, even setting up a new one results in no network working..

 

[Richard]

What exactly measns

Since this night 4 AM, my VM's network stopped working.

They are all fine, even setting up a new one results in no network working..

??

How are networks configured and what does not work any more?

 

[Benjamin Hodgens]

I had this problem when i was using bridged networking w/ an old crappy unmanaged switch. New VMs or restarted VMs had no network connectivity. Never figured it out precisely but haven't had the problem in months - i've since upgraded and replaced the switch.

 

[Benjamin Hodgens]

I have now had this problem again, but I'm unsure how to produce it or provide diagnostic information - is there any way to file a bug officially with a core by non-paying customers?

This is all 'professional' equipment (Dell 410s) which has been largely upgraded since the last time I had the problem, with a managed Procurve gigE switch (last time it was an unmanaged netgear gigE).

The configuration is similar to before, but on the current proxmox 4.1 (not 3.x as previously): bridged networking. Doesn't seem to make a

The first time I had the issue (on 3.x), rebooting didn't seem to make a difference (IIRC - it was 5+ months ago). That was when I upgraded to 4.1, thinking perhaps that would help (and if not, I was going to have to use something else).

Logs when the VM starts up look about as you'd expect (I think):

[ 1318.537900] device tap104i1 entered promiscuous mode
[ 1318.542051] vmbr0: port 6(tap104i1) entered forwarding state
[ 1318.542062] vmbr0: port 6(tap104i1) entered forwarding state
[ 1321.743710] kvm: zapping shadow pages for mmio generation wraparound
[ 1321.748838] kvm: zapping shadow pages for mmio generation wraparound
[ 1624.763622] device tap108i0 entered promiscuous mode
[ 1624.767934] vmbr0: port 7(tap108i0) entered forwarding state
[ 1624.767945] vmbr0: port 7(tap108i0) entered forwarding state

This only appears to be with new VMs... I can start and run older provisioned VMs, but if I try to create a new VM I have this problem. This time, it's with OpenSuSE installer (both Tumbleweed and Leap 43.1). I can't get a dhcp lease, or talk to the network in any way (manual config in VM, etc.).

I haven't tried rebooting this time, I'm afraid I won't be able to start any of the VMs...

 

[Richard]

I have now had this problem again, but I'm unsure how to produce it or provide diagnostic information - is there any way to file a bug officially with a core by non-paying customers?

This is all 'professional' equipment (Dell 410s) which has been largely upgraded since the last time I had the problem, with a managed Procurve gigE switch (last time it was an unmanaged netgear gigE).

The configuration is similar to before, but on the current proxmox 4.1 (not 3.x as previously): bridged networking. Doesn't seem to make a

The first time I had the issue (on 3.x), rebooting didn't seem to make a difference (IIRC - it was 5+ months ago). That was when I upgraded to 4.1, thinking perhaps that would help (and if not, I was going to have to use something else).

Logs when the VM starts up look about as you'd expect (I think):

[ 1318.537900] device tap104i1 entered promiscuous mode
[ 1318.542051] vmbr0: port 6(tap104i1) entered forwarding state
[ 1318.542062] vmbr0: port 6(tap104i1) entered forwarding state
[ 1321.743710] kvm: zapping shadow pages for mmio generation wraparound
[ 1321.748838] kvm: zapping shadow pages for mmio generation wraparound
[ 1624.763622] device tap108i0 entered promiscuous mode
[ 1624.767934] vmbr0: port 7(tap108i0) entered forwarding state
[ 1624.767945] vmbr0: port 7(tap108i0) entered forwarding state

This only appears to be with new VMs... I can start and run older provisioned VMs, but if I try to create a new VM I have this problem. This time, it's with OpenSuSE installer (both Tumbleweed and Leap 43.1). I can't get a dhcp lease, or talk to the network in any way (manual config in VM, etc.).

I haven't tried rebooting this time, I'm afraid I won't be able to start any of the VMs...

Unfortunately "this problem" is still not specified yet. It would be helpful to post

- content of /etc/netwwork/interfaces

- config file of the VM

- which traffic relation (ping from x to y) does work and which does not

 

[Norberto Iannicelli]

I'm with a similar problem, but it affects the nodes.
Before the last update was fine, I restarted the servers and the problems started.

I have set bond-tlb and was working fine, now I'm having to use only one eth, if I connect the cable to the other port eth entire cluster goes down, restarting all nodes. And not to, is turning on and off all the time. Someone is going through something like that?

-------------------
proxmox-ve: 4.2-58 (running kernel: 4.4.13-2-pve) pve-manager: 4.2-17 (running version: 4.2-17/e1400248) pve-kernel-4.4.6-1-pve: 4.4.6-48 pve-kernel-4.4.13-1-pve: 4.4.13-56 pve-kernel-4.4.8-1-pve: 4.4.8-52 pve-kernel-4.4.13-2-pve: 4.4.13-58 pve-kernel-4.4.10-1-pve: 4.4.10-54 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1 pve-cluster: 4.0-43 qemu-server: 4.0-85 pve-firmware: 1.1-8 libpve-common-perl: 4.0-71 libpve-access-control: 4.0-18 libpve-storage-perl: 4.0-56 pve-libspice-server1: 0.12.8-1 vncterm: 1.2-1 pve-qemu-kvm: 2.6-1 pve-container: 1.0-71 pve-firewall: 2.0-29 pve-ha-manager: 1.0-32 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u2 lxc-pve: 1.1.5-7 lxcfs: 2.0.0-pve2 cgmanager: 0.39-pve1 criu: 1.6.0-1 zfsutils: 0.6.5.7-pve10~bpo80
--------------------

--------------------
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_miimon 100
bond_mode balance-tlb

auto vmbr0
iface vmbr0 inet static
address 192.168.1.1
netmask 255.255.255.0
gateway 192.168.1.254
bridge_ports bond0
bridge_stp on
bridge_fd 0
post-up echo 1 > /proc/sys/net/ipv4/ip_forward