All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: PATCH: 0/10: Merge xenfb & xenconsoled into qemu-dm
Date: Thu, 16 Aug 2007 16:34:15 +0100	[thread overview]
Message-ID: <20070816153415.GH16779@redhat.com> (raw)
In-Reply-To: <C2EA077C.14489%keir@xensource.com>

On Thu, Aug 16, 2007 at 01:54:04PM +0100, Keir Fraser wrote:
> On 16/8/07 13:49, "Daniel P. Berrange" <berrange@redhat.com> wrote:
> 
> >> Are these patches intended to be applied now, or are they RFC?
> > 
> > They could be applied now, but was expecting people might have some feedback
> > /recommendations for changes - Christian normally has lots of good comments
> > for QEMU related stuff. So if I have to do another revision of the patches
> > I'm fine with it.
> 
> My own feeling is that the xenfb merge is very sensible, but I don't see
> much of a win from merging xenconsoled, and the downside is that you then
> need a qemu-dm instance for every PV guest. I think that requiring qemu-dm
> for more 'featureful' PV guests -- framebuffer, USB, etc -- is well and
> good, but someone who is running more minimal domU configurations --
> console, net, block -- isn't going to want or welcome the rather unnecessary
> per-domU overhead of qemu-dm.

Yep, I can see that would be useful for some folks working in constrained
environments. Of course they probably don't want the XenD overhead either,
but that's a can of worms I won't get into right now ;-)

Thinking about this, I think I can easily re-work the last two patches so
that xenconsoled will continue to process the guest consoles, if-and-only-if
the guest doesn't have a QEMU instance already doing it. That would give us
choice between both deployment scenarios per-guest.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-08-16 15:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 20:00 PATCH: 0/10: Merge xenfb & xenconsoled into qemu-dm Daniel P. Berrange
2007-08-15 20:02 ` PATCH: 1/10: Add a QEMU machine type for fullvirt guests Daniel P. Berrange
2007-08-15 20:04 ` PATCH: 2/10: Add a QEMU machine type for paravirt guests Daniel P. Berrange
2007-08-15 20:05 ` PATCH: 3/10: Remove standalone xenfb code Daniel P. Berrange
2007-08-15 20:06 ` PATCH: 4/10: Refactor xenfb event handlers Daniel P. Berrange
2007-08-15 20:07 ` PATCH: 5/10: Refactor QEMU console integration Daniel P. Berrange
2007-08-15 20:08 ` PATCH: 6/10: Merge private & public xenfb structs Daniel P. Berrange
2007-08-15 20:09 ` PATCH: 7/10: Async negotiation with xenfb frontend Daniel P. Berrange
2007-08-15 20:10 ` PATCH: 8/10: Add pv console to QEMU paravirt machine Daniel P. Berrange
2007-08-15 20:11 ` PATCH: 9/10: XenD device model re-factoring Daniel P. Berrange
2007-08-15 20:12 ` PATCH: 10/10: Gut the xenconsoled daemon Daniel P. Berrange
2007-08-16  7:30 ` PATCH: 0/10: Merge xenfb & xenconsoled into qemu-dm Keir Fraser
2007-08-16 12:49   ` Daniel P. Berrange
2007-08-16 12:54     ` Keir Fraser
2007-08-16 15:34       ` Daniel P. Berrange [this message]
2007-08-16 16:04         ` Keir Fraser
2007-08-16 16:13         ` Pat Campbell
2007-08-16 16:17           ` Keir Fraser
2007-08-16 16:21             ` Daniel P. Berrange
2007-08-16 19:43               ` Mark Williamson
2007-08-16 20:07                 ` [PATCH][QEMU] Shared CD-Rom Support Ben Guthro
2007-08-17 20:12         ` PATCH: 0/10: Merge xenfb & xenconsoled into qemu-dm Daniel P. Berrange
2007-08-18 10:11           ` Keir Fraser
2007-08-17 20:14     ` Daniel P. Berrange

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=20070816153415.GH16779@redhat.com \
    --to=berrange@redhat.com \
    --cc=keir@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /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.