[DragonFlyBSD - Bug #3323] virtio (if_vtnet...) not detected on Hetzner cloud (AMD system)

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #3323 has been updated by mneumann.


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.

----------------------------------------
Bug #3323: virtio (if_vtnet...) not detected on Hetzner cloud (AMD system)
http://bugs.dragonflybsd.org/issues/3323#change-14398

* Author: mneumann
* Status: New
* Priority: Normal
* Target version: 6.4
* Start date: 2022-08-08
----------------------------------------
`pciconf -lv` lists a "Virtio network device"

!clipboard-202208082105-nspru.png!

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--------------------------------
clipboard-202208082105-nspru.png (53.9 KB)
clipboard-202208082127-sx4pg.png (57.3 KB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account