CentOS - Oct 2010 - Xen guest not starting automatically

I have a xen system with four guest OS's, (see list below). When I 
reboot the host, other guests autostart normally, but mail2 does not. I 
have found no explanation for this.

The host and all guests are CentOS 5.5.

[root at farm1 xen]# ls -l /etc/xen/auto
total 0
lrwxrwxrwx 1 root root 8 Dec 11  2009 dawit -> ../dawit
lrwxrwxrwx 1 root root 8 May  5 21:10 mail2 -> ../mail2
lrwxrwxrwx 1 root root 8 Nov 26  2009 mail3 -> ../mail3
lrwxrwxrwx 1 root root 6 Oct 29  2009 ns2 -> ../ns2

Here is my config for the problem guest:

cat /etc	/xen/mail2
name = "mail2"
uuid = "68e33ec6-ef36-9eac-27d7-65a709684551"
maxmem = 500
memory = 500
vcpus = 1
bootloader = "/usr/bin/pygrub"
# kernel = "/var/lib/xen/boot_kernel.5g5MLq"
# ramdisk = "/var/lib/xen/boot_ramdisk.1pSOoP"
# extra = "ro root=LABEL=/ console=xvc0"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
disk = [ "tap:aio:/vm/mail2.img,xvda,w" ]
vif = [ "mac=00:16:36:24:67:3c,bridge=xenbr0,script=vif-bridge" ]


- Jussi

-- 
Jussi Hirvi * Green Spot
Topeliuksenkatu 15 C * 00250 Helsinki * Finland
Tel. +358 9 493 981 * Mobile +358 40 771 2098 (only sms)
jussi.hirvi at greenspot.fi * http://www.greenspot.fi

Am 30.10.10 14:46, schrieb Jussi Hirvi:
> The host and all guests are CentOS 5.5.
> 
> [root at farm1 xen]# ls -l /etc/xen/auto
> total 0
> lrwxrwxrwx 1 root root 8 Dec 11  2009 dawit -> ../dawit
> lrwxrwxrwx 1 root root 8 May  5 21:10 mail2 -> ../mail2
> lrwxrwxrwx 1 root root 8 Nov 26  2009 mail3 -> ../mail3
> lrwxrwxrwx 1 root root 6 Oct 29  2009 ns2 -> ../ns2
SELinux turned on? What does ls -Z in that directory say? Do you get AVC
denials in the audit log?

Ralph

On 30.10.2010 15:46, Jussi Hirvi wrote:
> I have a xen system with four guest OS's, (see list below). When I
> reboot the host, other guests autostart normally, but mail2 does not. I
> have found no explanation for this.
>
> The host and all guests are CentOS 5.5.
Have you checked relevant log files:
-  dmesg
- /var/log/xen/*

Usually if one of the guests doesn't start without explanation it should 
give something out. Brute force fix would be to delete the guest and 
recreate it.

-vpk