similar to: how to pxeboot dom0?

hi, i´m using fedora core 6 and want to build xen 3.1 from source for the 2.6.20 kernel. how can i build xen with the existing kernel-config from /boot (e.g. config-2.6.20-1.2948.fc6xen) and an installed kernel-devel (source) package? is it good to use this config or should i create a new one? i searched the net and haven´t found any howto to build xen from source with newer kernel versions and

Hi all, I'm trying to get a pxeboot server up and running, according to the instructions on the WIKI (http://wiki.centos.org/HowTos/PXE/PXE_Setup & http://wiki.centos.org/HowTos/PXE/PXE_Setup/Menus) Here's my /tftpboot/pxepxelinux.cfg/default : default menu.c32 prompt 1 timeout 300 ONTIMEOUT local MENU TITLE PXE Menu label Dos Bootdisk MENU LABEL ^Dos bootdisk

Attempting to PXE boot from the BaseOS/x86_64/kickstart/images/pxeboot/ files results in repeating messages Invalid or corrupt kernel image eventually changing to Could not find kernel image: centos8.2.x86_64/vmlinuz I downloaded the files again, from a different mirror, and they are all the same. Wiped the files and recreated /tftpboot/linux-install/centos8.2.x86_64/. No dice. First mirror

Hello, I hope this doesn't bounce again... I'm having trouble passing control of the PXE process from PXELINUX to the FreeBSD "pxeboot" program. I tried invoking "pxeboot" from the PXELINUX "boot:" prompt. This causes an error "Invalid or corrupt kernel image." I named pxeboot "pxeboot.0" and tried invoking pxeboot.0 from the

Hi all, I've searched the depths of the resources on the internet; however I'm having trouble deploying a pxeboot solution via pxelinux. So far what I have successfully implemented in my infrastructure is a successful pxeboot setup for FreeBSD ( without the use of pxelinux ). I'd ultimately like to have a solution that will allow me to choose a network install of various Unix-like

Hi Folks, I have configured pxelinux.0 to allow chain-booting freebsd pxeboot.0 from it like this: label fbsdpxe KERNEL pxeboot.0 This works as expected, so no issue with that. There's one weird thing however. If I rename pxeboot.0 to pxeboot (omitting .0) and change the config file accordingly it throws this error at me: Invalid or corrupt kernel image. Same happens if I

Hello... In the split-second before the reboot, I can see that the pxeboot.0 process is indeed started-- pxeboot gets out just over 2 lines of text before the reboot occurs. So it's not a "ready" message. The text in question is (without *'s): ****************************************** PXE Loader 1.00 Building the boot loader arguments Relocating the loader and the

Has anyone succeeded in installing CentOS-6.0 by PXEboot. If so, would you say how you did it, please. I tried (on an HP MicroServer), but gave up in the end and used a USB stick installation instead. But I'd be very interested to know how to do it, for the future. Unfortunately I didn't keep a proper note of my PXEboot attempt, but IIRC the problem was that install.img was not found,

I am using pxeboot (syslinux) 1.75 and I'm attempting to boot diskless with the pxeboot.0 system. The system boots, downloads the pxeboot.0, the kernel and then the screen turns to garbage. Does anyone know what this is/how to fix this? Thanks. -- Paul Slinski System Administrator Global IQX http://www.globaliqx.com/ pauls at globaliqx.com

hello, sorry that I post it here again, as I have already posted it on www.redhat.com/archives/fedora-xen/. Now I am working on fedora6Xen,i.e. 2.6.20-1.2944.fc6xen .Several questions: 1. After I have installed the windowsXP, the XP OS of course needs to reboot, but then the WindowsXP is automatically closed. How can I restart it? And I use #virsh start , the domain will be running, but when I

Hi again... The text under "BTX loader..." should appear as a block where each line is 56 characters long. "BTX halted" is on its own line. Apologies for my mailer... -Chris -----Original Message----- From: McMahon, Chris Sent: Wednesday, November 19, 2003 8:32 AM To: 'H. Peter Anvin'; McMahon, Chris Cc: 'syslinux at zytor.com'; 'mike at

latest pxeboot (7.1): mother-board NIC/LOM CPU ------------- ------- --- Intel SWV25 em xeon works fine SUN X2200 bge amd works fine DELL PE 2950 bce xeon failes 95% of the times hangs or goes into btx dump regs. mode :-) Intel SE7320VP21 msk xeon failes 50% of the times - hangs pxeboot with btx.S 1.45 2008/02/27 23:35:39, works fine. so it seems that changes since 1.45 have

I am having a problem with setting up diskless clients under CentOS 5.2. I have everything working under CentOS 4.7. This is an adaptation of the (somewhat old) Diskless Linux with PXE HOWTO by Gerd v. Egidy, originally at the URL http://www.intra2net.com/opensource/diskless-howto/, which is now defunt (there is a mirror of it at http://blog.chinaunix.net/u/2389/showart_82438.html). What I am

Hi, folks, We've been using pxeboot to pull up a menu, to build or rebuild machines for years. We have this new server, and it fails. Times out. What's happening is that it tries in this order .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d .../pxelinux.cfg/01-88-99-aa-bb-cc-dd .../pxelinux.cfg/C0A8025B .../pxelinux.cfg/C0A8025 .../pxelinux.cfg/C0A802

Hey CentOS list! I've got an oddity with a diskless client setup that I suspect is the result of the initrd.img I'm using, or some parameter I'm unaware -- or I need to build my own initrd image (and could use some assistance on what has to be done in that department) Testbed is defined as: VM A: ip: 192.168.250.10 with dhcp server, tftp server, nfs server VM B: pxeboot VM,

Well, I started the install, got pxeboot to get to the kickstart file, formatted the drive... and then it failed, telling me "unable to read group information from repositories. This is a problem with the generation of your install tree." A quick google gives me the first hit from a year ago, bug 4372 <http://bugs.centos.org/view.php?id=4372>, which says there's a metadata

Hi, I am trying to create an image that is larger than 1.44MB to be used with PXE boot (Ghost 8 requires 2 floppys). My current attempts result in the boot hanging at : Loading boot sector... booting... Starting... My config just says the following: default memdisk append initrd=smalldos.img I created the image following http://syslinux.zytor.com/archives/2005-August/005573.html (I am unsure

Digging into this, as we rework it, here's a question: assuming the system being pxebooted is server 1, and the tftp server is server 2, on server 2, in the menu for pxeboot, is there any way to specify that the image to boot, and the initrd, are on a server 3? That is, MENU repoboot KERNEL repo://my/repo/images/vmlinuz APPEND repo://my/repo/images/initrd.img (or an IP address, like

I tried to test Asterisk 1.4 on FC6 x86_64. I have it working on FC5 x86_64 very good, but since FC keeps updating, I tried to follow newer kernel versions. I can't pass the zaptel compilation. Everything is OK, but when I finished, and tried to load it, allways got module not found when I run modprobe zaptel, and modprobe ztdummy. I already tried to modify is with the sed 1 option but

Does anyone have a howto or documentation on how to add new drivers to the pxeboot initrd/kernel? It appears that although some newer dells (t300) have Broadcom NetXtreme IIs in them, 4.6 won't recognize them for some reason (possibly because they're dual port?) -Drew -------------- next part -------------- An HTML attachment was scrubbed... URL: