From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Wei Liu <liuw@liuw.name>,
jan.kiszka@siemens.com,
Stefano Stabellini <sstabellini@kernel.org>,
virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org
Subject: Re: [virtio-dev] VIRTIO adoption in other hypervisors
Date: Fri, 28 Feb 2020 11:18:38 +0000 [thread overview]
Message-ID: <87k147vu29.fsf@linaro.org> (raw)
In-Reply-To: <fca8366e-662f-af2f-382c-0216d9df63f8@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> 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 virtio devices
are handled directly in QEMU?
--
Alex Bennée
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: virtualization@lists.linux-foundation.org,
jan.kiszka@siemens.com,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <liuw@liuw.name>,
virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] VIRTIO adoption in other hypervisors
Date: Fri, 28 Feb 2020 11:18:38 +0000 [thread overview]
Message-ID: <87k147vu29.fsf@linaro.org> (raw)
In-Reply-To: <fca8366e-662f-af2f-382c-0216d9df63f8@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> 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 virtio devices
are handled directly in QEMU?
--
Alex Bennée
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2020-02-28 11:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 10:16 VIRTIO adoption in other hypervisors Alex Bennée
2020-02-28 10:16 ` [virtio-dev] " Alex Bennée
2020-02-28 10:30 ` Jan Kiszka
2020-02-28 10:30 ` [virtio-dev] " Jan Kiszka
2020-02-28 10:36 ` Jan Kiszka
2020-02-28 10:36 ` [virtio-dev] " Jan Kiszka
2020-02-28 16:47 ` Alex Bennée
2020-02-28 16:47 ` [virtio-dev] " Alex Bennée
2020-02-28 17:08 ` Jürgen Groß
2020-02-28 17:16 ` Jan Kiszka
2020-02-28 17:16 ` [virtio-dev] " Jan Kiszka
2020-02-29 1:29 ` Stefano Stabellini
2020-02-28 10:58 ` Paolo Bonzini
2020-02-28 10:58 ` [virtio-dev] " Paolo Bonzini
2020-02-28 11:18 ` Alex Bennée [this message]
2020-02-28 11:18 ` Alex Bennée
2020-02-28 11:21 ` Paolo Bonzini
2020-02-28 11:21 ` [virtio-dev] " Paolo Bonzini
2020-02-28 11:09 ` Stefan Hajnoczi
2020-02-28 11:09 ` [virtio-dev] " Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k147vu29.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=jan.kiszka@siemens.com \
--cc=liuw@liuw.name \
--cc=pbonzini@redhat.com \
--cc=sstabellini@kernel.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.