similar to: "Old method" bootloader failing with large ramdisk

This is a proposal for modifying the interface for domU bootloaders (i.e. something that provides us with a kernel and ramdisk file with which the domain can be booted). The current interface, as is, has a number of problems, including: 1) the first disk specified is assumed to be the disk containing the files 2) ''bootentry'' is highly pygrub-specific. There is no easy facility

Had to changed the Subject header because the mailing list software thought the previous one ("so old bootloader" ...) was suspicious. Just a backgrounder and a little more info I've gathered: Trying to install Fedora Core 3 via PXE using DHCP-TFTP. Kernel loads but initrd isn't used for rootfs. The machine's an AMD Athlon 64-based box with 512MB physical memory (one DDR

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1337273492 -3600 # Node ID cdb947baea102aa6a1d53472f8a3e5f2d6cc485e # Parent ac45608496cd85b0bf1aed6e5b869b4a86ca672f libxl: do not overwrite user supplied config when running bootloader. Currently when running the bootloader libxl will update b_info->u.pv.kernel, .ramdisk, .cmdline and .bootloader. This can

I am running Xen 3.0 (64bit) on CentOS 5.3, and I want to install Ubuntu 10.04 using the steps below: 1. Create a new disk with LVM 2. Downlaod vmlinuz & initrd.gz from http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/ 3. /usr/sbin/xm create -c /etc/xen/ubuntu.cfg install=true 4. Format the whole disk as EXT3, mount as / 5. The installer show some

Hi, I was wondering whether it is technically possible to go back from eg. DOS or Linux directly to the bootloader (instead of rebooting the hardware). We currently have 2 images (one DOS and one Linux) that need to be started before loading a system. They do things like disable PXE on NICs (using an Intel DOS tool), verify the correctness of the network patchings and validate if the

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

Hi, I'm trying to install Fedora Core 3 on an AMD 64-based machine using PXE (via DHCP and TFTP). I've managed to get the machine to load the kernel over the network and start booting, but instead of loading the root fs from initrd.img (that I appended as a config via pxelinux.cfg), it loads the pre-existing rootfs on my harddisk. At the top of dmesg is the message: "so old

(Moving from offlist discussion.) I''m interested in opinions... Assume there are four single vcpu domains A, B, C, D, running on a 2-CPU physical machine. We wish to test for time skew on domain A. Assuming B, C, and D are all running some workload that attempts to fully saturate the (single) cpu. 1) Should the affect on domain A be essentially the same regardless of what load

Folks, The second release candidate for Xen 3.4.0 is available at http://xenbits.xensource.com/xen-unstable.hg, tagged as ''3.4.0-rc2''. Please test! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hullo Everybody ; I am failing to start my new VM and it tells me unkown bootloader . Below are my parameters and output . Could somebody be having an idea of putting right this problem? [root@virtualintranet /]# xe vm-param-list uuid=70645ba3-bcbc-683b-099e-ed197301fcc2 uuid ( RO) : 70645ba3-bcbc-683b-099e-ed197301fcc2 name-label ( RW): PVG1

Fix for pygrub path on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py +++ b/tools/python/xen/xend/XendDomainInfo.py @@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_ from xen.util.blkif import blkdev_uname_to_file from xen.util

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub

Hi I am having some problems installing a paravirt RHEL guest on a deb amd64 xen machine uname -a = Linux debxen 2.6.20-1-xen-amd64 #1 SMP Tue Apr 24 22:23:22 UTC 2007 x86_64 GNU/Linux ============== xm info ============== host : debxen release : 2.6.20-1-xen-amd64 version : #1 SMP Tue Apr 24 22:23:22 UTC 2007 machine : x86_64

Hi! Some bootloaders (eg. syslinux) have to ability to load multiple ramdisks, effectively concatenating them. This makes it very easy to augment ramdisks, like eg. customizing an installer. Can I do something similar with XEN? Separating the ramdisk cpio arhives with commas in the config file didn''t work... -- Thanks, Feri. _______________________________________________ Xen-users

Hello, I have a problem with a 2.5.62 kernel and ramdisk. I am using isolinux to create a cd that loads some of its partition in ramdisk. The script involves mounting a ramdisk (e2fs) on /fake/ramdisk, copying part of the cd to that mount point, unmounting it, and remounting it on /fake/needwrite. The problem is that, although the content of /fake/needwrite gets correctly copied, the content of

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1346945306 -7200 # Node ID 8a2eef481d3ab3ca5692dd0083c95cf314fe1da3 # Parent 19d367bf07b7687b831c212a57a70e73ea14d3b7 pygrub: always append --args If a bootloader entry in menu.lst has no additional kernel command line options listed and the domU.cfg has ''bootargs="--args=something"'' the additional

Greetings! Trying to to run a xen3 domU on a xen4 dem0 I run into problems. The xen server ''XEN1''(dom0) is openSUSE-11.3 (kernel 2.6.34) and xen-4.0.1. With qemu I created an image ''M08.raw'' from the SUSE-9.3 (kernel 2.6.11) and XEN-3.0 installation CD''s. The XEN modules were included in the installation. In M08.raw/boot I configured grub/menu.lst:

Hi, I have a Xen server running OpenSuSE 10.2, with Xen version 3.0.3_11774. It''s happily hosting two DomU''s running the same OS / kernel. Now I tried to create a new DomU running a newer OS - OpenSuSE 11.1. It comes with Xen version 3.3.1_18494_03. Unfortunately for me, it doesn''t work - this is what I get: > xen1:/etc/xen/vm # xm create NEW > Using config file

This patch (against unstable) makes sure that the skel/etc/init.d/rcS file is executable before building the final ramdisk image. This should fix the problem some people are having with their ramdisk builds. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com _______________________________________________ Xen-devel mailing list