Re: [Xen-devel] libxl config datastructures

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

tamas.k.lengyel@xxxxxxxxx writes ("Re: [Xen-devel] libxl config 
datastructures"):
> I'm OK with the config parser in Xlu, my problem is the conversion between 
> XLU_Config and the datastructure the libxl domain creation functions are 
> expecting. Right now the only way would be to duplicate the code in xl to do 
> the transition, which I don't want to do, or by calling xl itself instead of 
> using libxl, which I found very ugly and hack-ish.

Yes.

> Further problems with XLU_Config is the fact that the datastructure is 
> transparent. It would be fine, if there were more accessor functions written 
> for it, such that it could be saved again as a file or dumped in a char *. 
> Also would be required the ability to change elements of a XLU_ConfigList.

I have just gone and looked at the code and you mean
  parse_config_data
in xl_cmdimpl.c.

I think this should be in libxlu.  Sadly this is too late for Xen 4.2.

If you would like to send patches to move the code from
parse_config_data into libxlu, we'll consider them for 4.3.

Thanks,
Ian.

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