similar to: XEN on old CPUs

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:

Package: xen-utils-common Version: 4.1.2-1 Severity: normal Hi, I was doing some experiments today with XL TOOLSTACK, and found few problems when trying to do PV domU boot. I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386, and with simple configuration without any disks, nics or virtual framebuffer, kernel boots (and then kernel itselfs correctly fails with information

I've a dual core system (see /proc/cpuinfo at the end) running CentOS 4.4 (fully up-to-date) and I'm running a PHP script that's parsing files and dumping the results into a database. Software versions: # rpm -q php php-4.3.9-3.22 # rpm -q MySQL-server-standard MySQL-server-standard-5.0.27-0.rhel4 # uname -srvmpio Linux 2.6.9-42.0.3.ELsmp #1 SMP Fri Oct 6 06:21:39 CDT 2006 i686

Hello! I need to purchase a new box, which I would like to optimize for good R performance. For the record, I will run Fedora Core 5 as and OS, and I wanted to know if anyone has experience with how the following affects R performance: - Is there a big advantage to having a 64-bit CPU over having a 32-bit? - Does an Opteron offer any advantages over an Athlon, and if yes, does it justify an

On Wed, 16 Apr 2008 13:46:09 +0200 Ingo Molnar <mingo at elte.hu> wrote: > > * Pekka Paalanen <pq at iki.fi> wrote: > > > > we should fix this restriction ASAP. Forcibly dropping to UP will > > > cause mmiotrace to be much less useful for diagnostic purposes of > > > Linux > > > > Ok, how do you propose we solve this? > >

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.

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.

Hi! Here is my isolinux.cfg. It's slackware based. ====================== default Kernels/bare.i/bzImage initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=8192 rw root=/dev/ram ZILIX_KERNEL=bare.i prompt 1 timeout 1200 font lat1-16.psfu display mensagem.msg F1 mensagem.msg F2 opcoes.msg F3 help.msg label linux kernel Kernels/bare.i/bzImage append - label adaptec.s kernel

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

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

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

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

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

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

We are still trying to find a reasonable solution on this one. It is not a bug in the code itself, but rather in the build system we use for tests. In the mean time, you can either safely ignore the error on the test, or build without the asm optimizations. Sorry for the inconvenience. Jean-Marc On 01/13/2016 10:31 AM, Jesus Cea wrote: > Opus 1.1.2. > > As experienced in previous

>>> Jesus Cea <jcea at jcea.es> schrieb am 13.01.2016 um 16:31 in Nachricht <56966DC0.9030604 at jcea.es>: > Opus 1.1.2. > > As experienced in previous release: > > """ > ./test-driver: line 107: 25185 Illegal instruction "$@" > $log_file 2>&1 > FAIL: celt/tests/test_unit_mathops > """ The shell

On 01/14/2016 02:23 AM, Ulrich Windl wrote: >> """ >> ./test-driver: line 107: 25185 Illegal instruction "$@" > $log_file > 2>&1 >> FAIL: celt/tests/test_unit_mathops >> """ > > The shell script most likely does not have the illegal instruction; a more > useful report would be to run the thing under a

On 14/01/16 08:23, Ulrich Windl wrote: > The shell script most likely does not have the illegal instruction; a more > useful report would be to run the thing under a debugger like gdb and then > disassemble the instruction in question. I was under the impression of this being a well known "issue" already. If you need all details I could try to find some time to provide full