search for: xc_dom_elfloader

Hi, I was wondering if there is any documentation on how to write a bare metal application for Xen. I don''t need to parse the device 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,

...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 14 08:43:44 2007 -0700 @@ -0,0 +1,53 @@ +#ifndef _AS...

...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 14 08:43:44 2007 -0700 @@ -0,0 +1,53 @@ +#ifndef _AS...

...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 14 08:43:44 2007 -0700 @@ -0,0 +1,53 @@ +#ifndef _AS...

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.

...al for 4.4, but we are frozen for 4.3 right now so I can't touch it) FWIW I wrote up some details of how I cross compile with Debian/Ubuntu at http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling which includes lists of packages to install etc. > I also found that xc_dom_elfloader.c’s function, xc_dom_guest_type(), > did not know about the EM_ARM machine type. You shouldn't be hitting the elf loader paths, you should instead use the zImage version of the kernel which will hit the xc_dom_armzimageloader.c code paths. We did at one point in the very early days of the...

Well, the mainline kernel just hit 2.6.27-rc1, so it's time for an update about what's new with Xen. I'm trying to aim this at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices

Well, the mainline kernel just hit 2.6.27-rc1, so it's time for an update about what's new with Xen. I'm trying to aim this at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices

Well, the mainline kernel just hit 2.6.27-rc1, so it's time for an update about what's new with Xen. I'm trying to aim this at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices

Well, the mainline kernel just hit 2.6.27-rc1, so it's time for an update about what's new with Xen. I'm trying to aim this at both the user and developer audiences, so bear with me if I seem to be waffling about something irrelevant. 2.6.26 was mostly a bugfix update compared with 2.6.25, with a few small issues fixed up. Feature-wise, it supports 32-bit domU with the core devices

...2m arm: pl011 UART driver arm: early setup code arm: shutdown, smp and smpboot arm: driver for the generic timer for ARMv7 arm: trap handlers arm: vgic emulation arm: vtimer arm: makefiles config/arm.mk | 18 + tools/libxc/xc_dom_elfloader.c | 8 +- tools/libxc/xc_hvm_build.c | 5 +- xen/arch/arm/Makefile | 76 ++++ xen/arch/arm/Rules.mk | 29 ++ xen/arch/arm/asm-offsets.c | 76 ++++ xen/arch/arm/domain.c | 269 ++++++++++++++ xen/arch/arm...

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>