Virtio network card, no info (maybe not fully supported?)

virtio
proxmox
kvm

#1

Hi there!

I install VyOS on my home server (Proxmox) and set to virtio network card (best performance) the VM vorking well, but now i check interface status, and get this:

    vyos@vyos:~$ show interfaces ethernet eth0 physical
Settings for eth0:
        Supported ports: [ ]
        Supported link modes:   Not reported
        Supported pause frame use: No
        Supports auto-negotiation: No
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: Other
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Link detected: yes
driver: virtio_net
version: 1.0.0
firmware-version:
bus-info: 0000:00:12.0
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

#2

Looks good for me,
what you see as wrong?


#3

Now i set to vmxnet3. you see the differences:

Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   1000baseT/Full
                                10000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: No
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        MDI-X: Unknown
        Supports Wake-on: uag
        Wake-on: d
        Link detected: yes
driver: vmxnet3
version: 1.4.a.0-k-NAPI
firmware-version:
bus-info: 0000:00:12.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

#4

i think is how data presented by driver to ethtool
What version of VyOS by the way?


#5
Version:          VyOS 1.2.0-rolling+201804110337
Built by:         autobuild@vyos.net
Built on:         Wed 11 Apr 2018 03:37 UTC
Build ID:         a7cf1949-4659-43e8-82ca-1db806310d4b

Architecture:     x86_64
Boot via:         installed image
System type:      KVM guest

Hardware vendor:  QEMU
Hardware model:   Standard PC (i440FX + PIIX, 1996)
Hardware S/N:
Hardware UUID:    5EC01258-023E-4D67-9549-5B942B664D26

Copyright:        VyOS maintainers and contributors

#6

@dmbaturin your thoughts on that ?


#7

I believe many of those options are genuinely not supported by vmx3 (or other paravirtual NICs).

However, if you’ve got a system where the NIC information for vmx3 is more complete, please share the output.


#8

Iteresting but the vmxnet3 (on proxmox) use much more CPU like Virtio.

Conf: i3 5005U, i add to VyOS VM 1 Core and 1 Gb memory

Speedtest (160/60 Mbit) Virtio: about 25-30%

Speedtest (160/60 Mbit) vmxnet3 : 100%(!!)


#9

He already done that


#10

I switch back to virtio… Yes it seems to be not fully supported, but with vmxnet3, the CPU is constant 100% usage, if i download something (about 150 Mbit)

I hope the virtio will be fully supported in the future.


#11

are you on vSphere ?
if so which version of ESXi?


#12

No, i use Proxmox (KVM),

i tried to vmxnet3, but in KVM the resource usage is horrible. Now i set again to Virtio Netvork card. Unfortunatelly i dont see the card info (i think it is a driver bug) but the resource usage is much better!


#13

ah ok, i was wondering why you use vmxnet3
so i think it’s just how it shows on virtio, but it works just fine (not got any reports about issues)


#14

Yes, i not see any problem on daily work.

The only thing that i affected, if i try to set the interface (like add IP, etc… ) i get a error if i try to commit. It say that can not set to speed and duplex mode correctly…But after that, i able to save it… I think the reason that Vyos can not handle correctly to Virtio capabilities and it cause some bugs. errors.


#15

i think you need to submit bug report on that at phabricator.vyos.net
definitely incorrect behaviour here