All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jamie Lokier <jamie@shareable.org>
Cc: Avi Kivity <avi@redhat.com>, Alexander Graf <agraf@suse.de>,
	linux-fbdev-devel@lists.sourceforge.net, qemu-devel@nongnu.org,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [PATCH] Add VirtIO Frame Buffer Support
Date: Thu, 05 Nov 2009 21:05:11 -0600	[thread overview]
Message-ID: <4AF39267.9060104@codemonkey.ws> (raw)
In-Reply-To: <20091106023915.GO21630@shareable.org>

Jamie Lokier wrote:
> Avi Kivity wrote:
>   
>> On 11/03/2009 12:09 AM, Alexander Graf wrote:
>>     
>>> When we want to create a full VirtIO based machine, we're still missing
>>> graphics output. Fortunately, Linux provides us with most of the frameworks
>>> to render text and everything, we only need to implement a transport.
>>>
>>> So this is a frame buffer backend written for VirtIO. Using this and my
>>> patch to qemu, you can use paravirtualized graphics.
>>>       
>> What does this do that cirrus and/or vmware-vga don't?
>>     
>
> *This* virtio-fb doesn't, but one feature I think a lot of users
> (including me) would like is:
>
>    Option to resize the guest desktop when the host desktop / host
>    window / VNC client resizes.
>
>    Tell the guest to provide multiple desktops when the host has
>    multiple desktops, so things like twin monitors work nicely with
>    guests.
>
>    Relay EDID/Xrandr information and updates from host to guest, and
>    generally handle hotplugging host monitors nicely.
>
> Are there any real hardware standards worth emulating which do that?
>   

vmware-vga.

If you have a little tool in a guest that uses the X extension that 
vmware vga implements, it actually works in qemu too.

Regards,

Anthony Liguoru

WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org, linux-fbdev-devel@lists.sourceforge.net,
	Avi Kivity <avi@redhat.com>,
	kvm@vger.kernel.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] Re: [PATCH] Add VirtIO Frame Buffer Support
Date: Thu, 05 Nov 2009 21:05:11 -0600	[thread overview]
Message-ID: <4AF39267.9060104@codemonkey.ws> (raw)
In-Reply-To: <20091106023915.GO21630@shareable.org>

Jamie Lokier wrote:
> Avi Kivity wrote:
>   
>> On 11/03/2009 12:09 AM, Alexander Graf wrote:
>>     
>>> When we want to create a full VirtIO based machine, we're still missing
>>> graphics output. Fortunately, Linux provides us with most of the frameworks
>>> to render text and everything, we only need to implement a transport.
>>>
>>> So this is a frame buffer backend written for VirtIO. Using this and my
>>> patch to qemu, you can use paravirtualized graphics.
>>>       
>> What does this do that cirrus and/or vmware-vga don't?
>>     
>
> *This* virtio-fb doesn't, but one feature I think a lot of users
> (including me) would like is:
>
>    Option to resize the guest desktop when the host desktop / host
>    window / VNC client resizes.
>
>    Tell the guest to provide multiple desktops when the host has
>    multiple desktops, so things like twin monitors work nicely with
>    guests.
>
>    Relay EDID/Xrandr information and updates from host to guest, and
>    generally handle hotplugging host monitors nicely.
>
> Are there any real hardware standards worth emulating which do that?
>   

vmware-vga.

If you have a little tool in a guest that uses the X extension that 
vmware vga implements, it actually works in qemu too.

Regards,

