Hi all, I confirm the problem is really XEN related. We made more tests with non XEN kernel and we never got the error reported here. Now we are going to run again a XEN dom0 kernel, updating to latest kernel (from 2.6.32-27 to 2.6.32-29). I will report here more information whenever I collect them.
The problem is: when the system crash, the machine is still powered on but nobody may connect and login. So, we are going to log in on the console and leave a shell opened. When the kernel will hang, we'll try to issue «xm dmesg» command. Setting syslog on a remote machine, would this help at all? Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
