* Host crash with current unstable
@ 2009-07-15 13:02 Andre Przywara
0 siblings, 0 replies; only message in thread
From: Andre Przywara @ 2009-07-15 13:02 UTC (permalink / raw)
To: xen-devel; +Cc: Conny Seidel, Frank Arnold
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-07-15 13:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-15 13:02 Host crash with current unstable Andre Przywara
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.