[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-users] domUs don't boot correctly to end
> since I upgraded from xen-2.6.34-r1 / xen-4.0.0 to xen-2.6.38 / > xen-4.1.0 on gentoo, I got the problem, that if I boot many domU in a > short time (like 10 domU in 5 seconds) some of them won't start the > login-shell after initing local. It is also not possible to access them > via ssh. At my last test, 3 of 9 domU got that problem. After "xm > destroy domU" and "xm start domU" again they booted correctly and > started the login-shell. I didn't have exactly these symptoms but I found that starting so many domUs at once could cause problems because of such heavy disk i/o. I fixed this by modifying /etc/init.d/xendomains and adding a sleep after the xl create. Diff is below and should apply cleanly assuming it doesn't get corrupted. If you want a longer delay between the domU starts then define BOOTDELAY=XX in /etc/conf.d/xendomains. James $ diff -u /usr/portage/app-emulation/xen-tools/files/xendomains.initd-r2 /etc/init.d/xendomains --- /usr/portage/app-emulation/xen-tools/files/xendomains.initd-r2 2011-04-05 22:25:03.000000000 +0100 +++ /etc/init.d/xendomains 2011-05-15 15:34:18.820083366 +0100 @@ -58,9 +58,9 @@ if ! is_running ${name} ; then ebegin " Starting domain ${name}" if using_screen ; then - ${screen_cmd} screen -t ${name} xl create ${dom} -c + ${screen_cmd} screen -t ${name} xl create ${dom} -c ; sleep ${BOOTDELAY:=5} else - xl create --quiet ${dom} + xl create --quiet ${dom} ; sleep ${BOOTDELAY:=5} fi eend $? else This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |