similar to: Re: Possible bug with kernel decompressor.

Hi, I recently took delivery of a bunch of HP BL25p blades to add to my collection. I am attempting to install Centos4 x86_64 using PXE - the initial PXE DHCP stuff works, and the kernel and initrd are downloaded, but the server then immediately clears the screen and displays: "1706-Smart Array Controller Extended BIOS Data Area Memory Corrupted Array Controller Interrupt 14h BIOS Cannot

Hi, I''m trying to boot xen dom0 on a Compaq Proliant 2500 but so far I have been unsuccessful, I get (XEN) Not enough memory to stash the DOM0 kernel image. On a normal linux 2.6 kernel to boot I have pass "memmap=exactmap memmap=640K@0 memmap=319M@1M" to the kernel at boot otherwise it hangs because of the way Compaq Bios reports the system memory. I''ve tryed to use

Hello Xen Users, I am facing a problem getting my installation of XEN boot up on a Red Hat Linux Guest OS. What''s happening is that the grub loader tries to install Xen but after a while it crashes and starts rebooting recursively. I have tried both the entries listed below. I am using the following entries in the grub.conf file: title Xen-bhatia 3.0 / XenLinux-bhatia 2.6.16

Hello, I'm having a challenge with increasing vmalloc memory beyond 512M using pxelinux.0 to boot. This config works fine: --- # Configuration file # linux-2.6.20-1.2962.fc6 DEFAULT linux LABEL linux kernel kernels/vmlinuz-2.6.20-1.2962.fc6 append initrd=initrds/bladeinitrd-2.6.20-1.2962.fc6.img enforcing=0 vmalloc=512M --- If I increase vmalloc to 513M, I get errors

This is a collection of patches pulled over from Linux. 1: Decompressors: get rid of set_error_fn() macro 2: bzip2: Add missing checks for malloc returning NULL 3: Decompressors: remove unused function from unlzma.c 4: Decompressors: fix header validation in unlzma.c 5: Decompressors: check for read errors in unlzma.c 6: Decompressors: check for write errors in unlzma.c 7: Decompressors: validate

On Tue, 15 Oct 2024 14:20:02 +0400 Mariam Arutunian <mariamarutunian at gmail.com> wrote: > Package: libxen > Version: 4.17.3 > Severity: normal > X-Debbugs-Cc: mariamarutunian at gmail.com > > Dear Maintainer, > A vulnerability identified as CVE-2014-4608 was discovered and fixed in LZO decompressor in the Linux kernel with the following commit:

Hi guys! I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 works fine both memtest 4.1 and 4.2. With version 6.00 no error message caught, only writes out dots. Any keypress does a reboot.With version 5.01 the error message is the follow:Loading images/memtest/memtest86... okBooting kernel failed: Bad file

Hello, I am using with success SYSLINUX-1.48 to boot a CD-Rom in order to realize an automatic installation of Linux. Actually all messages during the boot step are displayed on VGA screen. In the operational version, we have only a VT on COM1. I have tested to modified my syslinux.cfg like the following listing but boot messages are always displayed on VGA screen ! Can you help me, please ? (I

Hello, I often see the double dash -- in the append line in isolinux/syslinux configurations I only know this as "disable further option processing" e.g. in bash. What is the function of the -- ? I don't see any difference if I use it don't use it. E.g here : append vga=normal initrd=/install.amd/initrd.gz -- quiet append vga=normal initrd=debian-installer/amd64/initrd.gz

+-- On Tue, 18 Oct 2016, Richard W.M. Jones wrote --+ | I was able to reproduce this myself: | | $ virt-builder ubuntu-16.04 --firstboot-command "dpkg-reconfigure openssh-server" --root-password password:123456 | | $ qemu-system-x86_64 -nodefconfig -display none -machine accel=kvm:tcg -m | 2048 -boot c -drive file=ubuntu-16.04.img,format=raw,if=ide -netdev |

On 01.05.20 20:43, Dan Williams wrote: > On Fri, May 1, 2020 at 11:14 AM David Hildenbrand <david at redhat.com> wrote: >> >> On 01.05.20 20:03, Dan Williams wrote: >>> On Fri, May 1, 2020 at 10:51 AM David Hildenbrand <david at redhat.com> wrote: >>>> >>>> On 01.05.20 19:45, David Hildenbrand wrote: >>>>> On 01.05.20

On 01.05.20 20:43, Dan Williams wrote: > On Fri, May 1, 2020 at 11:14 AM David Hildenbrand <david at redhat.com> wrote: >> >> On 01.05.20 20:03, Dan Williams wrote: >>> On Fri, May 1, 2020 at 10:51 AM David Hildenbrand <david at redhat.com> wrote: >>>> >>>> On 01.05.20 19:45, David Hildenbrand wrote: >>>>> On 01.05.20

On 01.05.20 20:03, Dan Williams wrote: > On Fri, May 1, 2020 at 10:51 AM David Hildenbrand <david at redhat.com> wrote: >> >> On 01.05.20 19:45, David Hildenbrand wrote: >>> On 01.05.20 19:39, Dan Williams wrote: >>>> On Fri, May 1, 2020 at 10:21 AM David Hildenbrand <david at redhat.com> wrote: >>>>> >>>>> On 01.05.20

On 01.05.20 20:03, Dan Williams wrote: > On Fri, May 1, 2020 at 10:51 AM David Hildenbrand <david at redhat.com> wrote: >> >> On 01.05.20 19:45, David Hildenbrand wrote: >>> On 01.05.20 19:39, Dan Williams wrote: >>>> On Fri, May 1, 2020 at 10:21 AM David Hildenbrand <david at redhat.com> wrote: >>>>> >>>>> On 01.05.20

Hello, I have a few proliant 5000 servers with buggy BIOS that always reports 16MB ram. In order for normal linux kernel to boot I need to specify memmap=exactmap memmap=640k@0 memmap=<RAMSIZE -1>M@1M My xen (binary install) dies as it complains that it "cannot allocate memory to stash the kernel image" which I''m sure is because of the above. How can I inform XEN of the

On 01.05.20 19:45, David Hildenbrand wrote: > On 01.05.20 19:39, Dan Williams wrote: >> On Fri, May 1, 2020 at 10:21 AM David Hildenbrand <david at redhat.com> wrote: >>> >>> On 01.05.20 18:56, Dan Williams wrote: >>>> On Fri, May 1, 2020 at 2:34 AM David Hildenbrand <david at redhat.com> wrote: >>>>> >>>>> On

On 01.05.20 19:45, David Hildenbrand wrote: > On 01.05.20 19:39, Dan Williams wrote: >> On Fri, May 1, 2020 at 10:21 AM David Hildenbrand <david at redhat.com> wrote: >>> >>> On 01.05.20 18:56, Dan Williams wrote: >>>> On Fri, May 1, 2020 at 2:34 AM David Hildenbrand <david at redhat.com> wrote: >>>>> >>>>> On

On 29.04.20 18:08, David Hildenbrand wrote: > Some paravirtualized devices that add memory via add_memory() and > friends (esp. virtio-mem) don't want to create entries in > /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware (e.g., e820), but > only

On 29.04.20 18:08, David Hildenbrand wrote: > Some paravirtualized devices that add memory via add_memory() and > friends (esp. virtio-mem) don't want to create entries in > /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware (e.g., e820), but > only

Hello, FYI. This problem looks similar to the problem I reported in Februari http://www.syslinux.org/archives/2013-February/019517.html Kind regards, Wim. On 06/28/2013 10:02 AM, Matt Fleming wrote: > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: >> Hi guys! >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and >> i have issues to boot it with