Slowly uplink

[Sessa45]

Hello,

my rootserver has an uplink of 1Gbit (recieve 100MB/s which i have tested with curl).
I created an Debian 9 VM and give unlimited speed. But i only recieve ~30MB/s (sometime up to 70).

Any idea why?

 

[wolfgang]

Hi,

you have to provide more information.
Send your VM config.
I guess you use an e1000 as vnic and they are not faster than 30Mbit.

 

[Sessa45]

Yes, you are right!

net0: e1000=72:3C:B8:84:77:CC,bridge=vmbr0

Whats the difference between the models?

 

[wolfgang]

Use virtio all other models are for legacy compatibility mode.

 

[Sessa45]

Unfortunately, the speed ist still slowly (round about 30MB)

 

[Sessa45]

Any other idea?

 

[wolfgang]

What OS (exact version) do you got in the VM?
If it is Windows which version of virtio driver do you installed.
What exact NIC type do you use?

 

[Sessa45]

Hi Wolfgang,

What OS (exact version) do you got in the VM?

root@debian:~# uname -a
Linux debian 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU

If it is Windows which version of virtio driver do you installed

Do you mean HDD?

What exact NIC type do you use?

Settings for eth1:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: off (auto)
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

driver: e1000e
version: 3.2.6-k
firmware-version: 1.8-0
expansion-rom-version:
bus-info: 0000:b3:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

 

[wolfgang]

What PVE version do you use?

because the e1000e version 3.2.6-k is quite old.

 

[Sessa45]

Im using the Virtual Environment 5.1-52.

In the shell: 4.15.18-1-pve #1 SMP PVE 4.15.18-15 (Wed, 04 Jul 201815:42:56 +0200) x86_64

 

[wolfgang]

Sorry but this can't be correct.

kernel 4.15.18-1 is the current kernel and contains the e1000e in version 3.4.1.1-NAPI.
I think the driver you send me is that from the VM?

 

[Sessa45]

I'm sorry for this, my mistake. Here the correctly infos:

root@LXC1:~# pveversion -v
proxmox-ve: 5.1-43 (running kernel: 4.15.17-1-pve)
pve-manager: 5.1-52 (running version: 5.1-52/ba597a64)
pve-kernel-4.15: 5.1-4
pve-kernel-4.15.17-1-pve: 4.15.17-8
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-31
libpve-guest-common-perl: 2.0-15
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-21
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-17
pve-cluster: 5.0-27
pve-container: 2.0-22
pve-docs: 5.1-17
pve-firewall: 3.0-8
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-3
qemu-server: 5.0-25
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3

 

[Sessa45]

Any further idea?

 

[wolfgang]

Please update to current version.

 

[Sessa45]

I have updated to proxmox-ve: 5.2-2 (running kernel: 4.15.17-2-pve) but the driver: e1000e and version: 3.2.6-k is still the old.

 

[wolfgang]

Have you reboot the node?

 

[Sessa45]

Yes, i have rebooted the node.

root@root:~# ethtool -i eth1
driver: e1000e
version: 3.2.6-k
firmware-version: 1.8-0
expansion-rom-version:
bus-info: 0000:b3:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
root@root:~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.17-2-pve)
pve-manager: 5.2-5 (running version: 5.2-5/eb24855a)
pve-kernel-4.15: 5.2-2
pve-kernel-4.15.17-2-pve: 4.15.17-10
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-35
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-1
proxmox-widget-toolkit: 1.0-19
pve-cluster: 5.0-28
pve-container: 2.0-24
pve-docs: 5.2-4
pve-firewall: 3.0-13
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-29
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3

 

[wolfgang]

My fault the version 3.4.1.1-NAPI comes white the next kernel (4.15.18-1-pve).
Which repository do you use because of the 4.15.18-1 is the last one?

 

[Sessa45]

Im using the no sub repo and the standard Debian repo´s.

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

 

[Sessa45]

Any idea in this case?