FAQ
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 a headless Mac Mini 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
o 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?

Aaron
--
"The goblins are in charge of maintenance? Why not just set it on fire
now and call it a day?"
--Whip Tongue, Viashino Technician

Search Discussions

  • Christopher G. Stach II at Mar 28, 2010 at 4:53 am

    ----- "Aaron Clark" wrote:

    What steps should I take next to debug this?
    Downgrade back to where you were bit by bit (or just guess that it's dom0's kernel) and see when it starts working again.

    What does the busted guest say when it tries to boot while you watch its [serial] console? Does the dom0 ever unpause the guest? (It should say in the logs.)

    --
    Christopher G. Stach II
    http://ldsys.net/~cgs/
  • Pasi Kärkkäinen at Mar 28, 2010 at 11:59 am

    On Sat, Mar 27, 2010 at 11:53:41PM -0500, Christopher G. Stach II wrote:
    ----- "Aaron Clark" wrote:
    What steps should I take next to debug this?
    Downgrade back to where you were bit by bit (or just guess that it's dom0's kernel) and see when it starts working again.

    What does the busted guest say when it tries to boot while you watch its [serial] console? Does the dom0 ever unpause the guest? (It should say in the logs.)
    Yeah, and remove the vfb (graphical vnc console) from the guest,
    so you can then do:

    xm create -f /etc/xen/guest -c

    to immediately attach to the console and see the guest kernel boot messages.

    -- Pasi
  • Aaron Clark at Mar 28, 2010 at 4:45 pm

    On 03/28/2010 07:59 AM, Pasi K?rkk?inen wrote:
    On Sat, Mar 27, 2010 at 11:53:41PM -0500, Christopher G. Stach II wrote:
    ----- "Aaron Clark"wrote:
    What steps should I take next to debug this?
    Downgrade back to where you were bit by bit (or just guess that it's dom0's kernel) and see when it starts working again.

    What does the busted guest say when it tries to boot while you watch its [serial] console? Does the dom0 ever unpause the guest? (It should say in the logs.)
    Yeah, and remove the vfb (graphical vnc console) from the guest,
    so you can then do:

    xm create -f /etc/xen/guest -c

    to immediately attach to the console and see the guest kernel boot messages.
    Ok, I've tried the following now:

    - rebooted the dom0 into the previous, working kernel-xen and start domU
    (doesn't work)
    - while in the old kernel-xen, switch the grub config for the domU to
    use the old kernel then try to start the domU (doesn't work)
    - remove the vnc lines from the guest's config via virsh edit and
    attempt to start (doesn't work)

    I do not have any serial console stuff set up, so I'll need a little bit
    more detailed instructions to get that working (which files I need to
    modify on guest and host, what to put where, etc).

    I have attached the snippet of the xend.log from my latest startup
    attempt and the virsh xml in use while it is 'running' but not actually
    working.

    Aaron
    --
    "The goblins are in charge of maintenance? Why not just set it on fire
    now and call it a day?"
    --Whip Tongue, Viashino Technician
    -------------- next part --------------
    An embedded and charset-unspecified text was scrubbed...
    Name: xend-snipped.log
    Url: http://lists.centos.org/pipermail/centos-virt/attachments/20100328/04c24df2/attachment.pl
    -------------- next part --------------
    An embedded and charset-unspecified text was scrubbed...
    Name: Belldandy.virsh
    Url: http://lists.centos.org/pipermail/centos-virt/attachments/20100328/04c24df2/attachment-0001.pl
  • Pasi Kärkkäinen at Mar 28, 2010 at 7:36 pm

    On Sun, Mar 28, 2010 at 12:45:58PM -0400, Aaron Clark wrote:
    On 03/28/2010 07:59 AM, Pasi K?rkk?inen wrote:
    On Sat, Mar 27, 2010 at 11:53:41PM -0500, Christopher G. Stach II wrote:
    ----- "Aaron Clark"wrote:
    What steps should I take next to debug this?
    Downgrade back to where you were bit by bit (or just guess that it's dom0's kernel) and see when it starts working again.

    What does the busted guest say when it tries to boot while you watch its [serial] console? Does the dom0 ever unpause the guest? (It should say in the logs.)
    Yeah, and remove the vfb (graphical vnc console) from the guest,
    so you can then do:

    xm create -f /etc/xen/guest -c

    to immediately attach to the console and see the guest kernel boot messages.
    Ok, I've tried the following now:

    - rebooted the dom0 into the previous, working kernel-xen and start domU
    (doesn't work)
    - while in the old kernel-xen, switch the grub config for the domU to
    use the old kernel then try to start the domU (doesn't work)
    - remove the vnc lines from the guest's config via virsh edit and
    attempt to start (doesn't work)

    I do not have any serial console stuff set up, so I'll need a little bit
    more detailed instructions to get that working (which files I need to
    modify on guest and host, what to put where, etc).
    You don't need a serial console to see the _guest_ kernel boot messages.
    You just disable vfb (graphical console) from the guest, and then the
    guest kernel messages will automatically go to the Xen text console:

    You can see the full guest kernel boot messages like this:

    xm create -f /etc/xen/<guest> -c

    Edit the /etc/xen/<guest> cfgfile first, and remove the vfb line to disable graphical console.
    I have attached the snippet of the xend.log from my latest startup
    attempt and the virsh xml in use while it is 'running' but not actually
    working.
    In your xml config there still was graphical console configured.

    -- Pasi
  • Aaron Clark at Mar 28, 2010 at 10:39 pm

    On 03/28/2010 03:36 PM, Pasi K?rkk?inen wrote:
    On Sun, Mar 28, 2010 at 12:45:58PM -0400, Aaron Clark wrote:

    Ok, I've tried the following now:

    - rebooted the dom0 into the previous, working kernel-xen and start domU
    (doesn't work)
    - while in the old kernel-xen, switch the grub config for the domU to
    use the old kernel then try to start the domU (doesn't work)
    - remove the vnc lines from the guest's config via virsh edit and
    attempt to start (doesn't work)

    I do not have any serial console stuff set up, so I'll need a little bit
    more detailed instructions to get that working (which files I need to
    modify on guest and host, what to put where, etc).
    You don't need a serial console to see the _guest_ kernel boot messages.
    You just disable vfb (graphical console) from the guest, and then the
    guest kernel messages will automatically go to the Xen text console:

    You can see the full guest kernel boot messages like this:

    xm create -f /etc/xen/<guest> -c

    Edit the /etc/xen/<guest> cfgfile first, and remove the vfb line to disable graphical console.
    I removed the vfb line from the /etc/xen/<guest> file... still doesn't
    start and the console does not attach.

    [root at Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c
    Using config file "/etc/xen/Belldandy".
    Started domain Belldandy
    xenconsole: Could not read tty from store: No such file or directory

    Aaron
    --
    "The goblins are in charge of maintenance? Why not just set it on fire
    now and call it a day?"
    --Whip Tongue, Viashino Technician
  • Christopher G. Stach II at Mar 29, 2010 at 3:14 am

    ----- "Aaron Clark" wrote:

    I removed the vfb line from the /etc/xen/<guest> file... still doesn't
    start and the console does not attach.

    [root at Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c
    Using config file "/etc/xen/Belldandy".
    Started domain Belldandy
    xenconsole: Could not read tty from store: No such file or directory
    Is there anything interesting in that run's qemu log?

    --
    Christopher G. Stach II
    http://ldsys.net/~cgs/
  • Aaron Clark at Mar 30, 2010 at 1:12 am

    On 03/28/2010 11:14 PM, Christopher G. Stach II wrote:
    ----- "Aaron Clark"wrote:
    I removed the vfb line from the /etc/xen/<guest> file... still doesn't
    start and the console does not attach.

    [root at Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c
    Using config file "/etc/xen/Belldandy".
    Started domain Belldandy
    xenconsole: Could not read tty from store: No such file or directory
    Is there anything interesting in that run's qemu log?
    The contents of the qemu log are:
    domid: 5
    qemu: the number of cpus is 1
    Watching /local/domain/5/logdirty/next-active
    Watching /local/domain/0/device-model/5/command
    qemu: could not open serial device 'none'

    Note that the qemu-dm process is listed as 'defunct' in ps.

    One interesting line from the xend.log that I don't know how to
    interpret is:
    [2010-03-29 21:03:53 xend.XendDomainInfo 3186] DEBUG
    (XendDomainInfo:633) Checking for duplicate for uname:
    /dev/SystemsVG/Belldandy [phy:/dev/SystemsVG/Belldandy], dev: hda:disk,
    mode: w
    [2010-03-29 21:03:53 xend 3186] DEBUG (blkif:27) exception looking up
    device number for hda:disk: [Errno 2] No such file or directory:
    '/dev/hda:disk'


    Not sure if it means anything but thoughts appreciated. This is **not**
    the last line in the log.

    Aaron
    --
    "The goblins are in charge of maintenance? Why not just set it on fire
    now and call it a day?"
    --Whip Tongue, Viashino Technician
  • Pasi Kärkkäinen at Mar 29, 2010 at 5:28 am

    On Sun, Mar 28, 2010 at 06:39:01PM -0400, Aaron Clark wrote:
    On 03/28/2010 03:36 PM, Pasi K?rkk?inen wrote:
    On Sun, Mar 28, 2010 at 12:45:58PM -0400, Aaron Clark wrote:

    Ok, I've tried the following now:

    - rebooted the dom0 into the previous, working kernel-xen and start domU
    (doesn't work)
    - while in the old kernel-xen, switch the grub config for the domU to
    use the old kernel then try to start the domU (doesn't work)
    - remove the vnc lines from the guest's config via virsh edit and
    attempt to start (doesn't work)

    I do not have any serial console stuff set up, so I'll need a little bit
    more detailed instructions to get that working (which files I need to
    modify on guest and host, what to put where, etc).
    You don't need a serial console to see the _guest_ kernel boot messages.
    You just disable vfb (graphical console) from the guest, and then the
    guest kernel messages will automatically go to the Xen text console:

    You can see the full guest kernel boot messages like this:

    xm create -f /etc/xen/<guest> -c

    Edit the /etc/xen/<guest> cfgfile first, and remove the vfb line to disable graphical console.
    I removed the vfb line from the /etc/xen/<guest> file... still doesn't
    start and the console does not attach.

    [root at Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c
    Using config file "/etc/xen/Belldandy".
    Started domain Belldandy
    xenconsole: Could not read tty from store: No such file or directory
    Hmm.. only now I notice you're trying to start a HVM guest.
    HVM guests will pretty much require graphical console..

    Sorry for the wrong tips. The stuff I wrote was for PV guests.

    -- Pasi
  • Sergio Charpinel Jr. at Mar 29, 2010 at 12:18 pm
    - Try to unset any graphical option and run the domU, maybe its
    missing some lib, like sdl. I don't know how to do it in virsh,
    because in xen cfg, default vnc option is 1.

    - Check paths to hvmloader, qemu-dm

    - post more log files, if you have.

    2010/3/29 Pasi K?rkk?inen <pasik at iki.fi>
    On Sun, Mar 28, 2010 at 06:39:01PM -0400, Aaron Clark wrote:
    On 03/28/2010 03:36 PM, Pasi K?rkk?inen wrote:
    On Sun, Mar 28, 2010 at 12:45:58PM -0400, Aaron Clark wrote:

    Ok, I've tried the following now:

    - rebooted the dom0 into the previous, working kernel-xen and start
    domU
    (doesn't work)
    - while in the old kernel-xen, switch the grub config for the domU to
    use the old kernel then try to start the domU (doesn't work)
    - remove the vnc lines from the guest's config via virsh edit and
    attempt to start (doesn't work)

    I do not have any serial console stuff set up, so I'll need a little
    bit
    more detailed instructions to get that working (which files I need to
    modify on guest and host, what to put where, etc).
    You don't need a serial console to see the _guest_ kernel boot
    messages.
    You just disable vfb (graphical console) from the guest, and then the
    guest kernel messages will automatically go to the Xen text console:

    You can see the full guest kernel boot messages like this:

    xm create -f /etc/xen/<guest> -c

    Edit the /etc/xen/<guest> cfgfile first, and remove the vfb line to
    disable graphical console.
    I removed the vfb line from the /etc/xen/<guest> file... still doesn't
    start and the console does not attach.

    [root at Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c
    Using config file "/etc/xen/Belldandy".
    Started domain Belldandy
    xenconsole: Could not read tty from store: No such file or directory
    Hmm.. only now I notice you're trying to start a HVM guest.
    HVM guests will pretty much require graphical console..

    Sorry for the wrong tips. The stuff I wrote was for PV guests.

    -- Pasi

    _______________________________________________
    CentOS-virt mailing list
    CentOS-virt at centos.org
    http://lists.centos.org/mailman/listinfo/centos-virt


    --
    Sergio Roberto Charpinel Jr.
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://lists.centos.org/pipermail/centos-virt/attachments/20100329/a59e6dda/attachment.html
  • Aaron Clark at Mar 30, 2010 at 1:15 am

    On 03/29/2010 08:18 AM, Sergio Charpinel Jr. wrote:
    - Try to unset any graphical option and run the domU, maybe its missing some lib, like sdl. I don't know how to do it in virsh, because in xen cfg, default vnc option is 1.
    Already tried, doesn't make a lick of difference.
    - Check paths to hvmloader, qemu-dm
    They do exist. Keep in mind that I have another domU with pretty much
    the same configuration that is functioning fine on this machine.
    - post more log files, if you have.
    What other log files would help?

    Here is the contents of the xen config generated by virsh:
    name = "Belldandy"
    uuid = "2627c318-d3a7-83a6-522c-fa2586fb86be"
    maxmem = 256
    memory = 256
    vcpus = 1
    builder = "hvm"
    kernel = "/usr/lib/xen/boot/hvmloader"
    boot = "c"
    pae = 1
    acpi = 1
    apic = 1
    localtime = 0
    on_poweroff = "destroy"
    on_reboot = "restart"
    on_crash = "restart"
    device_model = "/usr/lib64/xen/bin/qemu-dm"
    disk = [ "phy:/dev/SystemsVG/Belldandy,hda,w" ]
    vif = [ "mac�:16:3e:1d:43:df,bridge=xenbr0,script=vif-bridge" ]
    parallel = "none"
    serial = "none"

    Aaron
    --
    "The goblins are in charge of maintenance? Why not just set it on fire
    now and call it a day?"
    --Whip Tongue, Viashino Technician
  • Christopher G. Stach II at Mar 30, 2010 at 1:37 am

    ----- "Aaron Clark" wrote:

    qemu: could not open serial device 'none'
    http://os-drive.com/files/docbook/xen-faq.html#serial_console_hvm

    Does the LV show that it's open (or ever changes state) when the VM attempts to boot? Did you try taking a snapshot of the LV and mucking around with the xen configuration to see if anything changes? Did you update anything else on the machine, like perhaps the BIOS? Can you mount the VM's filesystem? Is its partition table okay? How about the boot loader?

    --
    Christopher G. Stach II
    http://ldsys.net/~cgs/
  • Aaron Clark at Mar 30, 2010 at 1:47 am

    On 03/29/2010 09:37 PM, Christopher G. Stach II wrote:
    ----- "Aaron Clark"wrote:
    qemu: could not open serial device 'none'
    http://os-drive.com/files/docbook/xen-faq.html#serial_console_hvm
    I will give this a look to see if it shed any light on the situation.
    Does the LV show that it's open (or ever changes state) when the VM attempts to boot? Did you try taking a snapshot of the LV and mucking around with the xen configuration to see if anything changes? Did you update anything else on the machine, like perhaps the BIOS? Can you mount the VM's filesystem? Is its partition table okay? How about the boot loader?
    - The LV goes to Open when the VM starts and stays that way until the VM
    is destroyed
    - I have tried messing with the virsh/xen config repeatedly after taking
    backups of them
    - The host machine has had no hardware or firmware updates applied to it
    - I can and have mounted the VM's file systems using kpartx with no
    troubles at all
    - When I dd'd the LV to a .img file and started it with KVM, the
    Bootloader appears as expected

    Baffled,
    Aaron
    --
    "The goblins are in charge of maintenance? Why not just set it on fire
    now and call it a day?"
    --Whip Tongue, Viashino Technician
  • Sergio Charpinel Jr. at Mar 30, 2010 at 11:33 am
    Aaron,

    Seems to be something related to your block device.

    Try this config file:
    name = "Belldandy"
    maxmem = 256
    memory = 256
    vcpus = 1
    builder = "hvm"
    kernel = "/usr/lib/xen/boot/hvmloader"
    boot = "c"
    on_poweroff = "destroy"
    on_reboot = "restart"
    on_crash = "restart"
    device_model = "/usr/lib64/xen/bin/qemu-dm"
    disk = [ "phy:/dev/SystemsVG/Belldandy,hda,w" ]
    vif = [ "mac�:16:3e:1d:43:df,bridge=xenbr0,script=vif-bridge" ]
    vncpasswd='YOURPASSHERE'
    vnclisten="YOURDOM0 IP HERE"
    vnc=1

    Using one of this options:
    disk = [ 'phy:/dev/SystemsVG/Belldandy, ioemu:hda,w' ]
    disk = [ 'phy:/dev/SystemsVG/Belldandy, sda,w' ]
    disk = [ 'phy:/dev/SystemsVG/Belldandy, xvda,w' ]

    You can try comment your vif line, maybe is something related to it, and it
    won't start.

    Then, try to connect to vnc server: dom0ip:5900

    What's the difference between yours domU config files ? Did you see any
    other error in xend.log ? If there is no difference at all, try to fsck your
    lvm partition.

    2010/3/29 Aaron Clark <ophidian at ophidian.homeip.net>
    On 03/29/2010 09:37 PM, Christopher G. Stach II wrote:
    ----- "Aaron Clark"wrote:
    qemu: could not open serial device 'none'
    http://os-drive.com/files/docbook/xen-faq.html#serial_console_hvm
    I will give this a look to see if it shed any light on the situation.
    Does the LV show that it's open (or ever changes state) when the VM
    attempts to boot? Did you try taking a snapshot of the LV and mucking around
    with the xen configuration to see if anything changes? Did you update
    anything else on the machine, like perhaps the BIOS? Can you mount the VM's
    filesystem? Is its partition table okay? How about the boot loader?
    - The LV goes to Open when the VM starts and stays that way until the VM
    is destroyed
    - I have tried messing with the virsh/xen config repeatedly after taking
    backups of them
    - The host machine has had no hardware or firmware updates applied to it
    - I can and have mounted the VM's file systems using kpartx with no
    troubles at all
    - When I dd'd the LV to a .img file and started it with KVM, the
    Bootloader appears as expected

    Baffled,
    Aaron
    --
    "The goblins are in charge of maintenance? Why not just set it on fire
    now and call it a day?"
    --Whip Tongue, Viashino Technician
    _______________________________________________
    CentOS-virt mailing list
    CentOS-virt at centos.org
    http://lists.centos.org/mailman/listinfo/centos-virt


    --
    Sergio Roberto Charpinel Jr.
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://lists.centos.org/pipermail/centos-virt/attachments/20100330/9fdb678b/attachment.html
  • Aaron Clark at Apr 1, 2010 at 3:50 am

    On 03/30/2010 07:33 AM, Sergio Charpinel Jr. wrote:
    Aaron,

    Seems to be something related to your block device.

    Try this config file:
    Sergio,

    I just tried this config and it booted fine:
    name = "Belldandy"
    maxmem = 256
    memory = 256
    vcpus = 1
    builder = "hvm"
    kernel = "/usr/lib/xen/boot/hvmloader"
    boot = "c"
    pae = 1
    on_poweroff = "destroy"
    on_reboot = "restart"
    on_crash = "restart"
    device_model = "/usr/lib64/xen/bin/qemu-dm"
    disk = [ "phy:/dev/SystemsVG/Belldandy,hda,w" ]
    vif = [ "mac�:16:3e:29:65:46,bridge=xenbr0,script=vif-bridge" ]
    vnc = 1

    Attached is the generated virsh xml from the above.

    I'm going to tinker with this for a bit to try and figure out what
    difference from the previous config is actually the cause of the issue.
    I just had the other, formerly working VM, bail with the same symptoms
    once I got this one work. The workaround is nice but I definitely want
    to isolate this bug now.

    Thanks everyone for all the help!

    Aaron
    --
    "The goblins are in charge of maintenance? Why not just set it on fire
    now and call it a day?"
    --Whip Tongue, Viashino Technician
    -------------- next part --------------
    An embedded and charset-unspecified text was scrubbed...
    Name: belldandy.virsh
    Url: http://lists.centos.org/pipermail/centos-virt/attachments/20100331/8c6aa473/attachment.pl
  • Aaron Clark at Apr 12, 2010 at 2:43 am

    On 03/31/2010 11:50 PM, Aaron Clark wrote:
    I'm going to tinker with this for a bit to try and figure out what
    difference from the previous config is actually the cause of the issue.
    I just had the other, formerly working VM, bail with the same symptoms
    once I got this one work. The workaround is nice but I definitely want
    to isolate this bug now.
    I just wanted to follow up on this a bit. Once I got it going, the VM
    ran for over 10 days without issues. Tonight I started tinkering with
    the Xen config to try an isolate whether it was acpi or apic causing
    troubles.... the short answer is that neither is the problem.

    What is the problem then? It looks like a bug in virsh/libvirt; I'll
    need some help to debug it though. I'm using the following file for all
    of this:
    name = "Belldandy"
    uuid = "b1f1d0a4-9687-947c-5eaf-b362d5d5a199"
    maxmem = 256
    memory = 256
    vcpus = 1
    builder = "hvm"
    kernel = "/usr/lib/xen/boot/hvmloader"
    boot = "c"
    pae = 1
    acpi = 1
    apic = 1
    on_poweroff = "destroy"
    on_reboot = "restart"
    on_crash = "restart"
    device_model = "/usr/lib64/xen/bin/qemu-dm"
    disk = [ "phy:/dev/SystemsVG/Belldandy,hda,w" ]
    vif = [ "mac�:16:3e:29:65:46,bridge=xenbr0,script=vif-bridge" ]
    vnc = 1


    1. xm create -f ./Belldandy.xen -- successfully starts as expected
    2. Copy Belldandy.xen to /etc/xen/Belldandy, start with xm create
    Belldandy -- successfully starts as expected
    3. Attempt to start with virsh start Belldandy -- fails horribly with
    the same 'no state' issue as before.

    So I can work around this for now by not using virsh to start them up
    but it's still quite annoying. I should note that I can remotely access
    that machine with VMM and it suffers the same issues but handles
    everything else just fine once I manually start the domU via xm as above.

    Aaron
    --
    "The goblins are in charge of maintenance? Why not just set it on fire
    now and call it a day?"
    --Whip Tongue, Viashino Technician
  • Pasi Kärkkäinen at Apr 12, 2010 at 7:34 am

    On Sun, Apr 11, 2010 at 10:43:21PM -0400, Aaron Clark wrote:
    On 03/31/2010 11:50 PM, Aaron Clark wrote:

    I'm going to tinker with this for a bit to try and figure out what
    difference from the previous config is actually the cause of the issue.
    I just had the other, formerly working VM, bail with the same symptoms
    once I got this one work. The workaround is nice but I definitely want
    to isolate this bug now.
    I just wanted to follow up on this a bit. Once I got it going, the VM
    ran for over 10 days without issues. Tonight I started tinkering with
    the Xen config to try an isolate whether it was acpi or apic causing
    troubles.... the short answer is that neither is the problem.

    What is the problem then? It looks like a bug in virsh/libvirt; I'll
    need some help to debug it though. I'm using the following file for all
    of this:
    name = "Belldandy"
    uuid = "b1f1d0a4-9687-947c-5eaf-b362d5d5a199"
    maxmem = 256
    memory = 256
    vcpus = 1
    builder = "hvm"
    kernel = "/usr/lib/xen/boot/hvmloader"
    boot = "c"
    pae = 1
    acpi = 1
    apic = 1
    on_poweroff = "destroy"
    on_reboot = "restart"
    on_crash = "restart"
    device_model = "/usr/lib64/xen/bin/qemu-dm"
    disk = [ "phy:/dev/SystemsVG/Belldandy,hda,w" ]
    vif = [ "mac�:16:3e:29:65:46,bridge=xenbr0,script=vif-bridge" ]
    vnc = 1


    1. xm create -f ./Belldandy.xen -- successfully starts as expected
    2. Copy Belldandy.xen to /etc/xen/Belldandy, start with xm create
    Belldandy -- successfully starts as expected
    3. Attempt to start with virsh start Belldandy -- fails horribly with
    the same 'no state' issue as before.

    So I can work around this for now by not using virsh to start them up
    but it's still quite annoying. I should note that I can remotely access
    that machine with VMM and it suffers the same issues but handles
    everything else just fine once I manually start the domU via xm as above.
    Hmm.. interesting.

    I guess the VM info (state) needs to be in the libvirt database before
    you can 'virsh start' it?

    -- Pasi
  • Christopher G. Stach II at Apr 1, 2010 at 8:56 am

    ----- "Aaron Clark" wrote:
    On 03/30/2010 07:33 AM, Sergio Charpinel Jr. wrote:
    Aaron,

    Seems to be something related to your block device.

    Try this config file:
    Sergio,

    I just tried this config and it booted fine:
    name = "Belldandy"
    maxmem = 256
    memory = 256
    vcpus = 1
    builder = "hvm"
    kernel = "/usr/lib/xen/boot/hvmloader"
    boot = "c"
    pae = 1
    on_poweroff = "destroy"
    on_reboot = "restart"
    on_crash = "restart"
    device_model = "/usr/lib64/xen/bin/qemu-dm"
    disk = [ "phy:/dev/SystemsVG/Belldandy,hda,w" ]
    vif = [ "mac�:16:3e:29:65:46,bridge=xenbr0,script=vif-bridge" ]
    vnc = 1

    Attached is the generated virsh xml from the above.

    I'm going to tinker with this for a bit to try and figure out what
    difference from the previous config is actually the cause of the
    issue.
    I just had the other, formerly working VM, bail with the same symptoms
    once I got this one work. The workaround is nice but I definitely
    want to isolate this bug now.
    Try mucking with the acpi and apic flags. IIRC, they both default to 0 in this version of Xen so by eliding them, you turned them off. On the right machine, either will screw up HVM.

    --
    Christopher G. Stach II
    http://ldsys.net/~cgs/

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcentos-virt @
categoriescentos
postedMar 28, '10 at 12:55a
activeApr 12, '10 at 7:34a
posts18
users4
websitecentos.org
irc#centos

People

Translate

site design / logo © 2022 Grokbase