search for: xc_dom_malloc_filemap

...it bombs out when trying to load the kernel. I see the following in /var/log/xen/domain-builder-ng.log: xc_dom_release: called xc_dom_allocate: cmdline="root=/dev/hda1 ro quiet splash", features="" xc_dom_kernel_file: filename="/var/run/xend/boot/boot_kernel.25ua2U" xc_dom_malloc_filemap : 1723 kB xc_dom_ramdisk_file: filename="/var/run/xend/boot/boot_ramdisk.2aUKzk" xc_dom_malloc_filemap : 6646 kB xc_dom_boot_xen_init: ver 3.1, caps xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... failed xc_...

...''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') And more in the /var/log/xen/domain-builder-ng.log file : xc_dom_allocate: cmdline="root=/dev/xvda2 ro ", features="" xc_dom_kernel_file: filename="/boot/vmlinuz-2.6.18.8" xc_dom_malloc_filemap : 1528 kB xc_dom_ramdisk_file: filename="/boot/initrd.img-2.6.18.8" xc_dom_malloc_filemap : 37 MB xc_dom_boot_xen_init: ver 4.0, caps xen-3.0-x86_64 xen-3.0-x86_32p xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... failed xc_dom_find_loader: trying Linux b...

...---------------------- */ >> >> void *xc_dom_malloc(struct xc_dom_image *dom, size_t size); >> +int xc_dom_register_external(struct xc_dom_image *dom, void *ptr, size_t size); >> void *xc_dom_malloc_page_aligned(struct xc_dom_image *dom, size_t size); >> void *xc_dom_malloc_filemap(struct xc_dom_image *dom, >> const char *filename, size_t * size, >> diff --git a/tools/libxc/xc_dom_bzimageloader.c b/tools/libxc/xc_dom_bzimageloader.c >> index 2225699..964ebdc 100644 >> --- a/tools/libxc/xc_dom_bzimageloader.c >> +++ b...

...=> does not work (trying to use Linux bzImage loader) For the last one, I have in /var/log/xen/domain-builder-ng.log: xc_dom_allocate: cmdline="root=LABEL=atsina:ROOTFS ro console=hvc0", features="" xc_dom_kernel_file: filename="/boot/atsina/vmlinuz-2.6.26-1-amd64" xc_dom_malloc_filemap : 1703 kB xc_dom_ramdisk_file: filename="/boot/atsina/initrd.img-2.6.26-1-amd64" xc_dom_malloc_filemap : 6101 kB xc_dom_boot_xen_init: ver 3.2, caps xen-3.0-x86_64 xen-3.0-x86_32p xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... failed xc_dom_find_loader...

.... Thanks. domain-builder-ng.log: ### ----- xc domain builder logfile opened ----- xc_dom_allocate: cmdline="root=/dev/sda3 ro ip=:127.0.255.255::::eth0:none 2 console=xvc0", features="" xc_dom_kernel_file: filename="/boot/efw22/vmlinuz-2.6.21.7-2.neobiker.efw22xen" xc_dom_malloc_filemap : 2294 kB xc_dom_malloc : 5113 kB xc_dom_do_gunzip: unzip ok, 0x23dac4 -> 0x4fe5b0 xc_dom_ramdisk_file: filename="/boot/efw22/initrd-2.6.21.7-2.neobiker.efw22xen.img" xc_dom_malloc_filemap : 238 kB xc_dom_boot_xen_init: ver 3.3, caps xen-3.0-x86_32p xc_dom_parse_image...

..._backend: Disk vdev=xvda, using backend qdisk domainbuilder: detail: xc_dom_allocate: cmdline="debian-installer/exit/always_halt=true -- console=hvc0", features="(null)" domainbuilder: detail: xc_dom_kernel_file: filename="vmlinuz-2.6.32-5-amd64" domainbuilder: detail: xc_dom_malloc_filemap : 2367 kB domainbuilder: detail: xc_dom_ramdisk_file: filename="initrd.img-2.6.32-5-amd64" domainbuilder: detail: xc_dom_malloc_filemap : 9075 kB domainbuilder: detail: xc_dom_boot_xen_init: ver 4.2, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 d...

...xl -v create -c domutest.cfg Parsing config file domutest.cfg domainbuilder: detail: xc_dom_allocate: cmdline="(hd0)/boot/grub/menu.lst", features="(null)" domainbuilder: detail: xc_dom_kernel_file: filename="/usr/lib/xen/boot/pv-grub-x86_64.gz" domainbuilder: detail: xc_dom_malloc_filemap : 1130 kB domainbuilder: detail: xc_dom_malloc : 14779 kB domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x11a833 -> 0xe6effa domainbuilder: detail: xc_dom_boot_xen_init: ver 4.1, caps xen-3.0-x86_64 xen-3.0-x86_32p domainbuilder: detail: xc_dom_parse_image: called domainbuild...

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

Biggest change is to switch the new DTB node to /xen-core-devices instead of /xen at Stefano''s request. I also dropped the few patches title HACK etc which weren''t supposed to be there and fixed up some bits and pieces which folks commented on. George, WRT the freeze I think this is functionality which we cannot ship Xen 4.4 without. The impact is entirely constrained to the