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

[Xen-users] Hard reset on starting HVM dom0, multiple kernels, distros, xen versions


  • To: <xen-users@xxxxxxxxxxxxx>
  • From: "Guido Hecken" <guido.hecken@xxxxxxxxxxxxx>
  • Date: Sat, 17 Nov 2012 11:41:00 +0100
  • Delivery-date: Sat, 17 Nov 2012 10:42:18 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>
  • Thread-index: Ac3EabCPXF/7f14ORf+bytkE6n5ARgAQvZBg
  • Thread-topic: [Xen-users] Hard reset on starting HVM dom0, multiple kernels, distros, xen versions

-----Ursprüngliche Nachricht-----
Von: xen-users-bounces@xxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxx] 
Im Auftrag von Adam Goryachev
Gesendet: Samstag, 17. November 2012 03:01
An: xen-users@xxxxxxxxxxxxx
Betreff: Re: [Xen-users] Hard reset on starting HVM dom0, multiple kernels, 
distros, xen versions

On 17/11/12 11:57, Alexandre Kouznetsov wrote:
> Hello.
>
> El 16/11/12 18:34, Sam Mulvey escribió:
>> Memtest and cpuburn for half an hour encountered no issues. I haven't
>> had any problems with other hardware. Is there something else I can
>> look at to debug?
> Not much. Analog hardware things: temperature, PSU capacity/quality,
> some loose connector, static electricity.
>
> I noticed that Xen you are using is version 4.1 or grater. I use 4.0
> myself, it have proven to be very stable, so a problem like one you
> describe immediately makes me think it's hardware issue.
>
> I guess it's could be a good idea to make sure the problem is
> reproduceable with a known stable Xen hypervisor (I use Debian
> Squeeze's one, 4.0.1 to be precise). If so, we can isolate it to
> hardware failure/incompatibility, of a nature still unknown.
>
> This list is monitored by people from Xen development team, maybe they
> can give a better clue. Until then, a formal bug report is the way to
> go, if the problem does not shows up with a known stable version.
>
Actually, I've seen this a number of times on various hardware using
Debian Stable versions of xen. The first time I spent over 10 hours
trying different things to make it work (virtualise an existing windows
server 2003 using dd to copy the old drive to the new). Finally, an
upgrade to debian testing resolved the issue immediately. Since then,
I've frequently used debian testing versions, which has always resolved
the issue for me. So I would point the finger at software.

PS, the hardware I've had this problem on with debian stable (first
time) had been in production for almost 12 months with debian testing
and has been rock solid.

[GH] 
Same here, all of our xen hypervsiors are running under debian squeeze without 
any problems.
At the moment I'm testing debian wheezy with xen 4.1.3, everything seems to run 
fine. All machines using HVM or Paravirtualization run stable and with good 
performance.

As others already advised here, check your hardware and test with squeeze or 
wheezy.
The squeeze/wheezy hypervisors are installed and configured by using preseed in 
~15 minutes - assumed you have a functional netboot environment and a working 
preseed-file.

Just my 2 cents
Guido


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


 


Rackspace

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