Hi, Ian! On Fri, 2011-04-22 at 14:19:32 +0100, Ian Campbell wrote:
> > After upgrading to Squeeze, I am watching a Xen VMHost that after a > > while it hangs. This did not happen when I was using Xen with Debian > > Lenny (in this case as with Squeeze, the Xen components are from > > Debian repositories). > > > > In each case I connected a keyboard and monitor to the computer and > > the screen remained black without answering any key. When this > > happens, I noticed that the drive activity LED apparently is > > permanently on. > I presume it also stopped responding to network e.g. ssh as well? Yes, the connection to the VMHost like its virtual machines is lost. In fact, one of the domUs has a DHCP server, and when this problem happens, the hosts that are configured with the DHCP server loses network connection. > Do the magic-sysrq key combinations produce any output? I didn't get to test it, but I will remember it when it returns to happen. > Can you reproduce it or did it just happen the once? If you can repro > then attaching and configuring a serial console would be useful, since > a) you could see if there was anything printed before the screen went > dark and b) you can access the Xen debug keyhandlers only over the > serial line. > > Were you doing anything when it hung or was the system just running in > a steady state? It happened several times. Surely I would say that at least five to ten times. The last time that I had to do hard reset was 14 hours ago. Unfortunately I have not a serial cable to connect to that computer (it's a home server), but I'll see if I can get one for more information to provide. I was analyzing the /var/log/messages and the crashes occur at times that do not currently hold any pattern. > I notice you are running a 32 bit hypervisor. I would highly recommend > using the 64 bit hypervisor (package "xen-hypervisor-4.0-amd64") even > on i386. You can continue to use your 32 bit dom0 kernel and userspace > but the 64 bit hypervisor is much more reliable and better tested etc. Thanks for the suggestion. I've purge the 32-bit hypervisor and I've installed the 64-bit hypervisor. I'll keep you informed. So far, records of dmesg I mentioned are still appearing. > [...] > > ---------------------------------------------------------------------- > > > > In particular, I noticed the following lines: > > > > ---------------------------------------------------------------------- > > [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2 > > [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9 > > > > [ 0.004000] ------------[ cut here ]------------ > > [ 0.004000] WARNING: at > > /build/buildd-linux-2.6_2.6.32-31-i386-qYaaJr/linux-2.6-2.6.32/debian/build/source_i386_xen/arch/x86/xen/enlighten > > .c:726 perf_events_lapic_init+0x28/0x29() > Thanks. This is a benign warning, unfortunately I doubt it is related > to the hang. Thanks for your reply. Regards, Daniel -- Daniel Bareiro - GNU/Linux registered user #188.598 Proudly running Debian GNU/Linux with uptime: 12:13:33 up 56 days, 17:08, 12 users, load average: 0.08, 0.03, 0.01
signature.asc
Description: Digital signature
