NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/55210: virtio lacks support for non-transitional devices acc. to VIRTIO Spec. 1.1



>Number:         55210
>Category:       kern
>Synopsis:       virtio lacks support for non-transitional devices acc. to VIRTIO Spec. 1.1
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 26 16:45:00 +0000 2020
>Originator:     Felix Deichmann
>Release:        NetBSD 9.0 (and -current)
>Organization:
NetBSD
>Environment:
NetBSD flex2-vm1.home.flxd.de 9.0 NetBSD 9.0 (GENERIC) #0: Fri Feb 14 00:06:28 UTC 2020  mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>Description:
In 9.0 (and also -current as it seems), our virtio driver seems to lack support for "non-transitional devices" according to Virtual I/O Device (VIRTIO) Version 1.1:

https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.html

The new devices seem to have a PCI Device ID in the range 0x1040 to 0x107f.
We only support "transitional devices" from 0x1000 to 0x103f.

In latest VirtualBox 6.1.6 with enabled virtio-scsi for example, the controller is not matched by our vioscsi driver:
vendor 1af4 product 1048 (SCSI mass storage, revision 0x01) at pci0 dev 15 function 0 not configured

vioif matches however, probably because VirtualBox still uses a "transitional" PCI ID for it.
>How-To-Repeat:
Boot NetBSD in VirtualBox 6.1.6 with enabled virtio-scsi controller.
>Fix:
Just adding/matching the new PCI IDs to be used by our existing drivers could be enough (hopefully)...



Home | Main Index | Thread Index | Old Index