similar to: PV-Grub and multiboot kernels

Hey guys, what I am trying to do is a chainload into grub2 installation in a DomU. So far I determined, PV-GRUB does not understand grub2''s grub.cfg notation. So I created a dummy menu.lst which has the needed root kernel and initrd rows and then referenced this to the DomUs config. The main intention to do this, is to be able to use kernel upgrades without touching the menu.lst for

Good evening all, I''ve all but finished installing Xen 2.0.5, XenLinux 2.6.10 and Debian GNU/Linux 3.0r4 into /boot on a colo box currently (and temporarily) running CentOS. I''ve chrooted into the debian install (chroot /boot /bin/bash) and was able to set everything up, install requisite packages, install xen, etc. Now I''m at the last step and I''ve run into

Hallo, I am currently installing XEN on an ARM64 EFI machine. (Debian Testing), Therefore, I installed the following packages: __________________________________________________________________ root at armbox:/etc# dpkg -l "xen*" | awk '/^ii/ {print $2 "\t\t" $3}' xen-hypervisor-4.6-arm64 4.6.0-1+nmu2 xenstore-utils 4.6.0-1+nmu2 root at

Hello Xen folks, I use Debian Squeeze. I want to passthrough PCI devices. With the old stable Debian (grub legacy) i did not have problems. I edit /etc/default/grub like: quote: GRUB_CMDLINE_XEN_DEFAULT="quiet xen-pciback.permissive xen-pciback.hide=(00:14.2)(01:05.1)" I run "update-grub". Now i look at /boot/grub/grub.cfg: ### BEGIN /etc/grub.d/20_linux_xen

Hi All, Now that we have multiboot capable pxelinux, thanks to mboot.c32, I decided to try and remove pxegrub from my x86 jumpstart infrastructure since, in theory, pxelinux can now do it all. The problem I'm having is I'm not very sure I'm following Tim's documentation correctly... I'm not 100% what comes after the --- and whether the Sun kernel needs it's arguments

The program segments loaded presently in mboot.c only consists of a subset of sections described by the ELF Section Header Table (SHT) in the ELF kernel binary. Segments with useful information often needed for debugging purposes (symbol tables, string tables, etc.) aren't usually present in the program segments and hence not loaded above. Some kernels use this debugging information to

Add a couple of documentation details about PV-GRUB support - the menu.lst content can be passed as a ramdisk. - virtual partitions are not supported. Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> diff -r b8d2a4134a68 stubdom/README --- a/stubdom/README Wed Mar 03 17:41:58 2010 +0000 +++ b/stubdom/README Wed Mar 03 20:42:53 2010 +0100 @@ -52,11 +52,17 @@ extra =

I''m trying to install xen-3.0.4 from source on a debian sarge (3.1r4) box with dual AMD-64 processors (with the new HVM support, although I don''t think that''s got anything to do with the problem). I installed only the packages necessary to compile xen and its kernel(gcc, make, bzip2, bridge-utils, etc). In the source directory, I ran ''make world &&

Hi, I want to slowly migrate from Debian to CentOS, so I setup a multiboot on my main machine. There's a Debian Etch install on /dev/hda, and GRUB is also installed on the Debian side. On /dev/hdb, I have CentOS 5. I fdisked the drive manually, then chose manual partitioning during install. The setup for CentOS is: hdb1 -> swap hdb2 -> /boot, ext2 hdb3 -> / , ext3 After

I have been trying to multiboot centos 4.1 and the current solaris express build 15. I have two hard drive s, the first one ( hd0 ) devoted to CentOS 4.1 and windows xp (no problems). The second drive (hd1) for Solaris 10 only. I tried to boot solaris from CentOS grub and got the following error messages: Booting Solaris 10 root(hd1,0) Filesystem type unknown, partition type 0Xbf kernel

Hey list, I recently started working with kickstart. It is awesome! I really had no idea how easy it would be to use. I do have one strange issue, that's really not that important, but that I'd like to figure out. I like to watch all the kernel boot messages go by in text mode by default, and when I've set up a box in the past, I've modified grub's menu.lst file to remove

doing that grub-install /dev/sda will give me the "corresponding BIOS device" error. But now I fixed it by doing a manual grub install. first boot with cd1 and type linux rescue at the prompt when you're at the linux prompt after detecting and mounting the partitions, do a "chroot /mnt/sysimage" then # grub --batch #grub> root (hd0,0) Filesystem type is ext2fs,

Hey, I built a 2.6.18.8-xen kernel and created the initial ram disk by following the instructions in README file in Xen source package. Then I put a entry for new kernel in /boot/grub/menu.lst (I am using CentOS 5). Here is the menu.lst: ########################################## default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-8.el5) root

From: Ralf Ertzinger <ralf at skytale.net> If a loaded kernel is in ELF format and contains a multiboot header indicating valid relocation information, prefer the informations from the ELF header. This is in violation of the Multiboot spec, but it's the way GRUB does things and Solaris kernels rely on this behaviour. Signed-of-by: Ralf Ertzinger <ralf at skytale.net> --- diff

I used to use multiple syslinux floppy images to implement what I call CD-ROM-multiboot (EL Torito supports up to 64 bootable images, Award BIOS 8 images, if not wrey old). Now that floppies are getting too small, I find that I must find a workaround for hard coded isolinux directory name in isolinux. Not a big deal, but there might be also others who would like to have multiboot feature. --

Hi Ian, can we push multiboot v2 support for Xen/ARM still into 4.3? It looks like it can coexists with zImage in the same binary - the multiboot structure can be put just behind the zImage header and the code can determine how it has been started: zImage bootloaders clears r0, multiboot one''s would set r0 to the MB magic. I will sketch a patch tomorrow, just wondering if we can have

Hi. Is it possible to integrate multiboot support, which was described by the nilo-project? I think grub support multiboot too. The reason for this feature request is, that it would be much easier to configure some modules to be loaded by pxelinux, than compiling a new full featured kernel. Also, if there are many different hosts, we would not need many different kernels (or one

On 8/5/2015 12:34 PM, Chris Murphy wrote: > On Wed, Aug 5, 2015 at 9:12 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> I am trying to upgrade my system from 500GB drives to 1TB. > I'm going to guess that there are no IDE drives that have 4096 byte > physical sectors, but it's worth confirming you don't have such a > drive because the current partition

Hi, some time ago I tried to boot an isolinux boot loader from another one to be able to boot e.g. a Knoppix CD with its original boot loader and menus from a "main" isolinux on a multiboot DVD. This works for isolinux <= 3.07 now! However, newer isolinux boot loaders have some problems and the isolinux (e.g. of the Knoppix CD) loaded from the multiboot DVD's main isolinux

On Wed, Aug 5, 2015 at 9:12 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: > I am trying to upgrade my system from 500GB drives to 1TB. I'm going to guess that there are no IDE drives that have 4096 byte physical sectors, but it's worth confirming you don't have such a drive because the current partition scheme you've posted would be sub-optimal if it does have 4096