On Feb 7, 2007, at 5:41 PM, Jerone Young wrote:
On Wed, 2007-02-07 at 17:37 -0500, Jimi Xenidis wrote:
On Feb 7, 2007, at 12:48 PM, Jerone Young wrote:
OK all is well...no fire here...move along. I figured out what
happened.
I included the vmlinux as the DOM0_IMAGE and not the zImage. It
com
On Wed, 2007-02-07 at 17:37 -0500, Jimi Xenidis wrote:
> On Feb 7, 2007, at 12:48 PM, Jerone Young wrote:
>
> > OK all is well...no fire here...move along. I figured out what
> > happened.
> > I included the vmlinux as the DOM0_IMAGE and not the zImage. It
> > compiled
> > through .. it is a b
On Feb 7, 2007, at 12:48 PM, Jerone Young wrote:
OK all is well...no fire here...move along. I figured out what
happened.
I included the vmlinux as the DOM0_IMAGE and not the zImage. It
compiled
through .. it is a bit surprising the Xen died though and not during
loading of Dom0. So ultimat
OK all is well...no fire here...move along. I figured out what happened.
I included the vmlinux as the DOM0_IMAGE and not the zImage. It compiled
through .. it is a bit surprising the Xen died though and not during
loading of Dom0. So ultimately this is a USER error ;-)
On Tue, 2007-02-06 at 17:58
Last time we saw this it had to do with building optimized and the
linker script simplification I attempted, so we were actually missing
bits.
before you do anything, try a clean build.
Another possibility is some corruption, you may want to debug what
the boot_of_allocator is reserving.
So cloning the Xen tree as of today .. you can no longer bootup Xen :-).
Here is the output on a JS21
The currently active flashside is: 1 (temporary)
Stopping BMC watchdog...
Trying to load: sync_console debug || root=/dev/sda3 debug from:
net ...
Bootloader 1.5
Reading MAC address from dev
