Proxmox VE 5.0 Beta1 Issue

elurex · Mar 23, 2017

After upgrading to PVE 5.0 beta1, I have following issue

After upgrading to proxmox ve 5.0 beta1 via apt, try to run apt update && apt upgrade always gets the following msg

Code:

The following packages have been kept back:
  corosync-pve dmeventd dmsetup libcorosync4-pve libdevmapper-event1.02.1 liblvm2cmd2.02 lvm2 openvswitch-switch
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.

Unable to set jumbo frames the following setting in /etc/network/interfaces failed to work

Code:

allow-vmbr1 bond1
iface bond1 inet manual
        ovs_bonds eth2 eth3
        ovs_type OVSBond
        ovs_bridge vmbr1
        ovs_options bond_mode=balance-slb lacp=active
        post-up ifconfig eth2 mtu 9000 && ifconfig eth3 mtu 9000 && ifconfig bond1 mtu 9000

must comment out post-up line

Autostart vm/lxc failed to work... must manually start vm/lxc

According to kernel 4.10 documentation, KVMGT is enabled, how do I assign GVT-D in PVE 5.0?

preferrring to https://kernelnewbies.org/Linux_4.10#head-6b7d1bd2f7247da9c87798a91e10302b0cc32331

12. Drivers
12.1. Graphics

Add initial ZTE VOU display driver commit
Add driver for Amlogic Meson Graphic Controller on GXBB/GXL/GXM socs commit
Add driver for MXSFB controller commit
Intel
- Add GVT-g device model, which allows the virtualization of GPU resources (merge), (merge)

tom · Mar 23, 2017

elurex said:
apt update && apt upgrade

please always "apt-get dist-upgrade" or "apt dist-upgrade"

apt-get upgrade will ALWAYS breaks Proxmox VE.

elurex · Mar 23, 2017

tom said:
please always "apt-get dist-upgrade" or "apt dist-upgrade"

apt-get upgrade will ALWAYS breaks Proxmox VE.

Dear Tom,

I ran the following commands/steps

zfs rollback rpool/ROOT/pve-1@2017-03-23
reboot
apt update && apt dist-upgrade
I still having the same three errors in my original post

dietmar · Mar 23, 2017

Please can you run the suggested commands (apt-get instead of apt)?

elurex · Mar 23, 2017

should I change /etc/apt/source.list first line
deb http://ftp.tw.debian.org/debian jessie main contrib to
deb http://ftp.tw.debian.org/debian stretch main contrib

I will try apt-get dist-upgrade again

Alessandro 123 · Mar 23, 2017

tom said:
please always "apt-get dist-upgrade" or "apt dist-upgrade"

apt-get upgrade will ALWAYS breaks Proxmox VE.

Is "update" needed or only directly "dist-upgrade" ?

elurex · Mar 23, 2017

#1 issue solved! I changed the content of my /etc/apt/source.list to following content

Code:

deb http://ftp.tw.debian.org/debian stretch  main contrib

# security updates
deb http://security.debian.org stretch/updates main contrib

#deb http://download.proxmox.com/debian jessie pve-no-subscription

deb http://download.proxmox.com/debian/pve stretch pvetest

Ivan Dimitrov · Mar 23, 2017

Hi, I jumped the gun and upgraded with apt-get update; apt-get dist-upgrade and also got the error:

Code:

apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  corosync-pve dmeventd dmsetup libcorosync4-pve libdevmapper-event1.02.1 liblvm2cmd2.02 lvm2
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.

If I add the stretch repos the next apt-get update; apt-get dist-upgrade is saying

Code:

apt-get dist-upgrade
511 upgraded, 157 newly installed, 10 to remove and 0 not upgraded.

Do you recommend updating the whole distro to Stretch or should we run the 5.0 beta still on the Jessie platform?

tom · Mar 23, 2017

5.0 is for stretch only.

elurex · Mar 24, 2017

more information on issue #2 jumbo frame

It seems that ixgbe on Debian Stretch is unable to set mtu from 1500 to 9000
dmesg reports the following error

