Re: libxl config datastructures

[tamas.k.lengyel@gmail.com]

[-- Attachment #1.1: Type: text/plain, Size: 1357 bytes --]

Hi Ian,

> I don't understand why you aren't happy to use just the config parser supplied in libxlu. 

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.

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.

Currently, the only way I was able to do this is by unmasking XLU_Config and XLU_ConfigList, and interacting with the elements directly. That way I can change the config, export it back to a file, then by forking and calling xl itself (!) I can create the VM with the modified config. It works, its a hack, I don't like it.

I would be happy to send you patches that would enable me to do the XLU_Config modifications I need to do without needing to unmask it.

As for libxl, without the datastructure conversion I won't be able 
to use it and have to do the ugly fork and xl call instead..

Tamas
 

[-- Attachment #1.2: Type: text/html, Size: 1730 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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