[Xen-devel] Latest xen-unstable and issues building/using it

[Kamala Narasimhan <kamala.narasimhan@xxxxxxxxx>]

I just got the latest xen-unstable from staging and  I encounter the
following issues -

1) I get the following build error while building 32 bit libxl (gcc
version 4.2.4) [btw, I am using 64-bit xen].  I got past the error by
simply declaring a local variable rather than directly casting and
passing info->u.pv.bootloader to fork_exec_bootloader but thought I
would mention.

libxl_bootloader.c: In function ‘libxl_run_bootloader’:
libxl_bootloader.c:391: warning: passing argument 2 of
‘fork_exec_bootloader’ discards qualifiers from pointer target type

2) I am used to using older tool stack but it appears I need to start
xencommns daemon first to use xl.  Is that correct or is there a
different wrapper I should be invoking?  It would help if there is a
wiki on the new tool stack assuming there isn't one already.

3) Also, it appears the sample config files that get installed under
/etc/xen are not updated to be in sync with libxl changes.  Example,
the old disk syntax for cdrom seg faults when used as is from the
sample config file.  Also, libxl defaults to hap=1, oos=1.  Not sure
if that is what we want; it probably has no impact on failure case I
suppose but the sample config files are not updated to include the new
hap, oos options with defaults as done with other options as they were
introduced in the past.

4) Lastly, xend/xm works right away when I try to create a domain but
xl fails when built and used as is because of qemu-dm startup failure.
 I will look into this but wanted to let the libxl developers know
that it doesn't work when it is built and used as is.

Kamala

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