similar to: Processed: severity of 519149 is important

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) | *

Processing commands for control at bugs.debian.org: > retitle 519149 xen-3: only loads bzImage domU kernels, not dom0 Bug#519149: xen-3: does not really load bzImage kernels. Changed Bug title to `xen-3: only loads bzImage domU kernels, not dom0' from `xen-3: does not really load bzImage kernels.'. > thanks Stopping processing here. Please contact me if you need assistance.

Hi William, Please could you provide some more details of the failure since this functionality works for me both with the Debian packages and upstream and I don't recall any additional patches upstream. Are there any messages in the logs? Particularly /var/log/xen/xend* and /var/log/xen/domain-builder-ng.log. Which kernel are you trying to load? The standard Lenny -686-bigmem kernel

Hi, There are a couple of open bugs against Xen-3 with patches which directly impact my efforts to have Debian Installer work in a Xen guest domain for Lenny. ?In both cases the relevant fixes are already committed in upstream Xen and I've been rebuilding and using the Debian packages with them without problems. First is #476366 which is a pygrub issue that prevents booting a guest using

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

Processing commands for control at bugs.debian.org: > reopen 678923 Bug #678923 {Done: George Shuklin <george.shuklin at gmail.com>} [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Bug reopened Ignoring request to alter fixed versions of bug #678923 to the same values previously set > End of message, stopping processing here. Please contact me if you need

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

Hello, Is there a function to check a bzImage CRC ? If (ImageCRC("/bzImage") == -1) Load_kernel("/BACKUP/bzImage") or what else Thanks Regards Johann

Thanks all, I did find extlinux in "my syslinux tarball" (I think that I understand my confusion now - I will explain at the end). So, now almost everything is fine...... Clearly my extlinux.conf is working (I can see my output on the console (SAY XXX)) I have a bzImage + rootfs.tar I tried : 0) mount /dev/sda1 /mnt/MyMountForSda1 -->> success 1) cd /mnt/MyMountForSda1

Hi, I'm pleased to announce release 0.8 of efilinux, a reference implementation of a minimal UEFI bootloader. This bootloader has no bells or whistles, it is simply a prototype with the minimum amount of smarts required to load a linux kernel (though loaders for other formats could be added). Currently it only supports booting x86-64 bzImages but i386 support is planned for release 0.9, with

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

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

Processing commands for control at bugs.debian.org: > severity 435406 wishlist Bug #435406 [xen-utils-common] xen-utils-common: xm save does not use compression Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Processing commands for control at bugs.debian.org: > severity 503044 wishlist Bug #503044 [xen-utils-common] xen-utils-common: should make the loopback device default to supporting more nodes Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Processing commands for control at bugs.debian.org: > severity 655303 wishlist Bug #655303 [xcp-xapi] xcp-xapi: document network configuration in README.Debian Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 655303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655303 Debian Bug Tracking

Processing commands for control at bugs.debian.org: > severity #674137 wishlist Bug #674137 [xcp-xapi] xcp-xapi: default ports in xapi Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 674137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674137 Debian Bug Tracking System Contact owner at

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

Package: src:xen Version: 4.1.3-4 Severity: serious The bzimage loader used in both libxc and the hypervisor lacks XZ support. Debian kernels since 3.6 are compressed with XZ and can't be loaded. Support for XZ compression was added in changeset 23002:eb64b8f8eebb somewhere last year. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990,

On 6/7/19 10:48 PM, H. Peter Anvin via Syslinux wrote: > On 6/7/19 10:34 PM, H. Peter Anvin via Syslinux wrote: >> On 6/7/19 10:25 PM, H. Peter Anvin via Syslinux wrote: >>>> >>>> However, the CRC polynomial for zlib and the Linux kernel should both be the >>>> same: 0x04c11db7. >>> >>> I just double-checked, and the CRC tables are

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