[PVE-User] Loosing network connectivity in a VM
dORSY
dorsyka at yahoo.com
Tue Jan 2 19:54:28 CET 2018
What does stops responding mean?
Is there anything in the host's logs (bridge/networking related)?
What do you see in the vm's when its happening? Is interface up? Is there an IP? What are the routes?
We had for example this bug for a while (tough it made only warnings for me):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715609
On Tuesday, 2 January 2018, 19:28:30 CET, Mark Schouten <mark at tuxis.nl> wrote:
I just had it again. Toggling the 'disconnect' checkbox in Proxmox 'fixes' the issue.
I do not use bonding. It is as simple as it gets. A bridge on a 10Gbit interface.
Do you have a link about these virtio issues in 4.10 ?
Met vriendelijke groeten,
--
Kerio Operator in de Cloud? https://www.kerioindecloud.nl/
Mark Schouten | Tuxis Internet Engineering
KvK: 61527076 | http://www.tuxis.nl/
T: 0318 200208 | info at tuxis.nl
Van: Alexandre DERUMIER <aderumier at odiso.com>
Aan: proxmoxve <pve-user at pve.proxmox.com>
Verzonden: 2-1-2018 17:49
Onderwerp: Re: [PVE-User] Loosing network connectivity in a VM
Try to upgrade to kernel 4.13, they are known virtio bug in 4.10.
(no sure it's related, but it could help)
do you use bonding on your host ? if yes, which mode ?
----- Mail original -----
De: "Mark Schouten" <mark at tuxis.nl>
À: "proxmoxve" <pve-user at pve.proxmox.com>
Envoyé: Mardi 2 Janvier 2018 13:41:43
Objet: [PVE-User] Loosing network connectivity in a VM
Hi,
I have a VM running Debian Stretch, with three interfaces. Two VirtIO
interfaces and one E1000.
In the last few days one of the Virtio interfaces stopped responding. The
other interfaces are working flawlessly.
The Virtio-interface in question is the busiest interface, but at the moment
the the interface stops responding, it's not busy at all.
tcpdump shows me ARP-traffic going out, but nothing coming back.
I experienced this with other VM's on this (physical) machine as, making me
believe it is a new bug in KVM/Virtio.
The config of the VM is quite default, as is the config for other VM's on which
I experienced this same issue.
Has anybody seen this behaviour before, does anyone have an idea what to do
about it?
root at host02:~# pveversion
pve-manager/5.0-30/5ab26bc (running kernel: 4.10.17-2-pve)
# info version
2.9.0pve-qemu-kvm_2.9.0-4
--
Kerio Operator in de Cloud? https://www.kerioindecloud.nl/
Mark Schouten | Tuxis Internet Engineering
KvK: 61527076 | http://www.tuxis.nl/
T: 0318 200208 | info at tuxis.nl
_______________________________________________
pve-user mailing list
pve-user at pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
pve-user at pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
pve-user at pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
More information about the pve-user
mailing list