search for: xc_dom_cor

...: konrad cc_compile_domain : dumpdata.com cc_compile_date : Mon Feb 20 12:25:42 EST 2012 xend_config_format : 4 sh-4.1# xm create /mnt/lab/latest/test.xm Using config file "/mnt/lab/latest/test.xm". Error: (1, ''Internal error'', ''panic: xc_dom_core.c:273: xc_dom_do_gunzip: inflate failed (rc=-3)'') And only on Intel.. and only if it is a 32-bit dom0. If I do the same test with a 64-bit dom0 I do not see this problem. Any thoughts of what it might be or what I should try out? My thought was to swap out the hypervisor (use a Xen 4.0)...

...tree and such yet, a simple booting "Hello World" would be fine :-) We wrote one and when trying to boot we get ( this was an uncompressed binary, no image): libxl: notice: libxl_numa.c:451:libxl__get_numa_candidate: NUMA placement failed, performance might be affected xc: error: panic: xc_dom_core.c:587: xc_dom_find_loader: no loader found: Invalid kernel libxl: error: libxl_dom.c:380:libxl__build_pv: xc_dom_parse_image failed: No such file or directory libxl: error: libxl_create.c:908:domcreate_rebuild_done: cannot (re-)build domain: -3 I attached the code ( it''s very small). Th...

...is a bug fix and should go into 4.5. >> >> I have a sneaking suspicion this is going to need to backport a very long way... >> --- >> tools/libxc/include/xc_dom.h | 10 ++++-- >> tools/libxc/xc_dom_bzimageloader.c | 20 ++++++++++++ >> tools/libxc/xc_dom_core.c | 61 +++++++++++++++++++++++++++-------- >> tools/libxc/xc_dom_decompress_lz4.c | 5 +++ >> 4 files changed, 80 insertions(+), 16 deletions(-) >> >> diff --git a/tools/libxc/include/xc_dom.h b/tools/libxc/include/xc_dom.h >> index 6ae6a9f..07d7224...

...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_dom_find_loader: trying multiboot-binary loader ... failed xc_dom_core.c:495: panic: xc_dom_find_loader: no loader found Anyone have any suggestions at all? I essentially just created a new image file, used fdisk to create the partition, and installed grub into the mbr, then copied the contents of the OS from the old disk image using "cp -a". Regards, MiL...

...> > multi-stage multiboot things, this is harder for me to help with. > > With any luck I should be able to work that bit out myself, since I > think stable's Xen has backported PVH support. So it seems it doesn't quite have enough PVH support. I get: xc: error: panic: xc_dom_core.c:702: xc_dom_find_loader: no loader found: Invalid kernel libxl: error: libxl_dom.c:638:libxl__build_dom: xc_dom_parse_image failed: No such file or directory libxl: error: libxl_create.c:1223:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl.c:1575:libxl__destroy_dom...

...xenU-2.6.9-67.0.7.EL the xen logs say: xc_dom_boot_xen_init: ver 3.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 xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... failed xc_dom_find_loader: trying multiboot-binary loader ... failed xc_dom_core.c:499: panic: xc_dom_find_loader: no loader found [2008-05-02 14:58:21 8653] ERROR (XendDomainInfo:111) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 109, in create_from_dict vm.start() Fi...

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.

...p xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... failed xc_dom_find_loader: trying Linux bzImage loader ... xc_dom_bzimageloader.c:357: panic: xc_dom_probe_bzimage_kernel: boot protocol too old (0204) failed xc_dom_find_loader: trying multiboot-binary loader ... failed xc_dom_core.c:517: panic: xc_dom_find_loader: no loader found xc_dom_release: called I have built my linux-2.6.18-xen.hg kernel this way : hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg cd linux-2.6.18-xen.hg/ make menuconfig make make modules_install make install mkinitramfs -o /boot/initrd.img-...

...ate.c libelf-private.h - -$(LIBELF_SRCS) libelf-private.h: - ln -s ../../xen/common/libelf/$@ $@ - -# add libelf bits to libxc -GUEST_SRCS-y += $(LIBELF_SRCS) +GUEST_SRCS-y += libelf-tools.c libelf-loader.c +GUEST_SRCS-y += libelf-dominfo.c libelf-relocate.c # new domain builder GUEST_SRCS-y += xc_dom_core.c xc_dom_boot.c @@ -125,8 +116,7 @@ clean: clean: rm -rf *.rpm $(LIB) *~ $(DEPS) xen \ $(CTRL_LIB_OBJS) $(CTRL_PIC_OBJS) \ - $(GUEST_LIB_OBJS) $(GUEST_PIC_OBJS) \ - $(LIBELF_SRCS) libelf-private.h + $(GUEST_LIB_OBJS) $(GUEST_PIC_OBJS) .PHONY: rpm...

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

