[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] PATCH: 0/10: Merge xenfb & xenconsoled into qemu-dm


  • To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Thu, 16 Aug 2007 13:54:04 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 16 Aug 2007 05:54:48 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcfgBIY9xMaggUv3EdymygAX8io7RQ==
  • Thread-topic: [Xen-devel] PATCH: 0/10: Merge xenfb & xenconsoled into qemu-dm

On 16/8/07 13:49, "Daniel P. Berrange" <berrange@xxxxxxxxxx> 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.

So I think that qemu-dm for PV guests should be optional, and automatically
enabled only if a config option that requires qemu is enabled.

 -- Keir




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.