All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: xen-devel@lists.xensource.com
Cc: Conny Seidel <conny.seidel@amd.com>, Frank Arnold <frank.arnold@amd.com>
Subject: Host crash with current unstable
Date: Wed, 15 Jul 2009 15:02:21 +0200	[thread overview]
Message-ID: <4A5DD35D.6020408@amd.com> (raw)

Hi,

we are experiencing serious problems with latest Xen unstable with 
2.6.18 Dom0 kernels.
Actually we cannot start any guests anymore.
When we boot Xen without any parameters, xm create returns and you can 
use xm list & co successfully. Only xm top shows a 100% usage (with the 
2nd vCPU not yet initialized) and QEMU seems to be blocked (no VNC update).
If you try to "xm destroy" or "xm pause" the guest, the whole box locks 
up, you can only power-cycle or hard-reset.
The last thing seen in the log files in the message about the domain 
being unpaused.
It seems that the hypervisor is still alive, so we suspect a Dom0 issue.

If you start xen.gz with "watchdog" the whole machine reboots 
immediately after the xm create.
The last thing seen in the log files in the message about the domain 
being unpaused.
I reduced the config file to the minimum (UP, empty disk and net), the 
problem still persists.

Can someone reproduce this? Has anyone an idea?

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448 3567 12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

                 reply	other threads:[~2009-07-15 13:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4A5DD35D.6020408@amd.com \
    --to=andre.przywara@amd.com \
    --cc=conny.seidel@amd.com \
    --cc=frank.arnold@amd.com \
    --cc=xen-devel@lists.xensource.com \
    /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.