Where is the code that maps the kernel of a DomU into memory? i.e, when you do a xm create <config file> what code is called to actually map the kernel into memory? Is it a python script or is it re-directed to Dom0 to do? Thanks. -Brian --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.

Where is the code that maps the kernel of a DomU into memory? i.e, when you do a xm create <config file> what code is called to actually map the kernel into memory? Is it a python script or is it re-directed to Dom0 to do? Thanks. -Brian --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.

Hi, I have a problem similar to the previous poster (thread: Virtual network of DomU''s), but apparently not with similar solutions... Situation: - two physical links aggregated to "default0" - dladm create-vlan on default0 with several different vlans - xVM DomU running linux connected to the same vlans when trying to ping the DomU from Dom0, I can see with snoop (in Dom0)

...by: Jeremy Fitzhardinge <jeremy@xensource.com> diff -r 3af164753238 tools/libxc/Makefile --- a/tools/libxc/Makefile Thu Jun 14 08:15:19 2007 -0700 +++ b/tools/libxc/Makefile Thu Jun 14 08:43:44 2007 -0700 @@ -47,6 +47,7 @@ GUEST_SRCS-y += $(LIBELF_SRCS) # new domain builder GUEST_SRCS-y += xc_dom_core.c xc_dom_boot.c GUEST_SRCS-y += xc_dom_elfloader.c +GUEST_SRCS-y += xc_dom_bzimageloader.c GUEST_SRCS-y += xc_dom_binloader.c GUEST_SRCS-y += xc_dom_compat_linux.c diff -r 3af164753238 tools/libxc/bootparam.h --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tools/libxc/bootparam.h Thu Jun 1...

...by: Jeremy Fitzhardinge <jeremy@xensource.com> diff -r 3af164753238 tools/libxc/Makefile --- a/tools/libxc/Makefile Thu Jun 14 08:15:19 2007 -0700 +++ b/tools/libxc/Makefile Thu Jun 14 08:43:44 2007 -0700 @@ -47,6 +47,7 @@ GUEST_SRCS-y += $(LIBELF_SRCS) # new domain builder GUEST_SRCS-y += xc_dom_core.c xc_dom_boot.c GUEST_SRCS-y += xc_dom_elfloader.c +GUEST_SRCS-y += xc_dom_bzimageloader.c GUEST_SRCS-y += xc_dom_binloader.c GUEST_SRCS-y += xc_dom_compat_linux.c diff -r 3af164753238 tools/libxc/bootparam.h --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tools/libxc/bootparam.h Thu Jun 1...

...by: Jeremy Fitzhardinge <jeremy@xensource.com> diff -r 3af164753238 tools/libxc/Makefile --- a/tools/libxc/Makefile Thu Jun 14 08:15:19 2007 -0700 +++ b/tools/libxc/Makefile Thu Jun 14 08:43:44 2007 -0700 @@ -47,6 +47,7 @@ GUEST_SRCS-y += $(LIBELF_SRCS) # new domain builder GUEST_SRCS-y += xc_dom_core.c xc_dom_boot.c GUEST_SRCS-y += xc_dom_elfloader.c +GUEST_SRCS-y += xc_dom_bzimageloader.c GUEST_SRCS-y += xc_dom_binloader.c GUEST_SRCS-y += xc_dom_compat_linux.c diff -r 3af164753238 tools/libxc/bootparam.h --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tools/libxc/bootparam.h Thu Jun 1...

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.

On 1/6/19 11:21 AM, Colin Watson wrote: > On Sat, Jan 05, 2019 at 10:51:13PM +0100, Hans van Kranenburg wrote: >> On 1/5/19 8:04 PM, Colin Watson wrote: >>> I think I'm OK with cherry-picking the relevant patch stack. Presumably >>> this would need to be in new grub-xen-pvh-bin / grub-xen-pvh binary >>> packages, as is usual for separate platform builds?

xc_dom_alloc_segment requires start address to be page align. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/libxc/xc_dom_arm.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c index ffe575b..366061d 100644 --- a/tools/libxc/xc_dom_arm.c +++ b/tools/libxc/xc_dom_arm.c @@ -290,6 +290,8 @@ int

Linux 3.11 added respective support, so I think we should follow suit. 1: xen: add LZ4 decompression support 2: libxc: add LZ4 decompression support Signed-off-by: Jan Beulich <jbeulich@suse.com>