Network Interfaces (NICs)
How to configure the virtual network interface on a VM running on Zenon's Proxmox infrastructure.
MTU: use 1500
The default MTU on Zenon's Proxmox bridges is 9000 (jumbo frames). We recommend setting the MTU to 1500 on your VM's NIC for all normal use.
Jumbo frames only work if every device on the path supports them. Most traffic leaves the VM towards networks, services and the internet that use 1500, so a VM inheriting 9000 can end up sending packets that are too large for the path. Typical symptoms:
- Small requests work (ping, SSH login, DNS), but large transfers hang or stall.
- TLS handshakes time out, or
git/curl/package downloads freeze partway through. - Problems that only appear towards some destinations or through VPNs and tunnels.
Path MTU discovery is supposed to handle this, but it depends on ICMP messages that are often filtered along the way. Using 1500 avoids the problem altogether.
Only use 9000 if you have a specific need for jumbo frames and have confirmed that every hop between the endpoints supports it. Contact Zenon if you are unsure.
Setting the MTU on the VM NIC
In the Proxmox UI, open the VM, go to Hardware, edit the Network Device, and set MTU to 1500.
Note that:
- The MTU field is only available for the VirtIO NIC model, which is also the model we recommend.
- The value
1means "inherit the bridge MTU", which on Zenon's bridges is 9000. Don't leave it at1unless you actually want jumbo frames.
Verify inside the VM after a restart (or after re-plugging the NIC):
ip link show # look for "mtu 1500" on the interface
If the guest still shows a different MTU, set it explicitly in the guest's network configuration so it doesn't depend on DHCP or defaults. For example with netplan:
network:
version: 2
ethernets:
ens18:
mtu: 1500
Verify the path
To check that full-size packets make it through to a destination, ping with the don't-fragment flag. A 1500 MTU leaves room for 1472 bytes of payload (1500 minus 20 for IP and 8 for ICMP):
ping -M do -s 1472 <destination>
If this fails with "message too long" or gets no replies while smaller sizes work, there is an MTU problem somewhere on the path.
Other recommendations
- Use the VirtIO network model. It has the best performance, and the VirtIO drivers for Windows are available on the same ISO as the QEMU Guest Agent.
- Keep the MTU consistent across all NICs on the VM that connect to the same network.