On Aug 9, 2011, at 11:04 PM, Kevin O'Connor wrote:

On Tue, Aug 09, 2011 at 02:32:02PM -0400, John Paul Walters wrote:

You're hitting a weird interaction with the mptable - its allocation
just barely fits, and since it takes up all the ram in the f-segment
it causes other allocations to fail (which are needed to hold info on
the boot drive).

This should no longer be an issue in the latest SeaBIOS from git.
Alternatively, if you increase the number of CPUs, you should see the
machine boot becuase only the mptable allocation will fail.


Thanks Kevin.  I updated SeaBIOS and I'm able to boot the VM now.

JP