search for: xc_dom_kernel_file

...I do "xm create -f <whatever>.cfg -c", I see a pygrub menu, but 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_do...

...en I start my DomU, I have got this error message : Error: (2, ''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: tryi...

...+ state->pv_kernel.data, + state->pv_kernel.size); if ( ret != 0) { LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, "xc_dom_kernel_mem failed"); goto out; } } else { - ret = xc_dom_kernel_file(dom, info->u.pv.kernel.path); + ret = xc_dom_kernel_file(dom, state->pv_kernel.path); if ( ret != 0) { LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, "xc_dom_kernel_file failed"); goto out; } } - if ( info->u.pv.ramdisk.path &...

...using ELF-generic loader) amd64, kernel from linux-image-2.6.26-1-amd64 => 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: ca...

...is error message. I useing gentoo as Dom0. I tried also a gentoo DomU with the same result. 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_mallo...

Here are two patches that let xm create, save and restore extract and preserve elfnotes read by the domain builder. This is handy for a few things. In particular, I''d like it so that xm can decide whether or not guest domains support fast resume (if save fails, or for checkpointing). _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

...le because blktap not available libxl: debug: libxl_device.c:219:libxl__device_disk_set_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: ve...

...e''s running xl create on domutest with the -v option: __START__ [root@xentest2012 noauto]# 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...

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

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -