Jussi Hirvi wrote: > I have a virtual machine stack which was purely Centos 5.4 the last time > I rebooted and experienced this problem: one of the guests does not > start automatically after reboot. > > [root at farm1 xen]# pwd > /etc/xen > [root at farm1 xen]# ls -l auto > total 0 > lrwxrwxrwx 1 root root 8 Dec 11 17:25 name1 -> ../name1 > lrwxrwxrwx 1 root root 8 May 5 21:10 name2 -> ../name2 > lrwxrwxrwx 1 root root 8 Nov 26 11:43 name3 -> ../name3 > lrwxrwxrwx 1 root root 6 Oct 29 2009 name4 -> ../name4 > > (I retyped the names there.) > > [root at farm1 xen]# ls -l > total 88 > drwxr-xr-x 2 root root 4096 Apr 3 15:15 auto > -rw------- 1 root root 430 Dec 11 13:14 name1 > -rw------- 1 root root 610 May 7 12:07 name2 > -rw------- 1 root root 303 Nov 4 2009 name3 > -rw------- 1 root root 295 Oct 29 2009 name4 > (...) > > Here is one guest that works: > > name = "name3" > uuid = "958f8695-95e0-b43c-512e-2ca8950d35de" > maxmem = 900 > memory = 900 > vcpus = 1 > bootloader = "/usr/bin/pygrub" > on_poweroff = "destroy" > on_reboot = "restart" > on_crash = "restart" > disk = [ "tap:aio:/vm/mail3.img,xvda,w" ] > vif = [ "mac=00:16:36:4f:d6:11,bridge=xenbr1,script=vif-bridge" ] > ~ > > > The next one does not autostart (but starts ok with "xm create name2"). > This is the only guest that has two bridges. There is only 500M RAM, but > a third guest starts fine with 500M): > > name = "name2" > 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","mac=00:16:36:24:67:3d,bridge=xenbr1" > ] > ~ > > What might be the problem?? > Try to stop the xendomains and restart them: service xendomains stop If domains are configured to be saved then check /var/lib/xen/save to find the saved domains. Then start them again service xendomains start This at least gives you a faster way to check than actually rebooting your host. Needless to say, check the log files in /var/log/xen/ Theo