similar to: Bug#695056: xen - Missing support for XZ compressed bzimage kernels

Displaying 20 results from an estimated 2000 matches similar to: "Bug#695056: xen - Missing support for XZ compressed bzimage kernels"

2013 Mar 15
0
[PATCH 4.1] Add DomU xz kernel decompression
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
2009 Mar 10
1
Bug#519149: xen-3: does not really load bzImage kernels.
Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: serious After noting that this version supposedly loads bzImage kernels: | xen-3 (3.2.1-2) unstable; urgency=low | | * Use e2fslibs based ext2 support for pygrub. (closes: #476366) | * Fix missing checks in pvfb code. | See CVE-2008-1952. (closes: #487095) | * Add support for loading bzImage files. (closes: #474509) | *
2007 Jun 15
1
[PATCH RFC] add domain builder support for bzImage kernels
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
2007 Jun 15
1
[PATCH RFC] add domain builder support for bzImage kernels
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
2007 Jun 15
1
[PATCH RFC] add domain builder support for bzImage kernels
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
2011 Nov 19
2
extlinux from syslinux 4.04 failed hard after choosing bzImage.
Hi, Today I replaced grub(1) with syslinux on my laptop, after rebooting to syslinux and selecting kernel I got massive freeze along with colorful output to screen - http://i.imgur.com/lFjFc.jpg I think I tried everything, even doing esc and writing after boot: /bzImage-3.1.0, after enter I had the same freeze with the same screen artefacts. How I installed extlinux: mkdir /boot/extlinux
2007 Apr 29
5
[patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for relocatable bzImage
Jeremy Fitzhardinge <jeremy@goop.org> writes: > Eric W. Biederman wrote: >> All it does is set a flag that tells a bootloader. >> "Hey. I can run when loaded a non-default address, and this is what >> you have to align me to." >> >> All relocation processing happens in the kernel itself. >> > > Is it possible to decompress and
2007 Apr 29
5
[patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for relocatable bzImage
Jeremy Fitzhardinge <jeremy@goop.org> writes: > Eric W. Biederman wrote: >> All it does is set a flag that tells a bootloader. >> "Hey. I can run when loaded a non-default address, and this is what >> you have to align me to." >> >> All relocation processing happens in the kernel itself. >> > > Is it possible to decompress and
2012 Feb 17
2
kernel is not a bzImage
Hello list, Since a few months I get the following error after I have recompiled Xen from hg, xen-4.1-stable or xen-unstable: ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: kernel is not a bzImage This comes from domU''s that are configured to use pv-grub. As a workaround I do have a working pvgrub-x86_64.gz from an earlier compile so I''m using that without problems.
2003 Jul 23
1
bzImage size limits?
Hi, What the the size limit of booting bzImage file with syslinux ? I have tested different sized bzImage files, and when the files are small <800K, they work with syslinuz, but at some size larger they fail to work. This was the same problem loadlin1.6 had, but loadlin1.6c fixes the issue, and I can boot bzImage sizes up to 1.5Meg with loadlin, but syslinux fails. Can you confirm this
2007 May 25
4
Extending boot protocol & bzImage for paravirt_ops
Well, it seems to be about time to have this conversation again. A rough overview of the previous thread and requirements is: 1. bzImage would not be a bare ELF file, but it would contain an ELF header+file within it 2. We need some way to add extra ELF notes into that ELF file 3. We use a "paravirtualized" bootloader type, with some other field to determine which
2007 May 25
4
Extending boot protocol & bzImage for paravirt_ops
Well, it seems to be about time to have this conversation again. A rough overview of the previous thread and requirements is: 1. bzImage would not be a bare ELF file, but it would contain an ELF header+file within it 2. We need some way to add extra ELF notes into that ELF file 3. We use a "paravirtualized" bootloader type, with some other field to determine which
2014 Mar 20
1
Checking CRC (of bzImage) before loading
Thanks all, It should be quick, so it will be implemented in C. Maybe I should have stated that I am not an expert in syslinux (intelligent but no expert). I think that I understand the "custom COM32 module" option : I simply have to change the code (and begin by looking into the files that were suggested). As for Peter's suggestion, I am not sure if I understood. Is this an
2004 Aug 25
2
Problem: booting stops during "Loading /bzimage...."
Hi I'm having problems PXE-booting a Sun-Blade 100x. As the subject line says, booting stops during "Loading /bzimage...." Broadcom UNDI PXE-2.1 (build 082) v6.2.11 Copyright (C) 2000-2003 Broadcom Corporation Copyright (C) 1997-2000 Intel Corporation All rights reserved. CLIENT MAC ADDR: 00 03 BA 44 4F F4 GUID: 00000000 0000 0000 0000 000000000000 CLIENT IP: 10.148.11.21 MASK:
2008 Aug 05
2
Bug#493856: xen-utils-3.2-1: i386 Dom0 cannot load Debian 2.6.26 amd64 kernel bzImage
Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Hi, I set the severity to important as it seems that current xen tools does not allow to load amd64 Debian kernel in DomU. I also put the debian-kernel ML in CC as I'm not sure the problem comes from xen tools or the kernel itself. Here is my configuration: Hypervisor: xen-hypervisor-3.2-1-amd64 3.2.1-2
2007 May 31
1
[patch rfc wip] first cut of ELF bzImage
I started with Vivek's ELF bzImage patch from Oct last year, mashed it to apply to hpa's new setup/boot code. This patch does a couple of things, which would probably be better split into multiple patches: 1. Glue an ELF header onto the front of bzImage. This is a real ELF header at the front of the file. Breaks akpm's laptop, apparently, but it works for me. 2.
2007 May 31
1
[patch rfc wip] first cut of ELF bzImage
I started with Vivek's ELF bzImage patch from Oct last year, mashed it to apply to hpa's new setup/boot code. This patch does a couple of things, which would probably be better split into multiple patches: 1. Glue an ELF header onto the front of bzImage. This is a real ELF header at the front of the file. Breaks akpm's laptop, apparently, but it works for me. 2.
2014 Mar 19
0
Checking CRC (of bzImage) before loading
On Wed, Mar 19, 2014 at 4:16 PM, Mau Z <zmau1962 at gmail.com> wrote: > Hi, > > I am wondering how to implement the following customer's requirement : > The system is a stand alone embedded system with no operator (with Linux). > There is one SSD for the system's usage (and that is where the system loads > from). > > The requirement is to have a duplication of
2014 Mar 19
2
Checking CRC (of bzImage) before loading
On 03/19/2014 01:30 PM, Gene Cumm wrote: > On Wed, Mar 19, 2014 at 4:16 PM, Mau Z <zmau1962 at gmail.com> wrote: >> Hi, >> >> I am wondering how to implement the following customer's requirement : >> The system is a stand alone embedded system with no operator (with Linux). >> There is one SSD for the system's usage (and that is where the system loads
2014 Mar 19
0
Checking CRC (of bzImage) before loading
On Mar 19, 2014 5:22 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > Or we could make the Linux loader (load_linux.c) throw an error on a bad > CRC, which is probably a good idea anyway. Then the ONERROR option can > be used for the fallback. > > -hpa Sounds like an excellent idea. Should linux.c32 get an override option (in case of a non-compliant