xen-devel
Re: [Xen-users] Xen 3.4.2 hypervisor crash, Cannot access memory beyond
To: |
Gabor Szilagyi <szilagyi@xxxxxxxxxxxx> |
Subject: |
Re: [Xen-users] Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt |
From: |
Pasi Kärkkäinen <pasik@xxxxxx> |
Date: |
Thu, 28 Jan 2010 23:16:16 +0200 |
Cc: |
Martin Kraus <lists_mk@xxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>, Thiago Camargo Martins Cordeiro <thiagocmartinsc@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> |
Delivery-date: |
Thu, 28 Jan 2010 13:17:37 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<4B61F7D8.5050604@xxxxxxxxxxxx> |
List-help: |
<mailto:xen-users-request@lists.xensource.com?subject=help> |
List-id: |
Xen user discussion <xen-users.lists.xensource.com> |
List-post: |
<mailto:xen-users@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe> |
References: |
<20100126155046.GD6085@finrod> <6b7f6eb1001261134sf59257ag8335a2189565eb71@xxxxxxxxxxxxxx> <20100127104417.GA2346@finrod> <4B60507E.6080705@xxxxxxxxxxxx> <20100127202649.GU2861@xxxxxxxxxxx> <4B61B746.8050207@xxxxxxxxxxxx> <20100128162610.GR2861@xxxxxxxxxxx> <4B61ECC9.1090404@xxxxxxxxxxxx> <20100128200240.GA2861@xxxxxxxxxxx> <4B61F7D8.5050604@xxxxxxxxxxxx> |
Sender: |
xen-users-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
CCing to xen-devel and Keir.
Keir: Have you seen this Xen hypervisor crash earlier? serial log below..
-- Pasi
On Thu, Jan 28, 2010 at 03:47:20PM -0500, Gabor Szilagyi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Pasi Kärkkäinen wrote:
> > On Thu, Jan 28, 2010 at 03:00:09PM -0500, Gabor Szilagyi wrote:
> > Pasi Kärkkäinen wrote:
> >>>> On Thu, Jan 28, 2010 at 11:11:50AM -0500, Gabor Szilagyi wrote:
> >>>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>>> Hash: SHA1
> >>>>>
> >>>>> Pasi Kärkkäinen wrote:
> >>>>>> On Wed, Jan 27, 2010 at 09:41:02AM -0500, Gabor Szilagyi wrote:
> >>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>>>>> Hash: SHA1
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Martin Kraus wrote:
> >>>>>>>> On Tue, Jan 26, 2010 at 05:34:59PM -0200, Thiago Camargo Martins
> >>>>>>>> Cordeiro wrote:
> >>>>>>>>> Hi!
> >>>>>>>>>
> >>>>>>>>> 1- Get the ISO of the Debian Lenny 5.0 amd64 from http://debian.org;
> >>>>>>>>> 2- Install your Debian into your own partition scheme (LVM over
> >>>>>>>>> RAID);
> >>>>>>>>> 3- Reboot into your new fresh Debian Lenny; upgrade it;
> >>>>>>>>> 4- * GRUB1 is still the default in Lenny, verify it;
> >>>>>>>>> 5- Install the Xen with the command: "aptitude install
> >>>>>>>>> xen-linux-system-2.6.26-2-xen-amd64";
> >>>>>>>>> 6- Reboot into you new dom0.
> >>>>>>>> Thanks for the effort but how does this solve the problem that xen
> >>>>>>>> doesn't
> >>>>>>>> start? I'm already running virtual hosts on that machine and I can't
> >>>>>>>> rip
> >>>>>>>> all of this apart just to get stuck with unbootable system again.
> >>>>>>>>
> >>>>>>>> What I need is to find out what the problem is and then start
> >>>>>>>> ripping stuff
> >>>>>>>> apart. I've tried to compile xen myself, versions 3.2, 3.3, 3.4, hg
> >>>>>>>> tip, all
> >>>>>>>> get stuck at some time during xen boot. Until I've tried the live
> >>>>>>>> cd, I
> >>>>>>>> thought that it's some incompatibility with my hardware but since
> >>>>>>>> the live cd is
> >>>>>>>> debian lenny on iso and it works fine, I have to look for the part
> >>>>>>>> that causes
> >>>>>>>> xen to freeze.
> >>>>>>>>
> >>>>>>>> Since there is only bios, grub and xen running in turn before the
> >>>>>>>> machine
> >>>>>>>> gets stuck I'd say that the problem is in one of these systems.
> >>>>>>>>
> >>>>>>>> I'll try to find out something about grub and then I'm going after
> >>>>>>>> kvm before
> >>>>>>>> I decide to scratch the whole machine.
> >>>>>>> Hi Martin,
> >>>>>>>
> >>>>>>> I am having the same problem ... ever since I installed grub2 I can
> >>>>>>> not
> >>>>>>> get xen to boot. I was told it is possible but yet to see someone
> >>>>>>> writing it down how. Tried the "new" syntax, put dummy=dummy as first
> >>>>>>> cmd line argument, even compiled the root=/... in the kernel nothing
> >>>>>>> works.
> >>>>>>>
> >>>>>>> I just get Panic on CPU 0 ... and stuck dump.
> >>>>>>>
> >>>>>> Please see:
> >>>>>> http://wiki.xensource.com/xenwiki/XenCommonProblems
> >>>>>>
> >>>>>> section:
> >>>>>> "Booting Xen with GRUB2 fails?"
> >>>>> Thanks for the tip ... I tried all those no change :
> >>>>>
> >>>>> here what I have currently in gurb.cfg both recommendation is use the
> >>>>> file name twice and use dummy=dummy
> >>>> No, you don't use both of them.
> >>>>
> >>>> The problem is that grub2 destroys the *first* parameter,
> >>>> so if you add the filename twice, that already is the extra
> >>>> first parameter, so no need for dummy anymore.
> >>>>
> >>>> Or then don't add the filename, but use dummy.
> >>>> You just need *one* extra parameter there, as the first parameter.
> >>>>
> >>>> See the working example from here:
> >>>> http://old.nabble.com/Strange-interaction-from-grub2-and-XEN-td26464067.html
> >>>>
> >>>>
> >>>>> I am trying both the newest patched kernel and the stuck kernel coming
> >>>>> with 3.4.2 source ... both compile without error (I pretty sure I got
> >>>>> the config right for xen). Actually I can boot the 2.6.31.6-xen-2 on
> >>>>> bare metal (strangely not the 2.6.18.8 !!)
> >>>>>
> >>>> xenlinux kernels (2.6.18.8) don't support running as baremetal.
> >>>> pv_ops Xen kernel do support that.
> >>>>
> >>>>> But got the same error ... so I strongly believe that the xen-3.4.2.gz
> >>>>> part crashes already with grub2 ..
> >>>>>
> >>>>> I tried several other combination from grub> prompt pretty much the same
> >>>>> CPU 0 panic and the numbers after (sometime sligthly different dump )
> >>>>>
> >>>> We really need to see the full console output to say what's wrong.
> > Pasi, Sorry for the crossposting I put this in my original thread as
> > well but maybe helpful here..
> >
> >
> >> Ok.. Hmm.. weird crash. Try removing "sync_console console_to_ring" from
> >> the xen options.
> >
> >> Does that make a difference?
>
> No unfortunately no difference: (note that I did make clean make
> install-xen) just to make sure it compiled right ... but the crash is
> identical...
>
> __ __ _____ _ _ ____
> \ \/ /___ _ __ |___ /| || | |___ \
> \ // _ \ '_ \ |_ \| || |_ __) |
> / \ __/ | | | ___) |__ _| / __/
> /_/\_\___|_| |_| |____(_) |_|(_)_____|
>
> (XEN) Xen version 3.4.2 (root@xxxxxxxxxxxx) (gcc version 4.3.4 (Debian
> 4.3.4-6) ) Thu Jan 28 15:41:41 EST 2010
> (XEN) Latest ChangeSet: unavailable
> (XEN) Command line: dummy=dummy dom0_mem=512M loglvl=all
> guest_loglvl=all 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 00000001
> ff1d68dc 00000000 ff14e687 0000e008 00000286 ff1d67c0 0000000a
> ff1c5146 ff22b0
>
>
> >
> >> -- Pasi
> >
> > 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
> >
> >
> > Gabor
> >
> >>>> -- Pasi
> >>>>
>
> - --
> +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
> | Gabor Szilagyi (Mr.) Gabor.Szilagyi@xxxxxxxxxxxx |
> | Computer System Adm. http://www.nyo.unep.org |
> | UNEP/New York Office Tel: +1-212-963-7781/Fax: +1-212-963-7341 |
> | I only open attachments I requested !!! No exceptions !!! |
> | Put your message in the email body !!! |
> +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
> "He who sacrifices freedom for security is neither secure nor free."
>
> Benjamin Franklin
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkth99gACgkQcYMbOTV6LVoUpACgs81ojuLe8zTaS7lnEY08M2n3
> Z4MAnRYSnEx9UrExQm07Y2uYStXsFMN+
> =rzdV
> -----END PGP SIGNATURE-----
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-users] Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt,
Pasi Kärkkäinen <=
- [Xen-devel] Re: [Xen-users] Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt, Keir Fraser
- Re: [Xen-users] Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt, gabor
- Re: [Xen-users] Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt, Keir Fraser
- Re: [Xen-users] Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt, Gabor Szilagyi
- [Xen-devel] Re: [Xen-users] Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt, Keir Fraser
- Re: [Xen-devel] Re: [Xen-users] Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt, Pasi Kärkkäinen
|
|
|