VIRTIO Growing Up: OASIS Standard Technical Committee
Over the last few years, interest in virtio has begun compounding. FreeBSD have their bhyve implementation, there’s an MMIO bus and SCSI endpoint implementation, and I’ve been fielding more queries about various alternate implementations. While it’s taken longer than I’d hoped, the effort hasn’t waned as I feared.
So I have carved out some time this year to turn this draft into a real, consensual standard with the trappings expected by those outside the normal Linux/KVM sphere (such as an IP policy). I know I said I’d never get involved in a standard process again after the FHS, but OASIS seems like the right umbrella to cleanly and efficiently run this effort.
There are limitations and workarounds in the current draft and implementations. None are fatal, but they make a case for a flag day change for 1.0 (with backwards compatibility possible for implementations which want that). More compelling, to me, is the chance for other vendors to get involved now and have their voices heard: after the standard is finalized, they’ll just have to follow along.
I look forward to polishing what we have, and making sure we can implement even more awesome things in future.