NIC is intel x520-da2

Code:

 eth2: Invalid MTU 9000 requested, hw max 1500

either using
ifconfig eth<x> mtu 9000 up (stated in intel ixgbe 5.0.4 release note )
or
ip link set eth<x> mtu 9000
both command fails

hec · Mar 24, 2017

I have the problem that i can set the MTU 9000 und the physical interfaces (x710) but i can't set the mtu on the ovs bond.

Code:

allow-vmbr1 bond0
iface bond0 inet manual
    ovs_bonds eth3 eth7
    ovs_type OVSBond
    ovs_bridge vmbr1
        pre-up ( ifconfig eth3 mtu 9000 && ifconfig eth7 mtu 9000 )
    ovs_options bond_mode=balance-tcp lacp=active
    mtu 9000

auto vmbr0
iface vmbr0 inet static
    address  192.168.61.85
    netmask  255.255.255.0
    gateway  192.168.61.1
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0

auto vmbr1
iface vmbr1 inet manual
    ovs_type OVSBridge
    ovs_ports bond0 vlan50
    mtu 9000

allow-vmbr1 vlan50
iface vlan50 inet static
    address  192.168.50.85
    netmask  255.255.255.0
    ovs_type OVSIntPort
    ovs_bridge vmbr1
    ovs_options tag=50
    mtu 9000

czechsys · Mar 24, 2017

Code:

post-up ifconfig eth2 mtu 9000 && ifconfig eth3 mtu 9000 && ifconfig bond1 mtu 9000

ifconfig is deprecated and package containing it by default not installed on stretch.

hec · Mar 24, 2017

i tried ip link too but same problem

Code:

ip link set mtu 9000 dev eth3
ip link set mtu 9000 dev eth7
ip link set mtu 9000 dev bond0
RTNETLINK answers: Invalid argument

czechsys · Mar 24, 2017

elurex said:
more information on issue #2 jumbo frame

NIC is intel x520-da2

Code:

eth2: Invalid MTU 9000 requested, hw max 1500

This is interesting. I have x520-da2 on HP G7 servers, pve 4.4, ixgbe 4.4.6, mtu 9k is working. Can you test your card in pve 4.4 or in different ixgbe version?

elurex · Mar 24, 2017

czechsys said:
This is interesting. I have x520-da2 on HP G7 servers, pve 4.4, ixgbe 4.4.6, mtu 9k is working. Can you test your card in pve 4.4 or in different ixgbe version?

pve 4.4 works flawlessly with mtu 9000 jumbo frame. this issue maybe a kernel issue more than a pve issue

czechsys · Mar 27, 2017

Just for info, i have supermicro servers on D9 stretch with network interfaces based on same chipset family for x520-da2 and 9k mtu is working.

fabian · Mar 27, 2017

yes, seems like the latest drivers from intel do not yet fully support kernels >= 4.8.

fabian · Mar 27, 2017

czechsys said:
Just for info, i have supermicro servers on D9 stretch with network interfaces based on same chipset family for x520-da2 and 9k mtu is working.

the Debian kernel uses the stock Linux intel drivers, which share a common root and the names with the ones from intel. for e1000e, igb and ixgbe PVE uses the one from intel (they were requested by users because of better support for some hardware features), which are rather different (and sometimes lag behind the upstream kernel development, unfortunately).

Firebug24k · Apr 22, 2017

Any news on getting jumbo frames working?

fabian · Apr 24, 2017

OVS, bond and team devices should handle it correctly in the current kernel. Some IB and intel drivers are still lacking the required changes.

Proxmox VE 5.0 Beta1 Issue

Active Member

Proxmox Staff Member

Active Member

Proxmox Staff Member

Active Member

Well-Known Member

Active Member

Renowned Member

Proxmox Staff Member

Active Member

Renowned Member

Renowned Member

Renowned Member

Renowned Member

Active Member

Renowned Member

Proxmox Staff Member

Proxmox Staff Member

New Member

Proxmox Staff Member