I have a dom0 machine running CentOS 5.4 with all the latest updates using Xen as my hypervisor. I am using Xen in part because this machine was set up prior to KVM being included in RHEL, and in part because KVM's network bridging configuration is not nearly as simple as Xen's. The dom0 machine is headless and I do all of my VM management via virsh from the command line. I have two hvm domU's:
A web server running CentOS 5.4
A mail server running Gentoo
Both VM's are backed by LV's on the dom0 but do not use LVM in the domU. Both have virtually identical libvirt configurations (differing by expected things like name, UUID, NIC MAC, VNC port, etc).
The web server domU (WSdomU hereafter) does not start since applying the most recent kernel update (kernel-xen-2.6.18-164.15.1.el5.x86_64 and kernel-2.6.18-164.15.1.el5.x86_64 for the dom0 and WSdomU respectively). By 'not start' I mean it appears to be running but it does not use an CPU cycles, does not bring up a graphical console, and does not respond on the network. The WSdomU is listed as no state rather than the normal running or blocked in xentop. The mail server domU starts fine and functions normally.
Here are the steps I have taken so far that did not solve the problem:
Reboot the dom0 to see if things come up on their own
Check xen dmesg on dom0
Check xend logs (a cursory viewing did not show anything blatant; specific suggestions of things to look for would be appreciated)
Attempted to connect to the WSdomU's graphical (VNC) console from the dom0
Shutdown the mail server domU and attempt to start the WSdomU
Check the SELinux labels on backing LV's (they're the same)
Set SELinux to permissive and attempt to start the WSdomU
Use virsh edit to try tweaking the WSdomU config
virsh undefine, reboot, virsh define the WSdomU config
dd the WSdomU LV to an .img file, copy it to my Fedora desktop and run it under KVM (works fine)
What steps should I take next to debug this?
I will edit in any additional configuration's requested in the comments.
