Sounds promising. What motherboard and graphics card you're using with it and how does it perform ?
Proxmox VE 5.0 beta1 released!
- Thread starter martin
- Start date
Sounds promising. What motherboard and graphics card you're using with it and how does it perform ?
I have the same problem, any solutions for this? im using an ssd formated disk clean partition. i have made format both in GPT and MBR with no sucess. could it be something with legacy boot /Uefi?
Last edited:
Please search the forum for " /dev/sda3"
This issue is already in several threads.
5.0 will stay on 4.10, if there are important fixes for BTFRS its very likely they got backported.
I know that you guys are currently relying on the Debian packages for OpenVswitch, but as you're probably aware, their packaged binary is does not have the DPDK options compiled in, which ought to result in a huge network performance boost.
What are the odds of maintaining a DPDK enhanced OpenVswitch package out of the PVE repo?
What are the odds of maintaining a DPDK enhanced OpenVswitch package out of the PVE repo?
we build our own (-switch and -common packages, that is), and Alexandre recently proposed to enable DPDK:
https://pve.proxmox.com/pipermail/pve-devel/2017-April/026070.html
We would also greatly appreciate ovs 2.7 to include DPDK. The next version of ovs is also to include dot1q-tunnel port mode and multiple VLAN tag support (both QinQ and 802.1ad). This would also take advantage of new capabilities in kernel 4.10 to accelerate these functions in the kernel, as opposed to userland.
The dot1q-tunnel feature should also provide protection from customers being able to generate DoS traffic via the publicised "Double tagged VLAN hopping" vulnerability, which currently affects nearly all virtualisation environments.
Posted a feature request here:
https://bugzilla.proxmox.com/show_bug.cgi?id=1350
The dot1q-tunnel feature should also provide protection from customers being able to generate DoS traffic via the publicised "Double tagged VLAN hopping" vulnerability, which currently affects nearly all virtualisation environments.
Posted a feature request here:
https://bugzilla.proxmox.com/show_bug.cgi?id=1350
Hello, I upgraded 4.4 to 5.0beta1 with no error to report but now, I've added a Intel x540-t2 10GBe adapters and the system doesn't recognize them. I see them with "lspci -nnn" as:
81:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Server Bypass Adapter [8086:155c] (rev 01)
81:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Server Bypass Adapter [8086:155c] (rev 01)
Dmesg shows nothing and there is nothing new in /etc/udev/rules.d/70-persistent-net.rules.
I tried to compile the driver from Intel and it fails with "error: unknown type name ‘cycle_t’" see below.
CC [M] /usr/src/ixgbe-5.0.4/src/ixgbe_fcoe.o
CC [M] /usr/src/ixgbe-5.0.4/src/ixgbe_ptp.o
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:247:8: error: unknown type name ‘cycle_t’
static cycle_t ixgbe_ptp_read_X550(const struct cyclecounter *hw_cc) {
^~~~~~~
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:283:8: error: unknown type name ‘cycle_t’
static cycle_t ixgbe_ptp_read_82599(const struct cyclecounter *hw_cc)
^~~~~~~
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c: In function ‘ixgbe_ptp_start_cyclecounter’:
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:1128:11: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
cc.read = ixgbe_ptp_read_X550;
^
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:1143:11: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
cc.read = ixgbe_ptp_read_82599;
^
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:1149:11: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
cc.read = ixgbe_ptp_read_82599;
^
cc1: some warnings being treated as errors
scripts/Makefile.build:294: recipe for target '/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.o' failed
make[2]: *** [/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.o] Error 1
Makefile:1524: recipe for target '_module_/usr/src/ixgbe-5.0.4/src' failed
make[1]: *** [_module_/usr/src/ixgbe-5.0.4/src] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.10.8-1-pve'
Makefile:107: recipe for target 'default' failed
make: *** [default] Error 2
make: Leaving directory '/usr/src/ixgbe-5.0.4/src'
Is 5.0-beta1 too bleeding edge for to run this adapter? Is this possibly a known issue? What are my next steps?
TIA
81:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Server Bypass Adapter [8086:155c] (rev 01)
81:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Server Bypass Adapter [8086:155c] (rev 01)
Dmesg shows nothing and there is nothing new in /etc/udev/rules.d/70-persistent-net.rules.
I tried to compile the driver from Intel and it fails with "error: unknown type name ‘cycle_t’" see below.
CC [M] /usr/src/ixgbe-5.0.4/src/ixgbe_fcoe.o
CC [M] /usr/src/ixgbe-5.0.4/src/ixgbe_ptp.o
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:247:8: error: unknown type name ‘cycle_t’
static cycle_t ixgbe_ptp_read_X550(const struct cyclecounter *hw_cc) {
^~~~~~~
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:283:8: error: unknown type name ‘cycle_t’
static cycle_t ixgbe_ptp_read_82599(const struct cyclecounter *hw_cc)
^~~~~~~
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c: In function ‘ixgbe_ptp_start_cyclecounter’:
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:1128:11: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
cc.read = ixgbe_ptp_read_X550;
^
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:1143:11: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
cc.read = ixgbe_ptp_read_82599;
^
/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.c:1149:11: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
cc.read = ixgbe_ptp_read_82599;
^
cc1: some warnings being treated as errors
scripts/Makefile.build:294: recipe for target '/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.o' failed
make[2]: *** [/usr/src/ixgbe-5.0.4/src/ixgbe_ptp.o] Error 1
Makefile:1524: recipe for target '_module_/usr/src/ixgbe-5.0.4/src' failed
make[1]: *** [_module_/usr/src/ixgbe-5.0.4/src] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.10.8-1-pve'
Makefile:107: recipe for target 'default' failed
make: *** [default] Error 2
make: Leaving directory '/usr/src/ixgbe-5.0.4/src'
Is 5.0-beta1 too bleeding edge for to run this adapter? Is this possibly a known issue? What are my next steps?
TIA
Is there another pvetest? I've configured and updated "deb http://download.proxmox.com/debian/pve stretch pvetest" ... unsure of what you mean!
ip link show
(edited)
=========================
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
5: eth3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
7: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr2 state UP mode DEFAULT group default qlen 1000
9: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
pveversion -v
=========================
proxmox-ve: 5.0-7 (running kernel: 4.10.8-1-pve)
pve-manager: 5.0-10 (running version: 5.0-10/0d270679)
pve-kernel-4.4.40-1-pve: 4.4.40-82
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.10.1-2-pve: 4.10.1-2
pve-kernel-4.4.24-1-pve: 4.4.24-72
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.10.8-1-pve: 4.10.8-7
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.4.44-1-pve: 4.4.44-84
libpve-http-server-perl: 2.0-4
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-7
qemu-server: 5.0-4
pve-firmware: 2.0-2
libpve-common-perl: 5.0-11
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-4
libpve-storage-perl: 5.0-3
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.9.0-1
pve-container: 2.0-6
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-1
lxcfs: 2.0.7-pve1
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
Thank you
EDIT: I think this board being a special "bypass" version has a source code branch that is different from the standard driver in the kernel. I'm still investigating but am 99.9% sure this is the problem. Any Intel dev's out there who can help me figure out how to obtain the driver?
EDIT x2: Warning regarding the X540-T2BP adapter. I've been in touch with the developer at Intel and he states the card requires a special driver that is not generally available to the public. OEM / Developer only. He forwarded a request for the driver on my behalf but I have not heard back and suspect I won't.
ip link show
(edited)
=========================
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
5: eth3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
7: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr2 state UP mode DEFAULT group default qlen 1000
9: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
pveversion -v
=========================
proxmox-ve: 5.0-7 (running kernel: 4.10.8-1-pve)
pve-manager: 5.0-10 (running version: 5.0-10/0d270679)
pve-kernel-4.4.40-1-pve: 4.4.40-82
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.10.1-2-pve: 4.10.1-2
pve-kernel-4.4.24-1-pve: 4.4.24-72
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.10.8-1-pve: 4.10.8-7
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.4.44-1-pve: 4.4.44-84
libpve-http-server-perl: 2.0-4
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-7
qemu-server: 5.0-4
pve-firmware: 2.0-2
libpve-common-perl: 5.0-11
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-4
libpve-storage-perl: 5.0-3
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.9.0-1
pve-container: 2.0-6
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-1
lxcfs: 2.0.7-pve1
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
Thank you
EDIT: I think this board being a special "bypass" version has a source code branch that is different from the standard driver in the kernel. I'm still investigating but am 99.9% sure this is the problem. Any Intel dev's out there who can help me figure out how to obtain the driver?
EDIT x2: Warning regarding the X540-T2BP adapter. I've been in touch with the developer at Intel and he states the card requires a special driver that is not generally available to the public. OEM / Developer only. He forwarded a request for the driver on my behalf but I have not heard back and suspect I won't.
Last edited:
Since i updated from 4.4 to 5.0, the syslog is almost completely filled with weird messages.
/var/log/syslog
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cost in numeric lt (<) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cost in numeric lt (<) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
pveversion -v
proxmox-ve: 5.0-7 (running kernel: 4.10.8-1-pve)
pve-manager: 5.0-10 (running version: 5.0-10/0d270679)
pve-kernel-4.10.8-1-pve: 4.10.8-7
libpve-http-server-perl: 2.0-4
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-7
qemu-server: 5.0-4
pve-firmware: 2.0-2
libpve-common-perl: 5.0-11
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-4
libpve-storage-perl: 5.0-3
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.9.0-1
pve-container: 2.0-6
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-1
lxcfs: 2.0.7-pve1
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
/var/log/syslog
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cost in numeric lt (<) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cost in numeric lt (<) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
May 16 19:11:42 pve pvestatd[2927]: Use of uninitialized value $cur_cost in subtraction (-) at /usr/share/perl5/PVE/Service/pvestatd.pm line 344.
pveversion -v
proxmox-ve: 5.0-7 (running kernel: 4.10.8-1-pve)
pve-manager: 5.0-10 (running version: 5.0-10/0d270679)
pve-kernel-4.10.8-1-pve: 4.10.8-7
libpve-http-server-perl: 2.0-4
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-7
qemu-server: 5.0-4
pve-firmware: 2.0-2
libpve-common-perl: 5.0-11
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-4
libpve-storage-perl: 5.0-3
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.9.0-1
pve-container: 2.0-6
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-1
lxcfs: 2.0.7-pve1
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
Note: I have updated my post above to reflect the problem with the Intel X540-T2BP card. It requires a special driver that is available under NDA only. Beware the low priced options on ebay!
Could we get the roadmap page to better spell out what the advantages of the new elements in 5.0 are? When "Debian Stretch" or Linux Kernel 4.10 are mentioned, I don't see how that impacts me since I don't really have the time to spend a side by side comparison between my Proxmox 4.4 setup, and where 5.0 is going.
Also, please try to avoid "this, that, the other, etc" too (avoid the etc part). I would like plenty of info to sink my teeth into, but I also know it's not productive to go extremely granular either.
I've found past major upgrades to be worthwhile, but I don't really see why I should eventually move to 5.0 based on current amount of info.
Also, please try to avoid "this, that, the other, etc" too (avoid the etc part). I would like plenty of info to sink my teeth into, but I also know it's not productive to go extremely granular either.
I've found past major upgrades to be worthwhile, but I don't really see why I should eventually move to 5.0 based on current amount of info.