@Not_Oles said:
* retiring OpenBSD on this server, for the moment, to free up more space
that's something I am planning to do soon.
That's done now - resizing a NetBSD filesystem is always a it fiddly, as you first have to make sure to remove to filesystem journal, then resize the filesystem, and finally re-create the journal again (if you are using wapbl).
I have installed qemu (with nvmm) to run a test NetBSD VM to see if I can reproduce the virtio issue I am seeing on the linveo VPS.
I looks like it could be a memory ordering issue in the virtio communication between the guest and the host, as adding an additional mfence in the driver code seems to fix it.
Comments
That's done now - resizing a NetBSD filesystem is always a it fiddly, as you first have to make sure to remove to filesystem journal, then resize the filesystem, and finally re-create the journal again (if you are using wapbl).
(there is still Debian installed using the other half of the disk)
Thanks @cmeerw!
Much appreciated! 
Thanks to Hosteroid for our nice community server! Which is now dual booting Debian and NetBSD. . . .
Anybody have a project and want to jump on? Please read "How To Apply" in the OP, and then come and join us!
I hope everyone gets the servers they want!
I have installed qemu (with nvmm) to run a test NetBSD VM to see if I can reproduce the virtio issue I am seeing on the linveo VPS.
I looks like it could be a memory ordering issue in the virtio communication between the guest and the host, as adding an additional mfence in the driver code seems to fix it.