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

Re: [Xen-devel] [PATCH v1 05/10] libxl: synchronise configuration when we hotplug a device

On Fri, Jul 18, 2014 at 01:20:11PM +0100, Ian Campbell wrote:
> On Fri, 2014-07-18 at 12:22 +0100, Wei Liu wrote:
> > I'm think about adding "xl initialise-dom0", which:
> > 1. generates UUID
> > 2. writes relevant xenstore keys
> > 3. generates stub JSON config
> > 4. launches QEMU
> > 
> > I think we always needs first 3 items. But I'm not quite sure about the
> > 4th. It's more flexible to launch a process in xencommons, isn't it?
> I suppose so. Perhaps we can simply provide some --no-do-foo which would
> allow each of these to be turned off so that an interested admin can
> launch it themselves?

What I had in mind is situation like this: if we are to launch some
other service, we would then need to modify a C program, which is a bit
error prone IMHO. And if we make mistake in parameters in one of our
releases, admin needs to either a) recompile xl or b) use --no-do-foo
then write some runes in xencommon.

For plan a), recompiling a binary is a hassle comparing to modifying a
script. For plan b), the admin ends up modifying the script anyway.

If admin wants to launch new service then he / she ends up editing some
init-scripts as well.

And AIUI we don't have qemu-system-arm for the moment. So picking up the
right arch for QEMU isn't really a requirement now.

So I propose we implement the first 3 items for the moment, and leave
launching QEMU as is in xencommon.


> Ian.

Xen-devel mailing list



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