search for: shtab

....33-xen savedefault boot When I try to boot, though, I get as far as the xen kernel trying to load, and then grub spits this out, and the machine reboots: root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen-3.0.4-1.gz [Multiboot-elf, <0x100000:0x9a878:0x5a788>, shtab=0x1f5078, entry=0x100000] module /vmlinuz-2.6.16.33-xen root=/dev/sda2 ro console=ttyS1,115200 noreboot sync_console [Multiboot-module @ 0x1f6000, 0x52afa0 bytes] module /initrd.img-2.6.16.33-xen [Multiboot-module @ 0x721000, 0x4b6000 bytes] Is there anything I''m missing? Any...

...----- -------------------------------------------------------------------- Booting ''Xen 3.3.2-rc5 / Debian GNU/Linux, Kernel 2.6.18.8-xen'' root (hda0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/xen-3.3.2-rc5.gz [Multiboot-elf,<0x100000:0xfd6b0:0x77950>,shtab=0x275078,entry=0 module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 [Multiboot-module @ 0x276000,0x5419c0 bytes] module /boot/initrd.img-2.6.18.8-xen Error 15: File not found press any key to continue ... ---------------------------------------------------------------------------...

...----- -------------------------------------------------------------------- Booting ''Xen 3.3.2-rc5 / Debian GNU/Linux, Kernel 2.6.18.8-xen'' root (hda0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/xen-3.3.2-rc5.gz [Multiboot-elf,<0x100000:0xfd6b0:0x77950>,shtab=0x275078,entry=0 module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 [Multiboot-module @ 0x276000,0x5419c0 bytes] module /boot/initrd.img-2.6.18.8-xen Error 15: File not found press any key to continue ... ---------------------------------------------------------------------------...

...----- -------------------------------------------------------------------- Booting ''Xen 3.3.2-rc5 / Debian GNU/Linux, Kernel 2.6.18.8-xen'' root (hda0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/xen-3.3.2-rc5.gz [Multiboot-elf,<0x100000:0xfd6b0:0x77950>,shtab=0x275078,entry=0 module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 [Multiboot-module @ 0x276000,0x5419c0 bytes] module /boot/initrd.img-2.6.18.8-xen Error 15: File not found press any key to continue ... ---------------------------------------------------------------------------...

I'm seeing this on a HP Blade and i'm not sure why this is happning since the nature of the issue is so wierd. I compiled mboot.c with a DEBUG defined in the mboot.c file. In the funciton init_mmap(), it prints the e820 map and on the HP blade this map values come out to be totally random. Some weird numbers which dont make any sense at all. However, if i add a while(1); or a exit(1); at

...oot/xen-linux-2.6.11-ocxen0 root=/dev/hda2 ro console=tty0 console=ttyS1,19200 savedefault boot and here''s the boot output: root (hd0,1) Filesystem type is ext2fs, partition type 0x83 kernel /boot/xen*2.0.6.gz dom0*mem*131072 noreboot [Multiboot*elf, <0x100000:0x3f070:0x35f90>, shtab*0x175078, entry*0x100000] module /boot/xen*linux*2.6.11*ocxen0 root*/dev/hda2 ro console*tty0 console*tt yS1,19200 [Multiboot*module @ 0x176000, 0x3fc808 bytes] savedefault I''m running Debian testing on IBM HS20s (Xeons) compiled with gcc-3.3 I have a feel...

Peter, Is this page update to date? http://www.kernel.org/git/?p=boot/syslinux/syslinux.git;a=shortlog I sent a multiboot symbol table loading patch (syslinux-3.11-mboot-sym_table-patch) a few months ago and I thought you have checked it in. I didn't follow up after that. But i dont see it in the changes now, should i resend it? thanks, Ram

Hello, I use Tim's mboot.c32 to load multiboot kernels over pxelinux. However, some kernels require the symbol table and other information in the ELF section header table to be able to load properly. This functionality is not present in mboot.c now, so I added support for it. The patch is attached. It would be great if you can push this into the next release of syslinux so ELF multiboot

...commands before booting, or ''c'' for a command-line. Booting ''Debian-based Dom0 in text mode (from testing)'' root (cd) Filesystem type is iso9660, using whole disk kernel /boot/xen-3.0.3.0.gz watchdog [Multiboot-elf, <0x100000:0x89658:0x4b9a8>, shtab=0x1d5078, entry=0x100000] module /boot/vmlinuz-2.6.16.29-xen ro 2 selinux=0 ramdisk_size=32758 image=roo tfs.img boot=cow [Multiboot-module @ 0x1d6000, 0x2d2280 bytes] module /boot/initrd-2.6.16-xen.img [Multiboot-module @ 0x4a9000, 0xafca00 bytes] __ __ _____ ___ _____ ___...

...not. Has anyone else encountered this problem on EMT64 hardware? Here are the errors I am getting: This is on a SLES 9 box, gcc version 3.3.3 (SuSE Linux): kernel (hd0,0)/boot/xen.gz dom0_mem=256000 com2=19200,8n1 console=vga,com2 nor eboot [Multiboot-elf, <0x100000:0x5e358:0x22ca8>, shtab=0x181078, entry=0x100000] module (hd0,0)/boot/vmlinuz-2.6-xen0 root=/dev/sda6 ro console=tty0 [Multiboot-module @ 0x182000, 0x67e5f0 bytes] module (hd0,0)/initrd-2.6.11.12-xen0 __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \...

...pci_alloc_consistent -> dma_alloc_coherent). Looks like an issue with the amount of memory in dom0. Is this known? thanks, -chris root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz com1=115200,8n1 console=com1,vga [Multiboot-elf, <0x100000:0x7c3e0:0x29c20>, shtab=0x1a6078, entry=0x100000] module /vmlinuz-2.6.12-xen0 root=/dev/VolGroup00/LogVol00 ro console=tty0,ttyS0 [Multiboot-module @ 0x1a7000, 0x6b43f8 bytes] module /initrd-generic-2.6.img [Multiboot-module @ 0x85c000, 0x2ab400 bytes] __ __ _____ ___ _ _ \ \/...

x86:x2apic: Disable x2apic on x86-32 permanently x2apic initialization on x86_32 uses vcpu pointer before it is initialized. As x2apic is unlikely to be used on x86_32, this patch disables x2apic permanently on x86_32. It also asserts the sanity of vcpu pointer before dereference to prevent further misuse. Signed-off-by: Fengzhe Zhang <fengzhe.zhang@intel.com> diff -r 02c0af2bf280

Our newly build xen kernel does not boot. The error message is : Invalid or unsupported executable format. I have build xen from the xen-2.0.4 source (make world, make install) on a debian sarge system. I have not changed any of the kernel configurations, I did make an initrd image. The entry in my menu.lst is : title Debian GNU/Linux, kernel 2.6.10-xen0 root (hd0,0) #

...ot gentoo on xen, but it doesn''t work. What can I do? Booting ''Xen 3.0.0 / Linux 2.6.12.5'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz dom0_mem=131072 com1=115200,8n1 [Multiboot-elf, <0x100000:0x641cc:0x27e34>, shtab=0x18c078, entry=0x100000] module /vmlinuz-2.6.12.5-xen-0 root=/dev/md0 console=tty0 console=ttyS0,115200 hdd=ide-scsi showopts debug [Multiboot-module @ 0x18d000, 0x33b468 bytes] __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |...

...think it has something to do with the ACPI or APIC on the processors. Here is the boot log from a console connection: * Ubuntu, kernel 2.6.15-26-amd64-server * kernel /boot/xen-3.0.gz com1=115200,8n1 console=vga,com1 [03;00H [Multiboot-elf, <0x100000:0x9e898:0x5a768>, shtab=0x1f9078, entry=0x100000] [04;00H module /boot/vmlinuz-2.6.16.33-xen_test6 root=/dev/sda1 ro console=tty0 console [05;00H =ttyS0 [06;00H [07;00H __ __ _____ ___ _ _ _ \ \/ /___ _ __ |___...

Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,

Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,

...bootlog is like this: Booting ''Xen -- SUSE Linux Enterprise Server 11 SP2 - 3.0.58-0.6.2'' root (hd0,5) Filesystem type is ext2fs, partition type 0x83 kernel /boot/xen.gz console=com1 com1=57600 loglvl=all guest_loglvl=all [Multiboot-elf, <0x100000:0x1ace98:0x5d168>, shtab=0x30a078, entry=0x100000] module /boot/vmlinuz-3.0.58-0.6.2-xen quiet sysrq=yes panic=9 console=ttyS0,576 00 resume=/dev/disk/by-id/ata-ST9500530NS_9SP1KKAS-part2 splash=silent showopts log_buf_len=64M [Multiboot-module @ 0x30b000, 0xb8fc80 bytes] module /boot/initrd-3.0.58-0.6.2-xen [Multib...

...now get a crash when eth0 is started, here is the full boot log: Booting ''Xen 3.4 / Linux 2.6.29-rc6-tip'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz com1=115200,8n1 console=com1,vga iommu=1 [Multiboot-elf, <0x100000:0x131748:0x8e8b8>, shtab=0x2c0078, entry=0x100000] module /vmlinux.bin.gz-2.6.29-rc6-tip root=/dev/sda2 console=hvc0 earlyprink=xe n pci=nomsi panic=5 [Multiboot-module @ 0x2c1000, 0xa13c48 bytes] __ __ _____ _ _ _ _ _ \ \/ /___ _ __ |___ /| || | _ _ _ __ ___| |_...

I ran some iperf tests today and it looks like the etherbridge is the limiting factor on throughput. In the beforetime, I saw great throughput to the VMs; over 800 Mbps. With the bridge, the numbers are in the 400s somewhere. Is this the speed I can expect from the bridge? Is there some tuning I should try, or another way to get more bandwidth into the VMs? This is with xen-2.0, 2.4.27-xen0