From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: agya naila <agya.naila@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: XEN 4.1 error Critical Interrupt - Front panel NMI
Date: Tue, 5 Feb 2013 18:30:21 +0200 [thread overview]
Message-ID: <20130205163021.GR8912@reaktio.net> (raw)
In-Reply-To: <CAN-nQwhBVOmWnZk-a6LZ2+tEa82XAOpxTHfOjEMhGkcNd7zL-A@mail.gmail.com>
On Tue, Feb 05, 2013 at 04:49:47PM +0100, agya naila wrote:
> Hello Everyone,
> I am quite new on XEN. I tried to installed XEN on my server and I know
> this server series IBM Xeon 3,4 Ghz didn't have Intel VTx support so I am
> pllaning to use paravirtualization.
> I configure the server with Ubuntu Desktop 12.0464 bit as dom0 with XEN
> 4.1 64 hypervisor. The configuration using repositories exactly by this
> tutorial [1]https://help.ubuntu.com/community/XenProposed :
>
- What exact Xen version are you using?
- What exact Linux dom0 kernel are you using?
- Please paste your grub settings for the Xen entry.
- Did you capture the error/crash logs from the Serial console? (SOL provided by the blade management).
-- Pasi
> Installing Xen
>
> Install a 64-bit hypervisor
>
> sudo apt-get install xen-hypervisor-amd64
>
> Modify GRUB to default to booting Xen:
>
> sudo sed -i 's/GRUB_DEFAULT=.*\+/GRUB_DEFAULT="Xen 4.1-amd64"/' /etc/default/grub
> sudo update-grub
>
> Set the default toolstack to xm (aka xend):
>
> sudo sed -i 's/TOOLSTACK=.*\+/TOOLSTACK="xm"/' /etc/default/xen
>
> Now reboot:
>
> sudo reboot
>
> But when rebooting the Dom0 failed to start, enclosed was the error
> message when Xen booting and after that Dom0 will restarting over and
> over.
> On Blade server system log I got error message :
> (Bestak_septaher) SMI Hdlr: 00151743 HI Fatal Error, HI_FERR/NERR Value=
> 0020
> (Bestak_septaher) Critical Interrupt - Front panel NMI
> Please Suggest, thank you very much for any one help.
> Best Regards,
> Agya
>
> References
>
> Visible links
> 1. https://help.ubuntu.com/community/XenProposed
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-02-05 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 15:49 XEN 4.1 error Critical Interrupt - Front panel NMI agya naila
2013-02-05 16:30 ` Pasi Kärkkäinen [this message]
2013-02-05 20:00 ` agya naila
2013-02-05 20:08 ` IBM HS20 Xen 4.1 and 4.2 Critical Interrupt - Front panel NMI crash Pasi Kärkkäinen
2013-02-06 7:58 ` Jan Beulich
2013-02-06 11:29 ` Pasi Kärkkäinen
2013-02-06 11:45 ` Jan Beulich
2013-02-06 11:48 ` agya naila
2013-02-06 12:01 ` agya naila
2013-02-06 13:28 ` Pasi Kärkkäinen
2013-02-06 13:39 ` agya naila
2013-02-07 20:51 ` Fabian Arrotin
2013-02-08 14:08 ` agya naila
2013-02-08 14:13 ` Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130205163021.GR8912@reaktio.net \
--to=pasik@iki.fi \
--cc=agya.naila@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.