Got some more info by dumping the hung machine registers with
'xm debug-keys d' and 'xm dmesg':
(XEN) *** Dumping CPU3 host state: ***
(XEN) [ Xen-3.2-1 x86_64 debug=n Not tainted ]
(XEN) CPU:3
(XEN) RIP:e008:[] __dump_execstate+0x1/0x60
(XEN) RFLAGS: 00010002 CONTEXT:
Same thing happening here every few days. I managed to get some more info
using crash utility and a core generated with xm dump-core. To get a
vmlinux with debug symbols I recompiled the linux-image-2.6.26-2-xen
package with CONFIG_DEBUG_INFO.
The strange thing is that it seems to be stuck on th
I'm experiencing the same problem on multi-vcpu domUs. The dom0 and domUs are
2.6.26-17lenny2 on amd64 or i386. When a domU hangs it's stuck in "r" state
on at least one vcpu, the network stack and the console are unresponsive.
--
Leszek Urbanski
--
To UNSUBSCRIBE, email to debian-bugs-dist-r
> unfortunately, in the last couple weeks, i've been experiencing some issues
> with some domU machines crashing on lenny xen dom0.
>
> at some point, the domU just hangs, and "xm console" is unresponsive. still
> able to ping the domU server, but not log in via ssh, and existing ssh
> connections
Package: linux-image-2.6.26-2-xen-686
Version: 2.6.26-15lenny3
Severity: important
we've been using xen on debian extensively for the last couple years, and it's
overall been great for freegeek!
unfortunately, in the last couple weeks, i've been experiencing some issues
with some domU machines cr
5 matches
Mail list logo
