<html>
<body>
Thanks Thomas, <br>
<br>
it seems you were right. I followed the instructions to enable <br>
hugepages via kernel command line and after reboot vdsmd starts <br>
correctly. <br>
(I went back to 4.1.9 in between, added the kernel command line and <br>
upgraded to 4.2) <br>
<br>
The docs/release notes should mention it - or did I miss it? <br>
<br>
Am Dienstag, den 06.02.2018, 17:17 -0800 schrieb Thomas Davis: <br>
<font color="#000000">> sorry, make that: </font><br>
<font color="#000000">> </font><br>
<font color="#000000">> hugeadm --pool-list </font><br>
<font color="#000000">> Size Minimum Current Maximum Default </font><br>
<font color="#000000">> 2097152 1024 1024 1024 * </font><br>
<font color="#000000">> 1073741824 4 4 4 </font><br>
<font color="#000000">> </font><br>
<font color="#000000">> </font><br>
<font color="#000000">> On Tue, Feb 6, 2018 at 5:16 PM, Thomas Davis <<a href="mailto:tadavis@lbl.gov">tadavis@lbl.gov</a>> wrote: </font><br>
<font color="#000000">> > I found that you now need hugepage1g support. The error messages </font><br>
<font color="#000000">> > are wrong - it's not truly a libvirt problem, it's hugepages1g are </font><br>
<font color="#000000">> > missing for libvirt. </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > add something like: </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > default_hugepagesz=1G hugepagesz=1G hugepages=4 hugepagesz=2M </font><br>
<font color="#000000">> > hugepages=1024 to the kernel command line. </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > You can also do a 'yum install libhugetlbfs-utils', then do: </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > hugeadm --list </font><br>
<font color="#000000">> > Mount Point Options </font><br>
<font color="#000000">> > /dev/hugepages rw,seclabel,relatime </font><br>
<font color="#000000">> > /dev/hugepages1G rw,seclabel,relatime,pagesize=1G </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > if you do not see the /dev/hugepages1G listed, then vdsmd/libvirt </font><br>
<font color="#000000">> > will not start. </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > </font><br>
<font color="#000000">> > On Mon, Feb 5, 2018 at 5:49 AM, Frank Rothenstein <f.rothenstein@bo </font><br>
<font color="#000000">> > dden-kliniken.de> wrote: </font><br>
<font color="#000000">> > > Hi, </font><br>
<font color="#000000">> > > </font><br>
<font color="#000000">> > > I'm currently stuck - after upgrading 4.1 to 4.2 I cannot start </font><br>
<font color="#000000">> > > the </font><br>
<font color="#000000">> > > host-processes. </font><br>
<font color="#000000">> > > systemctl start vdsmd fails with following lines in journalctl: </font><br>
<font color="#000000">> > > </font><br>
<font color="#000000">> > > <snip> </font><br>
<font color="#000000">> > > </font><br>
<font color="#000000">> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: vdsm: Running wait_for_network </font><br>
<font color="#000000">> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: vdsm: Running run_init_hooks </font><br>
<font color="#000000">> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: vdsm: Running check_is_configured </font><br>
<font color="#000000">> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > sasldblistusers2[10440]: DIGEST-MD5 common mech free </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: Error: </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: One of the modules is not configured </font><br>
<font color="#000000">> > > to </font><br>
<font color="#000000">> > > work with VDSM. </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: To configure the module use the </font><br>
<font color="#000000">> > > following: </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: 'vdsm-tool configure [--module </font><br>
<font color="#000000">> > > module- </font><br>
<font color="#000000">> > > name]'. </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: If all modules are not configured </font><br>
<font color="#000000">> > > try to </font><br>
<font color="#000000">> > > use: </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: 'vdsm-tool configure --force' </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: (The force flag will stop the </font><br>
<font color="#000000">> > > module's </font><br>
<font color="#000000">> > > service and start it </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: afterwards automatically to load the </font><br>
<font color="#000000">> > > new </font><br>
<font color="#000000">> > > configuration.) </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: abrt is already configured for vdsm </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: lvm is configured for vdsm </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: libvirt is not configured for vdsm </font><br>
<font color="#000000">> > > yet </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: Current revision of multipath.conf </font><br>
<font color="#000000">> > > detected, preserving </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: Modules libvirt are not configured </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net </font><br>
<br>
<font color="#000000">> > > vdsmd_init_common.sh[10414]: vdsm: stopped during execute </font><br>
<font color="#000000">> > > check_is_configured task (task returned with error code 1). </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]: </font><br>
<font color="#000000">> > > vdsmd.service: control process exited, code=exited status=1 </font><br>
<font color="#000000">> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]: </font><br>
<font color="#000000">> > > Failed to </font><br>
<font color="#000000">> > > start Virtual Desktop Server Manager. </font><br>
<font color="#000000">> > > -- Subject: Unit vdsmd.service has failed </font><br>
<font color="#000000">> > > -- Defined-By: systemd </font><br>
<font color="#000000">> > > -- Support: <a href="http://lists.freedesktop.org/mailman/listinfo/systemd">http://lists.freedesktop.org/mailman/listinfo/systemd</a> </font><br>
<font color="#000000">> > > -devel </font><br>
<font color="#000000">> > > -- </font><br>
<font color="#000000">> > > -- Unit vdsmd.service has failed. </font><br>
<BR />
<BR />
<font face="Arial" style="font-size: 12px; font-family: Arial;"><span style="font-size: 12px;"></span></font><div><font face="arial" size="2"><font><font><font><br>Frank Rothenstein </font></font></font><font><font><br><br>Systemadministrator<br>Fon: +49 3821 700 125<br>Fax: </font>+49 3821 700 190</font></font></div><div><font><font face="arial" size="2">Internet: www.bodden-kliniken.de<br>E-Mail: f.rothenstein@bodden-kliniken.de<br></font><br></font><span style="font-size: 12px; font-family: arial;"><img src="cid:547f8827.f9d4cce7.png.d413ca20"></span><br><font face="arial" style="font-size: 12px; font-family: Arial;"><span style="font-size: 12px;">_____________________________________________<br>BODDEN-KLINIKEN Ribnitz-Damgarten GmbH</span><br><span style="font-size: 12px;">Sandhufe 2</span><br><span style="font-size: 12px;">18311 Ribnitz-Damgarten</span><br><br><font size="1">Telefon: 03821-700-0<br>Telefax: 03821-700-240</font><br><br><font size="1">E-Mail: info@bodden-kliniken.de <br>Internet: http://www.bodden-kliniken.de</font><br><br><span style="font-size: 12px;">Sitz: Ribnitz-Damgarten, Amtsgericht: Stralsund, HRB 2919, Steuer-Nr.: 079/133/40188</span><br><span style="font-size: 12px;">Aufsichtsratsvorsitzende: Carmen Schröter, Geschäftsführer: Dr. Falko Milski, MBA</span><br><br><font size="1" style="font-size: 12px;">Der Inhalt dieser E-Mail ist ausschließlich für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der <br>vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, beachten Sie bitte, dass jede <br>Form der Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser E-Mail unzulässig ist. <br>Wir bitten Sie, sofort den Absender zu informieren und die E-Mail zu löschen. </font><br><span style="font-size: 12px;"><br> © BODDEN-KLINIKEN Ribnitz-Damgarten GmbH 2017</span><br><span style="font-size: 12px;">*** Virenfrei durch Kerio Mail Server und SOPHOS Antivirus ***</span></font></div><BR />
</body>
</html>