[ipxe-devel] In order to ooting ESXi mboot.c32 from ipxe enable IMAGE_COMBOOT in general/config.h

Brandon Penglase bpenglase-ipxe at Spaceservices.net
Sun Sep 9 22:17:55 UTC 2012

I did find after you left IRC, that there is another option in the
boot.cfg that VMWare provides:
So, confirming with Robin, I tried the following:
kernel tboot runweasel
However, on my VM, it still just sits, and on my physical machine, it
reboots after a few seconds. 
If I uncompress the files, as we were talking about, my VM throws a
"the OS disabled the CPU" error...
So, as of right now, I still do not have it working, but I figured I
would let you know about the 'runweasel' kernel option, so maybe you
might have some better luck.

	Brandon Penglase

On Sun, 9 Sep 2012 16:57:32 +0200
Thomas Glanzmann <thomas at glanzmann.de> wrote:

> Hello Brandon,
> > I decided to try this out to see if I could get the same thing.
> > Working with Michael and Robin in IRC, we actually were finding
> > things about the same time you were. Once I uncompressed the
> > tboot.b00, and renamed it back to what it was, it then found it as
> > a Multiboot image. 
> I did the same thing.
> > I then ran into another issue, where the number of multiboot modules
> > is limited to 8. You can change this in arch/i386/image/multiboot.c
> > (line 55), and see the comment there on why it is set as such.  I
> > raised mine to 70 (little bit higher then the full amount of
> > modules). Using the options that Robin provided earlier (with 9
> > modules), and DEBUG=multiboot, I get the following:
> > http://node4.smart-serv.net/~brandon/mboot-debug2.png
> I increased the number of modules, recompiled and I'm getting a
> reboot. That looks like a double page fault.
> Now the question is, is that related to the tboot.b00 or to the ipxe
> version. I think, I'll retry with an older ESX version and see if that
> boots.
> Cheers,
>         Thomas

More information about the ipxe-devel mailing list