Am 19.05.2010 um 18:25 schrieb Avi Kivity <avi@xxxxxxxxxx>:
On 05/19/2010 11:33 AM, Riccardo wrote:
This is a multi-part message in MIME format.
Hi,
I have a server dual xeon quad core with gentoo and qemu:
app-emulation/qemu-kvm-0.12.3-r1 USE="aio gnutls ncurses sasl vde -
alsa
-bluetooth -curl -esd -fdt -hardened -kvm-trace -pulseaudio -qemu-
ifup -sdl
-static"
Any suggestions?
It's possible to enable a log for what service?
There are almost impossible to debug.
Try copying vmlinux out of your guest and attach with gdb when it
hangs. Then issue the command
(gdb) thread apply all backtrace
to see what the guest is doing.
Another thing coming to my mind is sysrq. Do ctrl-alt-2 and type
"sendkey alt-print-o" (IIRC, please check the docs for sysrq letters).
That should give you a backtrace for stuck cpus. If that doesn't help,
go with dumping the state of all processes. For easy dumpibg, boot the
guest with -serial stdio and pass 'console=ttyS0' on the kernel
command line.
Alex
--
Do not meddle in the internals of kernels, for they are subtle and
quick to panic.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
