Hello, 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. Does anybody know about this problem? I really need them all to start up to end. server1 ~ # xm info host : server1 release : 2.6.38-xen-r1 version : #2 SMP Thu May 19 15:30:19 CEST 2011 machine : x86_64 nr_cpus : 16 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2266 hw_caps : bfebfbff:28100800:00000000:00003b40:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 49143 free_memory : 23031 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .0 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : dom0_mem=4096M cpufreq=xen cc_compiler : gcc version 4.4.3 (Gentoo 4.4.3-r2 p1.2) cc_compile_by : cc_compile_domain : % cc_compile_date : Tue May 17 17:48:53 CEST 2011 xend_config_format : 4 Regards, Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> 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@lists.xensource.com http://lists.xensource.com/xen-users
I do nearly the same with delay of 2. Perhaps I should increase the delay. Thanks for info, so I am not alone. Am 23.05.2011 11:22, schrieb James Dingwall:>> 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@lists.xensource.com http://lists.xensource.com/xen-users
Hi, On Mon, May 23, Mike Fröhner wrote:> 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. > > Does anybody know about this problem? I really need them all to > start up to end.I''ve had the same problem after upgrade my Dom0 from opensuse 11.3 to opensuse11.4. My workaround was to increase the XENDOMAINS_CREATE_USLEEP parameter in the /etc/sysconfig/xendomains file. Maybe your distribution have an equivalent start script, where you can increase the time betweeen starting each domU. -- Best regards Dieter Bloms -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won''t use my address in the From field. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2nd reply with that issue. I also got an delay of 2, but it seems to be not enough. I''ll gonna increase it to 5. Thanks. Am 23.05.2011 11:34, schrieb Dieter Bloms:> Hi, > > On Mon, May 23, Mike Fröhner wrote: > >> 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. >> >> Does anybody know about this problem? I really need them all to >> start up to end. > > I''ve had the same problem after upgrade my Dom0 from opensuse 11.3 to > opensuse11.4. > > My workaround was to increase the XENDOMAINS_CREATE_USLEEP parameter in > the /etc/sysconfig/xendomains file. > > Maybe your distribution have an equivalent start script, where you can > increase the time betweeen starting each domU. > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users