Anthony Liguoru

  reply	other threads:[~2009-11-06  3:05 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 22:09 [PATCH] Add VirtIO Frame Buffer Support Alexander Graf
2009-11-02 22:09 ` [Qemu-devel] " Alexander Graf
2009-11-02 22:32 ` Ondrej Zajicek
2009-11-02 22:42   ` Alexander Graf
2009-11-02 23:24     ` [Linux-fbdev-devel] " Alexander Graf
2009-11-02 23:24       ` [Qemu-devel] " Alexander Graf
2009-11-02 23:57       ` Ondrej Zajicek
2009-11-02 23:57         ` [Qemu-devel] Re: [Linux-fbdev-devel] " Ondrej Zajicek
2009-11-02 23:59         ` Alexander Graf
2009-11-02 23:59           ` [Qemu-devel] " Alexander Graf
2009-11-02 23:51     ` Ondrej Zajicek
2009-11-02 23:53       ` Alexander Graf
2009-11-02 23:58         ` Ondrej Zajicek
2009-11-03  6:21 ` Avi Kivity
2009-11-03  6:21   ` [Qemu-devel] " Avi Kivity
2009-11-03  6:22   ` Alexander Graf
2009-11-03  6:22     ` [Qemu-devel] " Alexander Graf
2009-11-03  6:24     ` Avi Kivity
2009-11-03  6:24       ` [Qemu-devel] " Avi Kivity
2009-11-03  6:27       ` Alexander Graf
2009-11-03  6:27         ` [Qemu-devel] " Alexander Graf
2009-11-03  6:34         ` Avi Kivity
2009-11-03  6:34           ` [Qemu-devel] " Avi Kivity
2009-11-03  6:39           ` Alexander Graf
2009-11-03  6:39             ` [Qemu-devel] " Alexander Graf
2009-11-03  7:43             ` Avi Kivity
2009-11-03  7:43               ` [Qemu-devel] " Avi Kivity
2009-11-03  7:50               ` Alexander Graf
2009-11-03  7:50                 ` [Qemu-devel] " Alexander Graf
2009-11-03  8:20                 ` Avi Kivity
2009-11-03  8:20                   ` [Qemu-devel] " Avi Kivity
2009-11-03  8:26                   ` Alexander Graf
2009-11-03  8:26                     ` [Qemu-devel] " Alexander Graf
2009-11-03  8:53                     ` Avi Kivity
2009-11-03  8:53                       ` [Qemu-devel] " Avi Kivity
2009-11-03 15:14                       ` Anthony Liguori
2009-11-03 15:14                         ` [Qemu-devel] " Anthony Liguori
2009-11-03 15:57                         ` Avi Kivity
2009-11-03 15:57                           ` [Qemu-devel] " Avi Kivity
2009-11-03 11:25             ` Vincent Hanquez
2009-11-03 11:25               ` Vincent Hanquez
2009-11-03  9:38               ` Avi Kivity
2009-11-03  9:38                 ` Avi Kivity
2009-11-03 15:29                 ` Ondrej Zajicek
2009-11-03 15:29                   ` [Linux-fbdev-devel] " Ondrej Zajicek
2009-11-03 16:05                   ` Avi Kivity
2009-11-03 16:05                     ` Avi Kivity
2009-11-03 16:53                     ` Ondrej Zajicek
2009-11-03 16:53                       ` Ondrej Zajicek
2009-11-03 17:33                     ` [Linux-fbdev-devel] " Paolo Bonzini
2009-11-03 17:33                       ` [Linux-fbdev-devel] [Qemu-devel] " Paolo Bonzini
2009-11-03 17:33                       ` [Linux-fbdev-devel] " Paolo Bonzini
2009-11-04 16:09                 ` [Qemu-devel] " Vincent Hanquez
2009-11-04 16:35                   ` Anthony Liguori
2009-11-04 16:35                     ` Anthony Liguori
2009-11-05  9:04                     ` Avi Kivity
2009-11-08  4:43                 ` Thomas Fjellstrom
2009-11-06  2:39   ` Jamie Lokier
2009-11-06  2:39     ` Jamie Lokier
2009-11-06  3:05     ` Anthony Liguori [this message]
2009-11-06  3:05       ` Anthony Liguori
2009-11-05 11:36 ` Michael S. Tsirkin
2009-11-05 11:36 ` Michael S. Tsirkin
2009-11-05 11:36   ` [Qemu-devel] " Michael S. Tsirkin

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=4AF39267.9060104@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=jamie@shareable.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.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.