Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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
  • Attempted to connect to the WSdomU's graphical (VNC) console from the dom0
  • 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)
  • Shutdown the mail server domU and attempt to start the WSdomU
  • Use kpartx to access the partitions of the domU
    • Tried switching grub to use the previous kernel
  • 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
  • Use fdisk on the LV to ensure it has the correct partition layout
  • dd the WSdomU LV to an .img file, copy it to my Fedora desktop and run it under KVM (works fine)
  • dd the .img file to a new LV and create a new libvirt config xml (fails to start)

Sample config used to attempt a reconfiguration:

<domain type='xen'>
  <name>Webserver</name>
  <os>
    <type>hvm</type>
    <loader>/usr/lib/xen/boot/hvmloader</loader>
    <boot dev='hd'/>
  </os>
  <memory>262144</memory>
  <vcpu>1</vcpu>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <devices>
    <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
    <interface type='bridge'>
      <source bridge='xenbr0'/>
      <script path='vif-bridge'/>
    </interface>
    <disk type='block'>
      <source dev='/dev/mapper/SystemsVG-Webserver'/>
      <target dev='hda'/>
    </disk>
    <graphics type='vnc' />
  </devices>
</domain>

What steps should I take next to debug this?

I will edit in any additional configuration's requested in the comments.

share|improve this question

2 Answers 2

can upload sosreport from your host server !! centos 5.4

share|improve this answer
    
Which repository has the sosreport package? –  Ophidian Mar 26 '10 at 3:43
    
yum install sysreport -y –  Rajat Mar 26 '10 at 11:04
up vote 0 down vote accepted

With some help from the Centos-Virt list, I have stumbled upon a configuration that starts the domU just fine.

<domain type='xen'>
  <name>Webserver</name>
  <memory>262144</memory>
  <currentMemory>262144</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type>hvm</type>
    <loader>/usr/lib/xen/boot/hvmloader</loader>
    <boot dev='hd'/>
  </os>
  <features>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
    <disk type='block' device='disk'>
      <driver name='phy'/>
      <source dev='/dev/SystemsVG/Webserver'/>
      <target dev='hda' bus='ide'/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:3e:29:65:46'/>
      <source bridge='xenbr0'/>
      <script path='vif-bridge'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' autoport='yes'/>
  </devices>
</domain>

Speculation is that some change in the Xen Hypervisor may have the acpi or apic flag causing issues.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.