Results 1 to 4 of 4

Thread: Xen domains don't start on reboot of Dom 0

  1. #1

    Default Xen domains don't start on reboot of Dom 0

    I hope this is the correct forum for this question. I've built a Xen server on top of SLED 10.2. Domain-0 is therefore running SLED 10.2, Domains 1 through 7 are running openSuse11.1. All hosts were built from a common Autoyast file so I expected them to behave the same, but on rebooting Domain-0 only Domains 0, 1, 2, and 3 start automatically. The remaining domains will start without error if I run them from the VMM or 'xm start <domain>'.

    I thought this was controlled by the config files in /etc/xen/vm but there is no apparent difference between the configurations other than the virtual disk designation and host name. I have tried changing the <on_poweroff>, <on_reboot>, and <on_crash> values but it doesn't change the behavior. There are both straight text and XML config files. I am posting the XML config files from Domain-1 and Domain-4, but the ASCII files appear to have the same settings.

    I can see the first 4 Domains build in xend.log, but I'm not finding any failure or reasons that the other 4 don't build logged anywhere.

    Any solutions or even suggestions as to what else to look at are very appreciated.

    Here are the XML config files for [Domain-1] and [Domain-4] (server names have been replaced with domain IDs):

    [Domain-0]:/etc/xen/vm # cat [Domain-1].xml
    <domain type='xen'>
    <name>[Domain-1]</name>
    <uuid>34d3455d-f5bd-e41a-3be2-c51388f2d8b0</uuid>
    <memory>393216</memory>
    <maxmemory>524288</maxmemory>
    <vcpu>1</vcpu>
    <on_poweroff>destroy</on_poweroff>
    <on_reboot>restart</on_reboot>
    <on_crash>destroy</on_crash>
    <clock sync='utc'/>
    <os type='opensuse'>
    <type>linux</type>
    <bootloader>/usr/lib/xen/boot/domUloader.py</bootloader>
    <bootargs>--entry=xvda2:/boot/vmlinuz-xen,/boot/initrd-xen</bootargs>
    <cmdline> </cmdline>
    </os>
    <devices>
    <disk type='file' device='disk'>
    <driver name='file'/>
    <source file='/var/lib/xen/images/[Domain-1]/disk1'/>
    <target dev='xvda'/>
    </disk>
    <interface type='bridge' model='para'>
    <mac address='00:16:3e:0a:1b:2c'/>
    <script path='/etc/xen/scripts/vif-bridge'/>
    </interface>
    <graphics type='vnc'/>
    </devices>
    </domain>

    [Domain-0]:/etc/xen/vm # cat [Domain-4].xml
    <domain type='xen'>
    <name>[Domain-4]</name>
    <uuid>166ca336-83c8-c17b-4039-ad7aff26e7ef</uuid>
    <memory>393216</memory>
    <maxmemory>524288</maxmemory>
    <vcpu>1</vcpu>
    <on_poweroff>destroy</on_poweroff>
    <on_reboot>restart</on_reboot>
    <on_crash>destroy</on_crash>
    <clock sync='utc'/>
    <os type='opensuse'>
    <type>linux</type>
    <bootloader>/usr/lib/xen/boot/domUloader.py</bootloader>
    <bootargs>--entry=xvda2:/boot/vmlinuz-xen,/boot/initrd-xen</bootargs>
    <cmdline> </cmdline>
    </os>
    <devices>
    <disk type='file' device='disk'>
    <driver name='file'/>
    <source file='/var/lib/xen/images/[Domain-4]/disk2'/>
    <target dev='xvda'/>
    </disk>
    <interface type='bridge' model='para'>
    <mac address='00:16:3e:0a:1b:2c'/>
    <script path='/etc/xen/scripts/vif-bridge'/>
    </interface>
    <graphics type='vnc'/>
    </devices>
    </domain>xen-2:/etc/xen/vm #

  2. #2

    Default Re: Xen domains don't start on reboot of Dom 0

    No takers, eh? Can someone at least tell me whether the /etc/xen/vm files are the only ones that should control this behavior? Would it help to have more of my configuration or log files? Is there a better forum for this question? I would have included logs but I'm not seeing anything that indicates any type of failure or that these domains are even trying to start... and the domains that start appear to do so without error unless I'm missing something.

    In any case, I appreciate the fact that a number of folks took a look at my post. If anyone has any ideas... any direction... even if you don't know for sure what would cause this, I'm open to suggestions. In the meantime I've spent too much time trying to get it to work "by the book" and I think I'll try writing a script to start the remaining VMs until I can find the correct solution. This is a production system so I would like for it to be a clean build, but I also need to get it deployed and I can't have 4 of my VMs requiring a manual start.

    Thanks all,
    Paul

  3. #3
    platinum NNTP User

    Default Re: Xen domains don't start on reboot of Dom 0

    pdoubek wrote:
    > I hope this is the correct forum for this question. I've built a Xen
    > server on top of SLED 10.2


    sorry, i didn't see your post before (because i know so little about
    Xen, i didn't open it), but see my previous post at:
    http://tinyurl.com/nxzdju

    --
    platinum

  4. #4
    NinjaTTT NNTP User

    Default Re: Xen domains don't start on reboot of Dom 0

    Take a look here
    You're missing (on_xend_stop shutdown) and (on_xend_start start) in xen managed domain setup.
    Another way to autostart is to sym. link from /etc/xen/auto to VM config in /etc/xen/vm

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •