[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Problem with Intel(R) Xeon(R) CPU L5640?


  • To: xen-users@xxxxxxxxxxxxx
  • From: admin <admin@xxxxxxx>
  • Date: Mon, 23 Oct 2017 01:20:10 +0200
  • Delivery-date: Tue, 24 Oct 2017 23:50:28 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Am Donnerstag, den 19.10.2017, 09:02 -0700 schrieb Sarah Newman:
> On 10/18/2017 05:09 PM, admin wrote:
> > Hi,
> > 
> > I have two servers of the same model, HP SE316M1.
> > 
> > The first one, running Xen 4.4, which was installed rather long
> > time ago.
> > Our backup server died (older Dell server) and was replaced by
> > another
> > HP server of the same model (SE316M1).
> > 
> > Unfortunately I have no chance of running Xen on the new server. 
> > I started with 4.9 and consecutively tried 4.8, 4.7 and 4.6 -
> > always having
> > Xen kernel crashing shortly after boot.
> > 
> > I then tried a self compiled Xen v4.9 with the same result.
> > 
> > Both server are equipped with 48 gigs of RAM and share the same
> > config, despite of:
> > 
> >   - srv1 (xen running) : HP Smart Array P800 RAID, 2 x Intel(R)
> > Xeon(R) CPU L5520 @2.27GHz Quad Core
> >   - srv2 (xen craching): HP Smart Array P410 RAID, 2 x Intel(R)
> > Xeon(R) CPU L5640 @2.27GHz Hexa Core
> > 
> > Also tried every combination of noapic, nolapic, acpi=off etc...
> > 
> > I then decided to install Xen v4.4 on the new server first in order
> > to migrate my VMs becuase
> > the old server needs some hardware maintainance. But Xen v4.4 did
> > crash as well!
> > 
> > Is this related to the CPU?
> 
> It has nothing to do with the CPU model.
> 
> What I would do for unknown hardware that's crashing, in no
> particular order:
> 
> Review the kernel logs when booted without Xen for warnings
> Check the BIOS and IPMI logs
Will do that

> Check for BIOS or device firmware updates
All up to date on both machines

> Review BIOS settings related to ACPI or PCI
Will check on that. My first idea was to compare all BIOS seetings
of both machines and make them match. But the running one is an
important productive machine - down time means $0 time...

> Run diagnostic utilities for the the various PCI devices if
> applicable
> Run a memory test in multi-core mode
> Remove or replace individual components to see if a particular
> component is causing problems

Thanks for your thoughts on this. I'll be back as soon as possible
or necessary.

> 
> --Sarah
> 
-- Manuel

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
https://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.