All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: virtio-dev@lists.oasis-open.org,
	virtualization@lists.linux-foundation.org
Cc: jan.kiszka@siemens.com,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <liuw@liuw.name>
Subject: VIRTIO adoption in other hypervisors
Date: Fri, 28 Feb 2020 10:16:21 +0000	[thread overview]
Message-ID: <87mu93vwy2.fsf@linaro.org> (raw)

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 as I'm aware
the various Rust based VMMs have vary degrees of support for virtio
devices over KVM as well. CrosVM specifically is embracing virtio for
multi-process device emulation.

I believe there has been some development work for supporting VIRTIO on
Xen although it seems to have stalled according to:

  https://wiki.xenproject.org/wiki/Virtio_On_Xen

Recently at KVM Forum there was Jan's talk about Inter-VM shared memory
which proposed ivshmemv2 as a VIRTIO transport:

  https://events19.linuxfoundation.org/events/kvm-forum-2019/program/schedule/

As I understood it this would allow Xen (and other hypervisors) a simple
way to be able to carry virtio traffic between guest and end point.

So some questions:

  - Am I missing anything out in that summary?
  - How about HyperV and the OSX equivalent?
  - Do any other type-1 hypervisors support virtio?

-- 
Alex Bennée

WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: virtio-dev@lists.oasis-open.org,
	virtualization@lists.linux-foundation.org
Cc: jan.kiszka@siemens.com,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <liuw@liuw.name>
Subject: [virtio-dev] VIRTIO adoption in other hypervisors
Date: Fri, 28 Feb 2020 10:16:21 +0000	[thread overview]
Message-ID: <87mu93vwy2.fsf@linaro.org> (raw)

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 as I'm aware
the various Rust based VMMs have vary degrees of support for virtio
devices over KVM as well. CrosVM specifically is embracing virtio for
multi-process device emulation.

I believe there has been some development work for supporting VIRTIO on
Xen although it seems to have stalled according to:

  https://wiki.xenproject.org/wiki/Virtio_On_Xen

Recently at KVM Forum there was Jan's talk about Inter-VM shared memory
which proposed ivshmemv2 as a VIRTIO transport:

  https://events19.linuxfoundation.org/events/kvm-forum-2019/program/schedule/

As I understood it this would allow Xen (and other hypervisors) a simple
way to be able to carry virtio traffic between guest and end point.

So some questions:

  - Am I missing anything out in that summary?
  - How about HyperV and the OSX equivalent?
  - Do any other type-1 hypervisors support virtio?

-- 
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


             reply	other threads:[~2020-02-28 10:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28 10:16 Alex Bennée [this message]
2020-02-28 10:16 ` [virtio-dev] VIRTIO adoption in other hypervisors 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
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=87mu93vwy2.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=liuw@liuw.name \
    --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.