This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Xen 4.0.1 freezes with no output

To: Sven Anders <anders@xxxxxxxxxx>
Subject: Re: [Xen-users] Xen 4.0.1 freezes with no output
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Wed, 8 Sep 2010 14:17:37 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 08 Sep 2010 04:19:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C875C13.7030501@xxxxxxxxxx>
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: <4C864321.3070302@xxxxxxxxxx> <20100907172401.GA2804@xxxxxxxxxxx> <4C868962.7040305@xxxxxxxxxx> <20100907185310.GB2804@xxxxxxxxxxx> <4C875C13.7030501@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Wed, Sep 08, 2010 at 11:49:07AM +0200, Sven Anders wrote:
> Pasi Kärkkäinen schrieb:
> > On Tue, Sep 07, 2010 at 08:50:10PM +0200, Sven Anders wrote:
> >
> >>> Also is the latest pvops dom0 kernel atm.
> > 
> > Yep, that'll give you atm.
> Ok, I tested the latest one. It crashes too. Same phenomenon.

Ok, I added xen-devel to CC.

> I assume the problem lies in the Xen code, not the pvops dom0 kernel.
> Should I try a newer version of Xen? (Currently using 4.0.1 from tar-file).
> But just to be sure:
>  Are there any kernel options which I should NOT use at all?
>  (Please take a look at my kernel config in the first post.)
> I'm still uncertain about this error message:
>  XENBUS: Unable to read cpu state
> Are these harmless and can I ignore them? What can be the cause?
> Maybe I should disable some of the BIOS options?
> Here are some of the options I enabled in the BIOS:
> - MPS and ACPI MADT ordering: Modern ordering
> - Intel(R) Virtualization Tech: Enabled
> - Execute-Disable Bit Capability: Enabled
> - Simultaneous Multi-Threading: Enabled
> - Intel(R) EIST Technologie: Enabled
> - Intel(R) Turbo Boost: Enabled
> - C1E Support: Enabled
> - Intel(R) C-STATE tech: Enabled
> - C State package limit setting: Auto
> - C1 Auto Demotion: Enabled
> - C3 Auto Demotion: Enabled
> - Intel VT-d: Enabled
> - Active State Power Managment: Enabled
> - Remote Access Configuration: Enabled
> - ACPI Aware O/S: Yes
> - ACPI APIC support: Enabled
> - APIC ACPI SCI IRQ: Disabled
> - ACPI Version Features: ACPI v2.0
> Any other (further) suggestions?
> I'm wondering, because I did not get ANY output at all.
> I enabled full debug output, compiled with debug enabled and I
> still get nothing...

How long does it take before it silently crashes?

-- Pasi

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>