Re: bounty for virtio 1.0 (now with instructions!)
On Tue, Nov 03, 2020 at 10:20:27PM +, co...@sdf.org wrote: > The QEMU people mentioned that even if "legacy virtio" IDs are used, > there's a bit to show that it's compatible with newer virtio. > Things that claim old virtio probably do both old & new. Yeah, but last I tried there were some environments where really only 0.9 was supported - I've been told this has changed by now (or will soonish), so indeeded only implementing 1.x might be an option - but we should double check. Martin
Re: bounty for virtio 1.0 (now with instructions!)
On 03.11.2020 23:20, co...@sdf.org wrote: > On Tue, Nov 03, 2020 at 10:42:27PM +0100, Martin Husemann wrote: >> On Tue, Nov 03, 2020 at 10:23:30PM +0100, Reinoud Zandijk wrote: >>> To be clear, do we want to (keep) supporting legacy devices? Its not >>> required >>> in 1.0 and could clean up the code a lot! >> >> Yes, we need that still, as not all hosts offer the newer ones. > > The QEMU people mentioned that even if "legacy virtio" IDs are used, > there's a bit to show that it's compatible with newer virtio. > Things that claim old virtio probably do both old & new. > "Transitional virtio" supports both, 1.0 and 0.9. I had a draft work with the upgrade of virtio, but incomplete.. signature.asc Description: OpenPGP digital signature
Re: bounty for virtio 1.0 (now with instructions!)
On Tue, Nov 03, 2020 at 10:42:27PM +0100, Martin Husemann wrote: > On Tue, Nov 03, 2020 at 10:23:30PM +0100, Reinoud Zandijk wrote: > > To be clear, do we want to (keep) supporting legacy devices? Its not > > required > > in 1.0 and could clean up the code a lot! > > Yes, we need that still, as not all hosts offer the newer ones. The QEMU people mentioned that even if "legacy virtio" IDs are used, there's a bit to show that it's compatible with newer virtio. Things that claim old virtio probably do both old & new.
Re: bounty for virtio 1.0 (now with instructions!)
On Tue, Nov 03, 2020 at 10:23:30PM +0100, Reinoud Zandijk wrote: > To be clear, do we want to (keep) supporting legacy devices? Its not required > in 1.0 and could clean up the code a lot! Yes, we need that still, as not all hosts offer the newer ones. Martin
Re: bounty for virtio 1.0 (now with instructions!)
On Mon, Nov 02, 2020 at 07:54:02PM +, co...@sdf.org wrote: > On Tue, Sep 01, 2020 at 01:28:44PM +, co...@sdf.org wrote: > > - 1af4:1044 VirtIO 1.0 random number generator > > - 1af4:1042 VirtIO 1.0 block device > > - 1af4:1041 VirtIO 1.0 network device > > > > Offer valid until 1 January 2021. To be clear, do we want to (keep) supporting legacy devices? Its not required in 1.0 and could clean up the code a lot! Though bhyve states it supports 0.9+additions i.e. `legacy' but extended with `trim' support etc. Supporting only 1.0 might thus be unwise. Any thoughts? Reinoud
