how big an image downloaded and booted by gPXE could be?
Luca <[email protected]> Wed, 9 Dec 2009 08:28:10 -0800
| Newsgroups | gmane.network.etherboot.user |
|---|---|
| Message-ID | <[email protected]> |
Hi all, I have a system with 8G of RAM. When I try to download and boot with gPXE an image whose size is around 4G, gPXE gets stuck after downloading it. Is there any limitation with gPXE on how big the downloaded image could be? Thanks. Here is a more detailed description of what I'm trying to do. I have two identical systems (each with 8G of RAM). I installed Fedora 11 on one of this. I made a copy of the HD (let's call it rootfs.img) and created a initial ramdisk containing this rootfs.img. This init file in initial ramdisk at a certain point switch root, mounting rootfs.img. The size of this ramdisk is 4G (let's call it ramdisk.img). I wanted to use gPXE to download the kernel and ramdisk.img and boot it. So I have gPXE downloading the following gPXE script #!gpxe kernel https://192.168.1.189/vmlinuz root=/dev/ram0 init=linuxrc ramdisk_size=4000000 ramdisk_blocksize=1024 initrd https://192.168.1.189/ramdisk.img boot gPXE downloads the script and the the kernel and the initrd, but then it gets stuck (don't think the kernel is started by gPXE, don't even see the message "Probing EDD ... or anything else). Only message I see, is the one telling me gPXE is done downloading both kernel and ramdisk.img. Thanks, Luca ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Etherboot-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/etherboot-discuss