|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] XEN 3.4.2 /proc/xen/balloon doesn't exist and grub2 tro
On Thu, Jan 28, 2010 at 03:01:27PM -0500, Gabor Szilagyi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Gabor Szilagyi wrote:
> > Pasi Kärkkäinen wrote:
> >> On Tue, Jan 26, 2010 at 11:49:43AM -0500, Gabor Szilagyi wrote:
> >>>>> So I am trying to make it myself.
> >>>>>
> >>>>> I have installed xen 3.4.2 from source, did make world and installed.
> >>>>>
> >>>>> Got the kernel source from from the git repository with the xen patches
> >>>>> following the xen wiki.... compiled dom0 kernel just fine.
> >>>>>
> >>>> So you're using pv_ops dom0 kernel?
> >>> Yes I am pretty sure.. I can boot it on the bare hardware not problem
> >>>
> >> Ok.
> >
> >>>>> I can boot xen, with grup (old something went odd with grub2 for me) and
> >>>>> then it boots my dom0 kernel fine.
> >>>>>
> >>>> For GRUB2 see:
> >>>> http://wiki.xensource.com/xenwiki/XenCommonProblems
> >>> Well, I have looked at this and went a head re-install Debian Squeeze
> >>> with grub2 ...
> >>>
> >>> Now, I can not even boot xen-3.4.2.gz which I built again from source....
> >>>
> >> Uhm.. what error do you get?
> >
> > I can copy from the console only the last few all line start with (XEN)
> > so I will not copy those
> >
> > Panic on CPU 0:
> > Cannot access memory beyond end of bootstrap direct-map area
> > ******************
> >
> > Reboot in five second
> > Early fatal page fault at e008:ff146c9 (cr2=fffde020,ec=0000
> > Stack dump ... and a whole bunch of numbers
> >
> >
> > I see this exact some other post
> >
> >> Can you set up a serial console to log the full boot process?
> > I could if I had the right cable.
> >> See:
> >> http://wiki.xensource.com/xenwiki/XenSerialConsole
>
> Hi Pasi,
>
> I got the null-modem and booted with the serial consol and here is the
> log.... hope you can suggest something...
>
> Press CTRL-A Z for help on special keys
>
>
>
> __ __ _____ _ _ ____
>
> \ \/ /___ _ __ |___ /| || | |___ \
>
> \ // _ \ '_ \ |_ \| || |_ __) |
>
> / \ __/ | | | ___) |__ _| / __/
>
> /_/\_\___|_| |_| |____(_) |_|(_)_____|
>
>
>
> (XEN) Xen version 3.4.2 (root@xxxxxxxxxxxx) (gcc version 4.3.4 (Debian
> 4.3.4-6) ) Mon Jan 25 16:28:40 EST 2010
> (XEN) Latest ChangeSet: unavailable
>
> (XEN) Console output is synchronous.
>
> (XEN) Command line: dummy=dummy dom0_mem=512M loglvl=all
> guest_loglvl=all sync_console console_to_ring com1=9600,8n1 console=com1
> (XEN) Video information:
>
> (XEN) VGA is text mode 80x25, font 8x16
>
> (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
>
> (XEN) Disc information:
>
> (XEN) Found 2 MBR signatures
>
> (XEN) Found 2 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN) 0000000000000000 - 000000000009d000 (usable)
> (XEN) 000000000009d000 - 00000000000a0000 (reserved)
> (XEN) 00000000000ce000 - 00000000000d4000 (reserved)
> (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 00000000d7f80000 (usable)
> (XEN) 00000000d7f80000 - 00000000d7f98000 (ACPI data)
> (XEN) 00000000d7f98000 - 00000000d7fbc000 (ACPI NVS)
> (XEN) 00000000d7fbc000 - 00000000e0000000 (reserved)
> (XEN) 00000000f8000000 - 00000000fc000000 (reserved)
> (XEN) 00000000fec00000 - 00000000fec10000 (reserved)
> (XEN) 00000000fee00000 - 00000000fee01000 (reserved)
> (XEN) 00000000ff000000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 00000001fe000000 (usable)
> (XEN) 00000001fe000000 - 0000000200000000 (reserved)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Cannot access memory beyond end of bootstrap direct-map area
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
> (XEN) Unknown interrupt (cr2=00000000)
> (XEN) ff202ec4 a1e00000 00000002 ff22be54 00000086 00000002
> ff1d68dc 00000000 ff14e687 0000e008 00000286 ff1d67c0 0000000a
> ff1c5146 ff22b0
>
>
>
> This is consistent the xen image I compiled on the same machine but I
> can do that again... tried to make an X83_32_pae for the same type of
> kernel would like to be able to use pv_ops and hvm domU as well (but at
> least boot xen :-)
>
This is not about dom0 kernel, since it's the Xen hypervisor that crashes here.
-- Pasi
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|