Project

General

Profile

Actions

Bug #3323

open

virtio (if_vtnet...) not detected on Hetzner cloud (AMD system)

Added by mneumann about 2 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
08/08/2022
Due date:
% Done:

0%

Estimated time:

Description

`pciconf -lv` lists a "Virtio network device"

But it does not show up under `ifconfig`. Also the virtio SCSI harddisk is not detected.

Just curious if I am doing anything wrong.


Files

Actions #1

Updated by mneumann about 2 months ago

`pciconf -lv` on the "Intel" system looks like.

The difference here is that on the Intel system, virtio has `rev=0`, while on the AMD system it has `rev=1`. Is this a different version of VirtIO?

Actions #2

Updated by daftaupe about 1 month ago

Could it be linked to the fact that one can choose to use either i440FX or Q35 as the chipset for KVM ?
I had some issues with the latter and had to use i440FX to have working (reckognized) vtnet at least (also AMD-based)

Looks like FreeBSD had to work on some drivers to make Q35-based vms to work properly too : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922

Actions #3

Updated by mneumann about 1 month ago

daftaupe wrote in #note-2:

Could it be linked to the fact that one can choose to use either i440FX or Q35 as the chipset for KVM ?
I had some issues with the latter and had to use i440FX to have working (reckognized) vtnet at least (also AMD-based)

Looks like FreeBSD had to work on some drivers to make Q35-based vms to work properly too : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922

See "comment 8" https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922#c8:

The device IDs you are seeing are for the VirtIO V1 spec. FreeBSD only supports the pre-V1 (aka legacy) VirtIO spec. I suppose there was a QEMU change to use V1 with Q35 chipset.

So the real problem is that we do not support the newer VirtIO specification.

Actions

Also available in: Atom PDF