|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] dom0 won't boot
>[Transcribed]
>(XEN) *** LOADING DOMAIN 0 ***
>(XEN) Xen-ELF header found:
>'GUEST_OS=linux,GUEST_VER=2.4,XEN_VER=1.3,VIRT_BASE=0xC0000000'
>(XEN) PHYSICAL MEMORY ARRANGEMENT:
>(XEN) Kernel image: 02800000->02b0b8fc
>(XEN) Initrd image: 00000000->00000000
>(XEN) Dom0 alloc.: 02c00000->0ac00000
>(XEN) VIRTUAL MEMORY ARRANGEMENT:
>(XEN) Loaded kernel: c0100000->c0458988
>(XEN) Init. ramdisk: c0459000->c0459000
>(XEN) Phys-Mach map: c0459000->c0479000
>(XEN) Page tables: c0479000->c047c000
>(XEN) Start Info: c047c000->c047d000
>(XEN) Boot stack: c047d000->c047e000
>(XEN) TOTAL: c00000000->c0800000
>(XEN) ENTRY ADDRESS: c0100000
>(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to swith input to
>Xen).
>[long pause.]
>(XEN) Domain 0 shutdown: rebooting machine!
>(XEN) Reboot disabled on cmdline: require manual reset
>
>Can I assume from the above that it had located the kernel and loaded it?
What's your [xen]linux command line? You're not getting any start of
day messages from dom0 which may mean that the console is set up incorrectly.
The less likely alternative is that something is going wrong (and taking a
long time to do so) before the first message that should be output from
dom0...
>> First, make sure your xen and vmlinuz-xen images are built from
>> the same repo version.
>
>This was a fresh bk clone on a new install -- what do you mean by "repo"?
"repo" is short for the bk repository which you're using; if you're using
a fresh clone you're probably up to date. The above comment was just
stressing that it's important that the xen and xenlinux images are in
sync (built from the same version), particularly with unstable.
cheers,
S.
|
|
|
|
|