linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefanha@gmail.com (Stefan Hajnoczi)
To: linux-arm-kernel@lists.infradead.org
Subject: [Qemu-devel] [RFC] Virtio-desktop: Virtio-based virtual desktop
Date: Thu, 24 Jan 2013 10:25:31 +0100	[thread overview]
Message-ID: <20130124092531.GD18072@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CALrVBktEQM5D-L+60RTzdRgo7jLZ671KxWMUFGnQwQ1bzgjO2A@mail.gmail.com>

On Thu, Jan 24, 2013 at 11:40:24AM +0530, Anup Patel wrote:
> IMHO, If we have something like Virtio-desktop specification then all
> possible guest OSes can have support for it and different hypervisor can
> emulate it without worrying about guest support.

At this point x86 virtualization is mature and working with a mix of
emulated x86 architecture pieces and virtio devices for
performance-critical or open-ended functionality that we want to be able
to extend.

ARM is getting KVM and virtio-mmio support.  It will be in a similar
position soon.

Virtio guest drivers have not been implemented widely.  The Linux and
Windows efforts are driven by the folks who were behind virtio from the
start, but Solaris, FreeBSD, and others didn't really jump on the virtio
bandwagon.

Given this landscape, what is the advantage of doing a virtio-desktop?
It will still need to fall back on ARM or x86 which is already being
virtualized and emulated.

Depending on how you see it we either have virtio-desktop already or,
if not, I think the experience with virtio adoption suggests other
hypervisors and guest OSes will not trip over themselves to implement
virtio-desktop.

What's the advantage over virtualizating an existing ARM or x86 platform
and using virtio devices where appropriate?

Stefan

       reply	other threads:[~2013-01-24  9:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALrVBktEQM5D-L+60RTzdRgo7jLZ671KxWMUFGnQwQ1bzgjO2A@mail.gmail.com>
2013-01-24  9:25 ` Stefan Hajnoczi [this message]
2013-01-24 14:38   ` [kvmarm] [Qemu-devel] [RFC] Virtio-desktop: Virtio-based virtual desktop Alexander Graf
2013-01-24 14:42     ` Peter Maydell
2013-01-24 14:52       ` Alexander Graf
     [not found]   ` <CALrVBksLFyq5Vb+oLtASrdgU6x=GxXCEFy_ZWmvSosDOU6CsiQ@mail.gmail.com>
2013-01-25  7:46     ` Stefan Hajnoczi
2013-01-25 19:04 ` Blue Swirl
2013-01-25 19:31   ` [kvmarm] " Alexander Graf
2013-01-27  8:20     ` [Qemu-devel] [kvmarm] " Gleb Natapov
2013-01-27 10:12       ` Blue Swirl
2013-01-27 13:53         ` Gleb Natapov
2013-01-27 14:07 ` [Qemu-devel] " Anthony Liguori
2013-01-27 16:23   ` [kvmarm] " Alexander Graf

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=20130124092531.GD18072@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).