Re: [Xen-devel] Xen 4.2 TODO / Release Plan

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2012-05-14 at 16:33 +0100, Ian Jackson wrote:
> >               * libxl_*_path. Majority made internal, only configdir and
> >                 lockdir remain public (used by xl). Good enough?
> 
> Yes.  We should perhaps add a note saying that the lockdir path
> function should not be used by out-of-tree callers.

Or move lockdir into xl, it's only actually used there.

So is config_dir_path now I look at it.

> >                       * libxl_cdrom_insert. Should be easy once
> >                         disk_{add,remove} done, IanJ to look at (or
> >                         doing so?).
> 
> This isn't on my proximate todo list yet.

OK.

> >               * does not automatically try to select a (set of) node(s)
> >                 on which to create a VM and pin its vcpus there. (Dario
> >                 Faggioli, patches posted)
> 
> This is still in progress somehow ?

RFC posted, awaiting another round IIRC.

> >       * Domain 0 block attach & general hotplug when using qdisk backend
> >         (need to start qemu as necessary etc) (Stefano S, patches
> >         posted, needs updates)
> 
> Is this not the same as the libxl_device_disk_local_{attach,detach}
> series you mention above ?

Yes it is.

The first entry was under "make them async if necessary", which noted
that this would be fixed by Stefano's series which was making them
internal, which is this second entry.

> >       * xl compatibility with xm:
> >               * xl support for autospawning vncviewer (vncviewer=1 or
> >                 otherwise) (Goncalo Gomes, new version of patch posted
> >                 recently)
> 
> I think we are awaiting a reworked series from Goncalo.

Yes.

> >       * Directory usage in libxl (Bastian, as part of Debian packaging,
> >         likely to defer to 4.3 unless there is some big problem with
> >         packaging deviating from upstream)
> 
> I think this can wait.

Agreed.

Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel