[virtio-dev] Re: VIRTIO adoption in other hypervisors

2020-02-28 Thread Jan Kiszka
On 28.02.20 17:47, Alex Bennée wrote: Jan Kiszka writes: On 28.02.20 11:30, Jan Kiszka wrote: On 28.02.20 11:16, Alex Bennée wrote: Hi, I believe there has been some development work for supporting VIRTIO on Xen although it seems to have stalled according to:

[virtio-dev] Re: VIRTIO adoption in other hypervisors

2020-02-28 Thread Alex Bennée
Jan Kiszka writes: > On 28.02.20 11:30, Jan Kiszka wrote: >> On 28.02.20 11:16, Alex Bennée wrote: >>> Hi, >>> >>> I believe there has been some development work for supporting VIRTIO on >>> Xen although it seems to have stalled according to: >>> >>>

Re: [virtio-dev] VIRTIO adoption in other hypervisors

2020-02-28 Thread Paolo Bonzini
On 28/02/20 12:18, Alex Bennée wrote: >> OS X Hypervisor.framework just uses QEMU, so it can use virtio devices >> too. VirtualBox also supports virtio devices. > I guess these don't do any sort of vhost support so all virtio devices > are handled directly in QEMU? OS X can use vhost-user.

Re: [virtio-dev] VIRTIO adoption in other hypervisors

2020-02-28 Thread Alex Bennée
Paolo Bonzini writes: > On 28/02/20 11:16, Alex Bennée wrote: >> - How about HyperV and the OSX equivalent? > > OS X Hypervisor.framework just uses QEMU, so it can use virtio devices > too. VirtualBox also supports virtio devices. I guess these don't do any sort of vhost support so all

Re: [virtio-dev] Re: [PATCH v5] virtio-snd: add virtio sound device specification

2020-02-28 Thread Gerd Hoffmann
On Thu, Feb 27, 2020 at 03:08:59PM +0100, Anton Yakovlev wrote: > Hello all, > > We have completed the implementation of the PoC specification v5. Below are > our comments on what might or should be improved in the specification. > > Initialization: > > 1. I think we should add the direction of

Re: [virtio-dev] VIRTIO adoption in other hypervisors

2020-02-28 Thread Stefan Hajnoczi
On Fri, Feb 28, 2020 at 10:16:21AM +, Alex Bennée wrote: > I'm currently trying to get my head around virtio and was wondering how > widespread adoption of virtio is amongst the various hypervisors and > emulators out there. > > Obviously I'm familiar with QEMU both via KVM and even when just

Re: [virtio-dev] VIRTIO adoption in other hypervisors

2020-02-28 Thread Paolo Bonzini
On 28/02/20 11:16, Alex Bennée wrote: > - How about HyperV and the OSX equivalent? OS X Hypervisor.framework just uses QEMU, so it can use virtio devices too. VirtualBox also supports virtio devices. Paolo - To unsubscribe,

[virtio-dev] Re: VIRTIO adoption in other hypervisors

2020-02-28 Thread Jan Kiszka
On 28.02.20 11:30, Jan Kiszka wrote: On 28.02.20 11:16, Alex Bennée wrote: Hi, I'm currently trying to get my head around virtio and was wondering how widespread adoption of virtio is amongst the various hypervisors and emulators out there. Obviously I'm familiar with QEMU both via KVM and

Re: [virtio-dev] [RFC] Upstreaming virtio-wayland (or an alternative)

2020-02-28 Thread Boris Brezillon
On Fri, 28 Feb 2020 19:11:40 +0900 David Stevens wrote: > > > > Yes, sure, we need to exactly specify the different kinds of file > > > > handles / resources. I think it makes sense to have a virtio feature > > > > flag for each of them, so guest+host can easily negotiate what they are > > > >

Re: [virtio-dev] [RFC] Upstreaming virtio-wayland (or an alternative)

2020-02-28 Thread Gerd Hoffmann
On Fri, Feb 28, 2020 at 07:11:40PM +0900, David Stevens wrote: > > But there also is "unix socket", or maybe a somewhat broader "stream", > > which would be another feature flag I guess because virtio-ipc would > > just tunnel the stream without the help from other devices. > > Can you elaborate

[virtio-dev] Re: VIRTIO adoption in other hypervisors

2020-02-28 Thread Jan Kiszka
On 28.02.20 11:16, Alex Bennée wrote: Hi, I'm currently trying to get my head around virtio and was wondering how widespread adoption of virtio is amongst the various hypervisors and emulators out there. Obviously I'm familiar with QEMU both via KVM and even when just doing plain emulation

[virtio-dev] VIRTIO adoption in other hypervisors

2020-02-28 Thread Alex Bennée
Hi, I'm currently trying to get my head around virtio and was wondering how widespread adoption of virtio is amongst the various hypervisors and emulators out there. Obviously I'm familiar with QEMU both via KVM and even when just doing plain emulation (although with some restrictions). As far

Re: [virtio-dev] [RFC] Upstreaming virtio-wayland (or an alternative)

2020-02-28 Thread David Stevens
> > > Yes, sure, we need to exactly specify the different kinds of file > > > handles / resources. I think it makes sense to have a virtio feature > > > flag for each of them, so guest+host can easily negotiate what they are > > > able to handle and what not. > > > > I was expecting that to be a

Re: [virtio-dev] [RFC] Upstreaming virtio-wayland (or an alternative)

2020-02-28 Thread Gerd Hoffmann
Hi, > > Yes, sure, we need to exactly specify the different kinds of file > > handles / resources. I think it makes sense to have a virtio feature > > flag for each of them, so guest+host can easily negotiate what they are > > able to handle and what not. > > I was expecting that to be a

Re: [virtio-dev] [RFC] Upstreaming virtio-wayland (or an alternative)

2020-02-28 Thread Boris Brezillon
Hi Gerd, On Thu, 27 Feb 2020 15:43:22 +0100 Gerd Hoffmann wrote: > Hi, > > > > > Can you provide more detail about the envisioned scope of this > > > > framework? > > > > > > The scope is "generic message+FD passing" interface, which is pretty > > > much what virtio-wl provides. > > > >