From: Jamie Lokier <jamie@shareable.org>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] virtio-serial: A guest <-> host interface for simple communication
Date: Wed, 24 Jun 2009 17:40:49 +0100 [thread overview]
Message-ID: <20090624164049.GE14121@shareable.org> (raw)
In-Reply-To: <1245760953-32139-1-git-send-email-amit.shah@redhat.com>
Amit Shah wrote:
> A few sample uses for a vmchannel are to share the host and guest
> clipboards (to allow copy/paste between a host and a guest), to
> lock the screen of the guest session when the vnc viewer is closed,
> to find out which applications are installed on a guest OS even when
> the guest is powered down (using virt-inspector) and so on.
Those all look like useful features.
Can you run an application to provide those features on a guest which
_doesn't_ have a vmchannel/virtio-serial support in the kernel?
Or will it be restricted only to guests which have QEMU-specific
support in their kernel?
-- Jamie
next prev parent reply other threads:[~2009-06-24 16:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1245760953-32139-1-git-send-email-amit.shah@redhat.com>
2009-06-23 12:42 ` [PATCH] virtio_serial: A char device for simple guest <-> host communication Amit Shah
[not found] ` <1245760953-32139-2-git-send-email-amit.shah@redhat.com>
2009-06-23 12:42 ` [PATCH] virtio-serial: virtio device for simple host <-> guest communication Amit Shah
2009-06-23 15:15 ` [Qemu-devel] [PATCH] virtio_serial: A char device for simple guest <-> host communication Blue Swirl
[not found] ` <1245760953-32139-3-git-send-email-amit.shah@redhat.com>
2009-06-23 15:19 ` [Qemu-devel] [PATCH] virtio-serial: virtio device for simple host <-> guest communication Blue Swirl
2009-06-23 12:55 ` [Qemu-devel] virtio-serial: A guest <-> host interface for simple communication Paul Brook
[not found] ` <200906231355.53557.paul@codesourcery.com>
2009-06-23 13:00 ` Amit Shah
[not found] ` <20090623130023.GA32110@amit-x200.redhat.com>
2009-06-23 13:09 ` Paul Brook
2009-06-23 13:58 ` Christian Bornträger
[not found] ` <200906231558.33794.borntraeger@de.ibm.com>
2009-06-23 14:16 ` Paul Brook
[not found] ` <200906231516.15470.paul@codesourcery.com>
2009-06-23 14:40 ` Christian Bornträger
2009-06-23 14:59 ` Daniel P. Berrange
2009-06-24 4:15 ` Rusty Russell
[not found] ` <200906241345.02051.rusty@rustcorp.com.au>
2009-06-24 12:39 ` Amit Shah
[not found] ` <20090624123937.GA14630@amit-x200.redhat.com>
2009-06-25 11:33 ` Rusty Russell
[not found] ` <200906252103.02892.rusty@rustcorp.com.au>
2009-06-25 20:49 ` Amit Shah
2009-06-24 16:40 ` Jamie Lokier [this message]
2009-06-24 17:10 ` [Qemu-devel] " Amit Shah
[not found] ` <20090624170632.GA24285@amit-x200.redhat.com>
2009-06-24 17:50 ` Jamie Lokier
[not found] ` <20090624175002.GJ14121@shareable.org>
2009-06-24 18:01 ` Amit Shah
[not found] ` <20090624180114.GA24906@amit-x200.redhat.com>
2009-06-24 19:20 ` Jamie Lokier
[not found] ` <20090624192027.GT14121@shareable.org>
2009-06-25 4:41 ` Amit Shah
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=20090624164049.GE14121@shareable.org \
--to=jamie@shareable.org \
--cc=amit.shah@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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 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).