Thank you. So gPXE can address 4GB of RAM.<br><br>Then, if I gPXE boot with the following script<br><br>#!gpxe<br>
<br>
kernel <a href="https://192.168.1.189/vmlinuz" target="_blank">https://192.168.1.189/vmlinuz</a> root=/dev/ram0 init=linuxrc<br>
initrd <a href="https://192.168.1.189/ramdisk.img" target="_blank">https://192.168.1.189/ramdisk.img</a><br>
boot<br><br>the ramdisk's size could not exceed 2G (considering gPXE has to download it and then load it in memory)? <br><br>Thank you, <br> Luca<br><br><div class="gmail_quote">On Wed, Dec 9, 2009 at 9:09 AM, Thomas Miletich <span dir="ltr"><<a href="mailto:thomas.miletich@gmail.com">thomas.miletich@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
As gPXE doesn't run in long mode it can only address 4GB of RAM(that's<br>
the maximum for 32 bit).<br>
You could however boot a 64 bit linux kernel, and let the initrd fetch<br>
the rootfs to a 4GB ramdisk.<br>
How you can accomplish this is probably specific to the distribution you use.<br>
<br>
There is also a 64 bit version of gPXE for EFI booted systems. EFI<br>
isn't supported widely yet, so I don't know if you can use it. I'm<br>
also unsure whether this version of gPXE allows larger images or has<br>
the same limits.<br>
<br>
Thomas<br>
<div><div></div><div class="h5"><br>
On Wed, Dec 9, 2009 at 5:28 PM, Luca <<a href="mailto:lucarx76@gmail.com">lucarx76@gmail.com</a>> wrote:<br>
> Hi all,<br>
> I have a system with 8G of RAM. When I try to download and boot with gPXE<br>
> an image whose size is around 4G, gPXE gets stuck after downloading it. Is<br>
> there any limitation with gPXE on how big the downloaded image could be?<br>
> Thanks.<br>
><br>
> Here is a more detailed description of what I'm trying to do.<br>
> I have two identical systems (each with 8G of RAM).<br>
> I installed Fedora 11 on one of this. I made a copy of the HD (let's call it<br>
> rootfs.img) and created a initial ramdisk containing this rootfs.img. This<br>
> init file in initial ramdisk at a certain point switch root, mounting<br>
> rootfs.img. The size of this ramdisk is 4G (let's call it ramdisk.img).<br>
><br>
> I wanted to use gPXE to download the kernel and ramdisk.img and boot it.<br>
><br>
> So I have gPXE downloading the following gPXE script<br>
> #!gpxe<br>
><br>
> kernel <a href="https://192.168.1.189/vmlinuz" target="_blank">https://192.168.1.189/vmlinuz</a> root=/dev/ram0 init=linuxrc<br>
> ramdisk_size=4000000 ramdisk_blocksize=1024<br>
> initrd <a href="https://192.168.1.189/ramdisk.img" target="_blank">https://192.168.1.189/ramdisk.img</a><br>
> boot<br>
><br>
> gPXE downloads the script and the the kernel and the initrd, but then it<br>
> gets stuck (don't think the kernel is started by gPXE, don't even see the<br>
> message "Probing EDD ... or anything else). Only message I see, is the one<br>
> telling me gPXE is done downloading both kernel and ramdisk.img.<br>
><br>
> Thanks,<br>
> Luca<br>
><br>
</div></div>> ------------------------------------------------------------------------------<br>
> Return on Information:<br>
> Google Enterprise Search pays you back<br>
> Get the facts.<br>
> <a href="http://p.sf.net/sfu/google-dev2dev" target="_blank">http://p.sf.net/sfu/google-dev2dev</a><br>
><br>
> _______________________________________________<br>
> Etherboot-discuss mailing list<br>
> <a href="mailto:Etherboot-discuss@lists.sourceforge.net">Etherboot-discuss@lists.sourceforge.net</a><br>
> <a href="https://lists.sourceforge.net/lists/listinfo/etherboot-discuss" target="_blank">https://lists.sourceforge.net/lists/listinfo/etherboot-discuss</a><br>
><br>
><br>
</blockquote></div><br>