Without being able to choose virtio-blk vs virtio-scsi, we need to use Full Virtualzation instead of Paravirtualization (for some OS.)

With Paravirtualization setting in Linode, OpenBSD 5.7 sees "Qumranet Virtual SCSI". But virtio-scsi (vioscsi) driver in OpenBSD isn't recommended (yet) for production use and virtio-blk (vioblk) is recommended by QEMU.

With Full-Virtualization setting in Linode, OpenBSD 5.7 writes "only" at about 100 MB/s -- which is a lot slower than Ubuntu 14.04 with Paravirtualization and virtio (500+ MB/s) on the same host.

Here's what I see with pcidump -v in OpenBSD under Linode KVM Paravirtualization:

0:3:0: Qumranet Virtio SCSI
0x0000: Vendor ID: 1af4 Product ID: 1004
0x0004: Command: 0107 Status: 0010
0x0008: Class: 01 Subclass: 00 Interface: 00 Revision: 00
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR io addr: 0x0000c000/0x0040
0x0014: BAR mem 32bit addr: 0xfebd1000/0x00001000
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR empty (00000000)
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1af4 Product ID: 0008
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
0x0040: Capability 0x11: Extended Message Signaled Interrupts (MSI-X)

Given this, it would be great if Linode configuration allowed us to choose between virtio-blk and virtio-scsi for paravirtualization.

Thanks for considering this feature.