search for: mbootpack

Hello Xen-Users, I am running a Debian GNU/Linux Devel-Station (P2/366 MHz, 512MByte) and use currently chroots which give some problems from time to time. I have following configuration: ----8<------------------------------------------------------------------ /dev/sda1 / 7700 GByte # Master System /dev/sda2 swap 256 MByte # Master System /dev/sda3 /var 512 MByte # Master System

I''ve now given up trying to get grub working with my particular e1000 adapter, I''ve tried all the patches and all I can get is something that works a little bit but never past the grub menu. I''m sure I read something somewhere about a tool which would combine a multiboot image + modules into a single bootable item which could be loaded by lilo, and am hoping that the

Hi: we have following setup: 1. 2.6.16-33-based Xen 3.0.3/Xen-3.0.4 DOM-0 kernels. 2. Using LILO-mbootpack from USB we boot Xen-->DOM-0 setup 3. We mount harddisk and try to install xp.hvm While,we are successful with FCs as DOM-U, for XP we get, VBD (768) could not be connected. We do have max_loop count to 64 and enough loop devices. Note that above error is consistent on both 3.0.3 and 3.0.4...

..., 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 which works for me [tm] and I''d be very interested in feedback from other people who want to PXE-boot Xen. Assuming you already have dhcp/tftp up and working at your site, it should be easy to test: 1) Edit dh...

Hi,   I am trying to build dom0 iso. I have following in my isolinux.cfg file. I see error: "Invalid or corrupt image file".   --- default 1 prompt 1 timeout 300 display menu.txt label 1   kernel boot/vmlinuz.vm   append boot/xen.gz  ramdisk_size=131072 initrd=boot/ramdisk.gz root=/dev/ram0 ---   The image I check is valid. xen.gz is actually xen-3.4.2.gz: xen.gz: gzip compressed data,

Hi All: I found this old message on the web archives. I've gotten Xen working with PXELinux, albeit with something of a hack. The basic chain is: 1. pxelinux 2. memdisk 3. FAT16 floppy image 4. grub installed on floppy image 5. xen.gz and vmlinuz on floppy image While this seems pretty simple, the key bits were to use: 1. FAT16 (not ext2, etc) for the floppy image 2. use the 'raw'

Hi, 1.) Is it possible to link the xen-kernel (xen.gz) into the dom0-kernel in order to have only one kernel binary to handle? 2.) The xen-patch drops make targets like bzImage, ... This breaks kernel configuring-/installing-scripts like Gentoo''s genkernel. It would be great to keep the standard targets or modify them. Thanx Rene _______________________________________________

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *