I started switching a system which had been primarily a low-volume nameserver/mail relay to being a xen host a couple days ago, and it's now hung overnight two nights in a row. The setup is a dom0 (still performing the dns/mail relay, since I haven't migrated it yet) running a -current kernel of a couple days ago on a 3.0_STABLE userland. The domU is still doing little (I'm setting it up as a web server, but no real traffic yet). What happened last night is that a "top" running in the domU hung at about 03:19, but there's evidence that the dom0 was doing _some_ processing until 07:00, although at that time it wouldn't respond on console. (As an aside, I'm unable to get dom0 into ddb - the machine has a serial console, if that matters) After a few minutes of poking around, I did the ^A^A^A thing to switch to the Xen console, and rebooted. A few other details: - the nightly cron jobs on the two "machines" run at the same time - I haven't tweaked that yet. - the domU's disk is provided by two files in the filesystem of the dom0 - the dom0 has 192M of RAM, the domU 128M. The physical machine has two CPUs (PIII-1GHz) and 1G RAM Any thoughts about what might be happening, how I can troubleshoot, and/or how I can fix this? I'd hate to lose the ability to run multiple VMs on this machine... Thanks, +j
Attachment:
signature.asc
Description: OpenPGP digital signature