similar to: Using syslinux to boot xen without initrd

Erwan, I'm using syslinux v3.85 Gene, the kernel was built using buildroot (and I checked that Xen support was enabled). Didn't try without the menu, will see that now. Also, I saw a short note on syslinux mboot wiki page: "A really good use case for this (using mboot.c32) is booting Xen <http://xensource.com>, or any other hypervisor-based virtualization pieces that also

Can you tell us the Syslinux version you use ? Le 8 sept. 2015 3:21 PM, "Ingrid Ribeiro Galvez via Syslinux" < syslinux at zytor.com> a ?crit : > Hello all, > > I have a Linux kernel image with Xen compiled for an embedded system. It > doesn't need an initrd as everything required for it to boot is already in > the final kernel image, and it works perfectly.

Hello list, I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this mission failed.. Hope you can help me by finding the reason for my problem. I downloaded the xen sources from http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz and compiled them by running "make" and "./install.sh". This seemed to work. After setting up grub like this,

Hi all, I installed Xen 3.0.2 using Gentoo portage. The kernel boots ok to the console but when I try to login either as root or myself it won''t authenticate. I read some posts that mentioned not having a populated /dev directory but this is in place. It also contains a full range of tty* and has console in it. I''m at a loss for what to look for. The console login is ok

Hi all, I have a machine that won't boot syslinux 4.02 but will boot syslinux 3.53. We've installed syslinux 4.02 on a number of machines but only this one has a problem. The problem is that the machine hangs entirely after printing "boot:" on the tty. The stanza being booted in /boot/extlinux.conf is: label xe # XenServer kernel mboot.c32 append /boot/xen.gz

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to boot into the shell of a XenServer 5.6 (I believe CentOS 5.5 underneath). I added init=/bin/sh to the boot line, but I'm still getting an error. Here is the boot line: mboot.c32 /boot/xen.gz com2=57600,8n1 console=com2,vga dom0_mem=752M lowmem_em ergency_pool=1M crashkernel=64M at 32M --- /boot/vmlinuz-2.6-xen

Hello there I built development version of syslinux from git 6.04-pre3-3-(sometag) and I am trying to boot a slackware-current system with it. I do not use a separated partition for `/boot`. It's just `/dev/sda1` here for `/` and `/boot` is just a folder. I simply use `mbr.bin` against a DOS partition table and the first partition having the bootable flag. With this layout, the only

Hi, I''ve been trying to use E5520 and X5650 together in an heterogeneous pool without success. I know the combination is not on the official XenServer supported list (http://hcl.xensource.com/CPUPoolsList.aspx), but I thought it would be possible to set the mask anyway and see for myself if the combination works… My problem is that the mask doesn''t "stick" after a

Hi How do I make an initrd for xen. I''m trying to boot rhel3 in fc4, and it keeps getting stuck at Freeing unused kernel memory. I''ve created the device files, but it still doesn''t boot up. I''m pretty sure that the solution lies in makeing an initrd file. Currently my xenU kernel is 2.6.11-1.1369_FC4xen0. Can someone please tell me how to do this? Many

Hello List, I'm ironing out details to upgrade a few systems to CentOS7. My servers have BMC with Serial over LAN support. In C5 and C6, I determined how to have BIOS/POST, kernel, and serial console access. I'm reading up on the method to accomplish the pieces with C7. Presently SoL output works, so I see BIOS/POST messages and the GRUB boot list. My changes to enable serial

I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)   root (hd1,0)   kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1   module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen   module

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

Hi all, A number of people have posted to the Xen lists recently wanting to network-boot Xen on machines whose NICs are not supported by GRUB. I''ve been writing a module for PXELINUX that will allow it to boot Xen directly over the network on PXE-enabled machines, without relying on any hacks (mbootpack, &c.), or needing to write/port any device drivers. I have a version of it

On a selection of boxes, ntpd running in Xen Dom0 reproducibly exhibits extermely high noise/jitter. Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise. Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0? Is the problem a config issue, or a bug? Already reported this downstream; everybody''s "stumped".

On a selection of boxes, ntpd running in Xen Dom0 reproducibly exhibits extermely high noise/jitter. Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise. Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0? Is the problem a config issue, or a bug? Already reported this downstream; everybody''s "stumped".

The Xen boot option ''ser_baud=<baud>'' has been removed from the unstable tree. If you were still using this obsolete option then the effect is that you will get no serial output when you boot Xen, which may lead you to believe that there is a more serious problem. To fix this you must move to the new boot option: ''com1=<baud>,8n1'' -- Keir

Hello, I had tried to install Xen binary on Fedora 2 according to the user manual. My platform has LVM. I tried 2 different grub entries for zen: The first was: kernel /xen.gz dom0_mem=131072 module /vmlinuz-2.6.10-xen0 root=LABEL=/ ro console=tty0 It says the it can''t find the / (root) and looks for a floppy or an NFS root. (I don''t have a floppy at all and

On Oct 11, 2015 1:26 AM, "Michael Glasgow" <glasgow at beer.net> wrote: > > Gene Cumm wrote: > > >> My test x86-64 binaries: > > >> > > >> https://sites.google.com/site/genecsyslinux/sl604p0g17-x64.tgz?attredirects=0&d=1 > > > > On Fri, Oct 2, 2015 at 4:46 PM, Derrick M <derrick.martinez at gmail.com> wrote: > >

Hi List, I run XEN 2 since some month (unfortunatly installed by a fiend of mine). Recently I bought some new hardware and tried to get XEN 3 running on a Debian Sarge 3.1. I installed via the Debian installer a RAID 1 with LVM. even though there are some devfs_mk_dir errors systems comes up. Now I installed XEN but system doe not boot as the boot device seems not to be recocnized by the

Hello, I have a big startproblem with the dom0 kernel. I use the latest stable xen with the 2.6.10 kernel. menu.lst: --- title Xen 2.05 / XenLinux 2.6.10 kernel /boot/xen.gz dom0_mem=512M noreboot module /boot/vmlinuz-2.6.10-xen0 root=/dev/sda1 ro console=tty0 --- Starterror: --- (XEN) Initial guest OS requires too much space (XEN) (8MB is greater than 0MB limit) --- System: I use an fresh