similar to: libxc: Question on kernel image unzipping

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

libxc: Use vcpu_guest_context_any_t instead of two pages Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 14a9a1629590 tools/libxc/xc_dom_boot.c --- a/tools/libxc/xc_dom_boot.c wed aug 27 10:26:50 2008 +0100 +++ b/tools/libxc/xc_dom_boot.c wed aug 27 12:07:28 2008 +0100 @@ -187,7 +187,7 @@ int xc_dom_boot_image(struct xc_dom_imag int xc_dom_boot_image(struct

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>

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

On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other >> than the gzip one) just use plain malloc/realloc and therefore the buffer ends >> up

I have just applied this to staging-4.1. Since my own backport and Bastian''s were entirely identical, I haven''t tested it other than to compile it... Thanks, Ian. commit 5e73e3548ce70e433a03843ac4fc21a49277baad Author: Ian Jackson <ian.jackson@eu.citrix.com> Date: Fri Mar 15 18:09:51 2013 +0000 Add DomU xz kernel decompression Signed-off-by: Jan Beulich

xc_dom_alloc_page deals with virtual address not physical address. When an ELF is loaded, virtual address and physical address may be different. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/libxc/xc_dom_arm.c | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c index a40e04d..75a6f1c

"H. Peter Anvin" <hpa at zytor.com> on Tue, 2013/12/03 20:26: > On 10/24/2013 01:09 AM, Christian Hesse wrote: > >>> > >>> version 6.02-pre5 works, 6.02-pre6 does not. > >> > >> Struggled with git bisect, but finally succeeded: > >> > >> 8f470e7bfe75f6401f6c5432988c620b863ad274 is the first bad commit > >>

Hello All... I have installed xen 3.3. I m running a Virtual Machine using an image file that has fedora 8 installed in it. When i view the Virtual Machine using VNC Viewer or on the browser using tight vnc,there appears 2 pointers .I need to solve this problem. Kindly suggecst me the correct solution. Waiting for responses. -- Thanks and Regards Anitha

Hi, I''m using Debian 5 (lenny) with Xen 3.2-1. When I try to start a Linux guest (installed with debootstrap like this <http://www.option-c.com/xwiki/Create_a_Debian_VM_with_debootstrap>), the VM hangs right after starting crond. This is exactly before the login prompt (which doesn''t come up). 1) In the internet, the solution is an /extra/ line in the configuration

> Damn, I messed up the git tags so I wasn't looking at an accurate list > of changes between -pre1 and -pre2. > > Your error is likely being triggered by the recent kernel changes. For > x86-64 we now try to boot a Linux kernel via the 32-bit entry point. > It's possible that code doesn't work correctly with vmware. > > Could you grab -pre10 and change the

Hi, Line 762 of efi/main.c (git firmware branch) should be changed to if (hdr->version < 0x20b) { Without this change syslinux efi64 gives out "handover protocol unimplemented error" and fails to boot. With this change syslinux boots the kernels fine (tested with 3.6.9 and 3.7rc6 kernels). Please fix this. Thanks in advance. Regards. Keshav

Hello, after I fixed one problem, the next one raised up. I am trying to create a guest domain. I specified the configurations in /etc/xen-tools/xen-tools.conf and I ran $sudo xen-create-image --hostname=virtualrouter1 --role=udev the output is: sudo: xen-create-image: command not found I searched all directories for a file with this name but couldn''t find any. Is this possible? I am

Howdy, I know that syslinux doesn't currently support this, but does anyone here know how I might go about getting some sort of boot process together that would have a single firmware image as opposed to seperate files for initrd, kernel, and root fs? Thanks.

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

> Actually, can you grab the version I built from, > > ftp://syslinux.org/pub/syslinux/tests/syslinux-6.02-pre2.tar.gz > > And see whether things work for you? I'm just trying to rule out any > kind of distribution error on the Syslinux build machine. > > -- > Matt Fleming, Intel Open Source Technology Center > _______________________________________________

PXELINUX has stopped recognizing the keeppxe option on the kernel command line. Here is a patch to make it work again. With COM32, it is no longer possible to use preprocessor directives to determine the SYSLINUX variant. The code inside the #if will never be compiled. So, I changed it to use syslinux_filesystem() to determine the variant. Also, I moved the relevant code from