search for: xc_dom_allocate

...wiki.xensource.com/xenwiki/VmxQuickstartGuide, but having troubles starting the guest. If 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 : 66...

...to the Debian Squeeze Xen packages, I have built the linux-2.6.18-xen.hg, but when 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...

...ret) diff -r ac45608496cd -r cdb947baea10 tools/libxl/libxl_dom.c --- a/tools/libxl/libxl_dom.c Thu May 17 16:39:51 2012 +0100 +++ b/tools/libxl/libxl_dom.c Thu May 17 17:51:32 2012 +0100 @@ -240,36 +240,37 @@ int libxl__build_pv(libxl__gc *gc, uint3 xc_dom_loginit(ctx->xch); - dom = xc_dom_allocate(ctx->xch, info->u.pv.cmdline, info->u.pv.features); + dom = xc_dom_allocate(ctx->xch, state->pv_cmdline, info->u.pv.features); if (!dom) { LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, "xc_dom_allocate failed"); return ERROR_FAIL; } - if (in...

...rks (using Linux bzImage loader) amd64, kernel from linux-image-2.6.18-5-xen-amd64 => works (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...

...''ve tested the DomU with nearly the same system at VMWare (Windows) and it works normaly, but on my server I get this 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, 0x2...

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

...if (!dom_path) + return ERROR_FAIL; + vm_path = xs_read(ctx->xsh, XBT_NULL, libxl_sprintf(ctx, "%s/vm", dom_path), NULL); retry_transaction: t = xs_transaction_start(ctx->xsh); @@ -107,7 +110,7 @@ int build_pv(struct libxl_ctx *ctx, uint32_t domid, dom = xc_dom_allocate(info->u.pv.cmdline, info->u.pv.features); if (!dom) { - XL_LOG(ctx, XL_LOG_ERROR, "xc_dom_allocate failed: %d", dom); + XL_LOG_ERRNOVAL(ctx, XL_LOG_ERROR, dom, "xc_dom_allocate failed"); return -1; } if ((ret = xc_dom_linux_build(ctx-&...

...ntoo) with kernel 3.5.7 and Xen 4.1.1. Each Dom has it''s own md (md0 for Dom0, md1 for Dom1 etc). Dom0 works fine so far, however, I''m stuck trying to create DomUs. It appears the xvda1 device on DomU is not created or accessible: Parsing config file dom1 domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 console=hvc0 root=/dev/xvda1 ro 3", features="(null)" domainbuilder: detail: xc_dom_kernel_mem: called domainbuilder: detail: xc_dom_boot_xen_init: ver 4.1, 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 domainbuilder...

..., backend phy unsuitable as phys path not a block device libxl: debug: libxl_device.c:144:disk_try_backend: Disk vdev=xvda, backend tap unsuitable 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: filen...

I''m unable to start xl console on latest xen-unstable (build with commit 8e0da8c07f4f80e14314977a11f738bd74a5b62b). > xl -vvv console sid > xenconsole: Could not read tty from store: No such file or directory I also tried "xl create -c", and it shows console from pygrub but when the "xl create" reaches the end I got the same error: > xenconsole: Could not

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.

...get error. /local/domain/2/target. Key lost : keysym=0xffe7(65511) Key lost : keysym=0xffe7(65511) __END__ Here''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 domainb...

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 -