From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-6818-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id AD307985ED0 for ; Fri, 28 Feb 2020 11:18:41 +0000 (UTC) References: <87mu93vwy2.fsf@linaro.org> From: Alex =?utf-8?Q?Benn=C3=A9e?= In-reply-to: Date: Fri, 28 Feb 2020 11:18:38 +0000 Message-ID: <87k147vu29.fsf@linaro.org> MIME-Version: 1.0 Subject: Re: [virtio-dev] VIRTIO adoption in other hypervisors Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: Paolo Bonzini Cc: virtualization@lists.linux-foundation.org, jan.kiszka@siemens.com, Stefano Stabellini , Wei Liu , virtio-dev@lists.oasis-open.org List-ID: Paolo Bonzini writes: > On 28/02/20 11:16, Alex Benn=C3=A9e 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 virtio devices are handled directly in QEMU? --=20 Alex Benn=C3=A9e --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org