vm shutdown long delay is a problem for users of pools
This is a multipart message in MIME format. ------=_NextPart_000_0079_01D2EB83.89CE5690 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, Shutting down VM's in the portal with the red downfacing arrow takes quite some time (about 90 seconds). I read this is mainly due to a 60 second delay in the ovirt-guest-agent. I got used to right-click and use "power off" instead of "shutdown", which is fine. My users make use of VM in a VM-pool. They get assigned a VM and after console disconnect the VM shuts down (default recommended behavior). My issue is that the users stays assigned to this VM for the full 90 seconds and cannot do "power off". Suppose he disconnected by accident, he has to wait 90 seconds until he is assigned to the pool again until he can connect to another VM. My questions are: - Is it possible to decrease the time delay of a VM shutdown? 90 seconds is quite a lot, 10 seconds should be enough - Is it possible for normal users to use "power off"? - Is it possible to "unallocate" the user from a VM if it is powering down? So he can allocate another VM Kind regards, Paul ------=_NextPart_000_0079_01D2EB83.89CE5690 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 = (filtered medium)"><style><!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:#954F72; text-decoration:underline;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:36.0pt; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} span.EmailStyle17 {mso-style-type:personal; font-family:"Calibri",sans-serif; color:windowtext;} span.EmailStyle18 {mso-style-type:personal; font-family:"Calibri",sans-serif; color:#1F497D;} span.EmailStyle19 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} /* List Definitions */ @list l0 {mso-list-id:1079979482; mso-list-type:hybrid; mso-list-template-ids:-963102632 -2055051548 68354051 68354053 68354049 = 68354051 68354053 68354049 68354051 68354053;} @list l0:level1 {mso-level-start-at:88; mso-level-number-format:bullet; mso-level-text:-; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:"Calibri",sans-serif; mso-fareast-font-family:Calibri;} @list l0:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:"Courier New";} @list l0:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Wingdings;} @list l0:level4 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Symbol;} @list l0:level5 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:"Courier New";} @list l0:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Wingdings;} @list l0:level7 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Symbol;} @list l0:level8 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:"Courier New";} @list l0:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt; font-family:Wingdings;} ol {margin-bottom:0cm;} ul {margin-bottom:0cm;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></head><body lang=3DNL = link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p = class=3DMsoNormal><span lang=3DEN-US = style=3D'color:#1F497D'>Hi,<o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Shutting = down VM’s in the portal with the red downfacing arrow takes quite = some time (about 90 seconds). I read this is mainly due to a 60 second = delay in the ovirt-guest-agent. I got used to right-click and use = “power off” instead of “shutdown”, which is = fine.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>My users = make use of VM in a VM-pool. They get assigned a VM and after console = disconnect the VM shuts down (default recommended behavior). My issue is = that the users stays assigned to this VM for the full 90 seconds and = cannot do “power off”. Suppose he disconnected by accident, = he has to wait 90 seconds until he is assigned to the pool again until = he can connect to another VM. <o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>My = questions are:<o:p></o:p></span></p><p class=3DMsoListParagraph = style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if = !supportLists]><span lang=3DEN-US style=3D'color:#1F497D'><span = style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New = Roman"'> = </span></span></span><![endif]><span lang=3DEN-US = style=3D'color:#1F497D'>Is it possible to decrease the time delay of a = VM shutdown? 90 seconds is quite a lot, 10 seconds should be = enough<o:p></o:p></span></p><p class=3DMsoListParagraph = style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if = !supportLists]><span lang=3DEN-US style=3D'color:#1F497D'><span = style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New = Roman"'> = </span></span></span><![endif]><span lang=3DEN-US = style=3D'color:#1F497D'>Is it possible for normal users to use = “power off”?<o:p></o:p></span></p><p = class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 = lfo1'><![if !supportLists]><span lang=3DEN-US = style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<span = style=3D'font:7.0pt "Times New = Roman"'> = </span></span></span><![endif]><span lang=3DEN-US = style=3D'color:#1F497D'>Is it possible to “unallocate” the = user from a VM if it is powering down? So he can allocate another = VM<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Kind = regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US = style=3D'color:#1F497D'><o:p> </o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US = style=3D'color:#1F497D'>Paul<o:p></o:p></span></p></div></body></html> ------=_NextPart_000_0079_01D2EB83.89CE5690--
Hi, Please see comments below. On Thu, Jun 22, 2017 at 7:15 PM, Paul <paul@kenla.nl> wrote:
Hi,
Shutting down VM’s in the portal with the red downfacing arrow takes quite some time (about 90 seconds). I read this is mainly due to a 60 second delay in the ovirt-guest-agent. I got used to right-click and use “power off” instead of “shutdown”, which is fine.
My users make use of VM in a VM-pool. They get assigned a VM and after console disconnect the VM shuts down (default recommended behavior). My issue is that the users stays assigned to this VM for the full 90 seconds and cannot do “power off”. Suppose he disconnected by accident, he has to wait 90 seconds until he is assigned to the pool again until he can connect to another VM.
My questions are:
- Is it possible to decrease the time delay of a VM shutdown? 90 seconds is quite a lot, 10 seconds should be enough
Is ovirt-guest-agent installed on all pool's VMs? Consider installing ovirt-guest-agent in all VMs in your Pool to decrease the time taken for the VM shutdown. - Is it possible for normal users to use “power off”?
There is no option in UserPortal to power-off a VM but you can try to click twice (sequential clicks) on the 'shutdown' button. Two sequential shutdown requests are handled in oVirt as "power off".
- Is it possible to “unallocate” the user from a VM if it is powering down? So he can allocate another VM
You can consider assigning two VMs per each user, if possible of-course (via WebAdmin->edit Pool -> and set "Maximum number of VMs per user" field to "2") so that way while one VM is still shutting down, the user can switch and connect to a second VM without waiting. Another option is to create a pool with a different policy for console disconnecting so that the VM won't shutdown each time the user close the console (via WebAdmin->Pool->Console tab->"Console Disconnect Action"). Consider changing this field to "Lock screen" or "Logout user" instead of "shutdown virtual machine". This policy will avoid accidentally console disconnection waiting each time...but on the other hand the VM state will remain as is since no shutdown occurs, so it really depends on your requirements. Regards, Sharon
Kind regards,
Paul
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multipart message in MIME format. ------=_NextPart_000_00F2_01D2F006.E05802E0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Sharon, Thanks for your comments. My findings on those: 1. Yes all VMs have ovirt-guest-agent installed and active, = shutdown time is still about 90 seconds. Any other way to reduce this? I = see in the logs =E2=80=9CJun 28 11:49:03 pool python: Shutdown scheduled = for Wed 2017-06-28 11:50:03 CEST, use 'shutdown -c' to cancel.=E2=80=9D = And then a wait of 60 seconds. Is it possible to adjust this delay? 2. Clicking twice works. Thanks for the tip! 3. =20 a. More VMs per user: yes, could be a good option b. I have some trouble with the =E2=80=9Cconsole disconnect = action=E2=80=9D and filed a bug for it last week [1]. Any disconnect = action (except shutdown) combined with =E2=80=9Cstrict user = checking=E2=80=9D (security wise recommended) blocks and depletes pool = resources and in my opinion jeopardizes the pool functionality. I am = curious what your thoughts are on this. Kind regards, Paul [1]: https://bugzilla.redhat.com/show_bug.cgi?id=3D1464396 =20 From: Sharon Gratch [mailto:sgratch@redhat.com]=20 Sent: dinsdag 27 juni 2017 19:04 To: Paul <paul@kenla.nl> Cc: users <users@ovirt.org> Subject: Re: [ovirt-users] vm shutdown long delay is a problem for users = of pools =20 Hi, Please see comments below. =20 On Thu, Jun 22, 2017 at 7:15 PM, Paul <paul@kenla.nl = <mailto:paul@kenla.nl> > wrote: Hi, Shutting down VM=E2=80=99s in the portal with the red downfacing arrow = takes quite some time (about 90 seconds). I read this is mainly due to a = 60 second delay in the ovirt-guest-agent. I got used to right-click and = use =E2=80=9Cpower off=E2=80=9D instead of =E2=80=9Cshutdown=E2=80=9D, = which is fine. =20 My users make use of VM in a VM-pool. They get assigned a VM and after = console disconnect the VM shuts down (default recommended behavior). My = issue is that the users stays assigned to this VM for the full 90 = seconds and cannot do =E2=80=9Cpower off=E2=80=9D. Suppose he = disconnected by accident, he has to wait 90 seconds until he is assigned = to the pool again until he can connect to another VM.=20 =20 My questions are: - Is it possible to decrease the time delay of a VM shutdown? = 90 seconds is quite a lot, 10 seconds should be enough =E2=80=8B=E2=80=8B =E2=80=8BIs ovirt-guest-agent installed on all pool's VMs? Consider = installing ovirt-guest-agent in all VMs in your Pool to decrease the = time taken for the VM shutdown.=20 =20 - Is it possible for normal users to use =E2=80=9Cpower = off=E2=80=9D? =E2=80=8BThere is no option in UserPortal to power-off a VM but you can=20 =E2=80=8Btry to click twice (sequential clicks) on the 'shutdown' = button. Two sequential shutdown requests are handled in oVirt as "power = off". - Is it possible to =E2=80=9Cunallocate=E2=80=9D the user from = a VM if it is powering down? So he can allocate another VM =E2=80=8BYou can consider assigning two VMs per each user, if possible = of-course (via WebAdmin->edit Pool -> and set "Maximum number of VMs per = user" field to "2") so that way while one VM is still shutting down, the = user can switch and connect to a second VM without waiting. Another option is to create a pool with a different policy for console = disconnecting so that the VM won't shutdown each time the user close the = console (via WebAdmin->Pool->Console tab->"Console Disconnect Action"). = Consider changing this field to "Lock screen" or "Logout user" instead = of "shutdown virtual machine".=20 This policy will avoid accidentally console disconnection waiting each = time...but on the other hand the VM state will remain as is since no = shutdown occurs, so it really depends on your requirements. Regards, Sharon =20 Kind regards, =20 Paul _______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org>=20 http://lists.ovirt.org/mailman/listinfo/users =20 ------=_NextPart_000_00F2_01D2F006.E05802E0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta = name=3DGenerator content=3D"Microsoft Word 15 (filtered = medium)"><style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:"Comic Sans MS"; panose-1:3 15 7 2 3 3 2 2 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman",serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:36.0pt; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman",serif;} p.gmail-m-3539624712128639787msolistparagraph, = li.gmail-m-3539624712128639787msolistparagraph, = div.gmail-m-3539624712128639787msolistparagraph {mso-style-name:gmail-m_-3539624712128639787msolistparagraph; mso-margin-top-alt:auto; margin-right:0cm; mso-margin-bottom-alt:auto; margin-left:0cm; font-size:12.0pt; font-family:"Times New Roman",serif;} span.gmail-hoenzb {mso-style-name:gmail-hoenzb;} span.EmailStyle19 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif; mso-fareast-language:EN-US;} @page WordSection1 {size:612.0pt 792.0pt; margin:70.85pt 70.85pt 70.85pt 70.85pt;} div.WordSection1 {page:WordSection1;} /* List Definitions */ @list l0 {mso-list-id:1046368022; mso-list-type:hybrid; mso-list-template-ids:520528076 68354063 68354073 68354075 68354063 = 68354073 68354075 68354063 68354073 68354075;} @list l0:level1 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level2 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level3 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l0:level4 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level5 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level6 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} @list l0:level7 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level8 {mso-level-number-format:alpha-lower; mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level9 {mso-level-number-format:roman-lower; mso-level-tab-stop:none; mso-level-number-position:right; text-indent:-9.0pt;} ol {margin-bottom:0cm;} ul {margin-bottom:0cm;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></head><body lang=3DNL link=3Dblue = vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span = lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'>Hi Sharon,<o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'>Thanks for your comments. My findings on = those:<o:p></o:p></span></p><p class=3DMsoListParagraph = style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if = !supportLists]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'><span style=3D'mso-list:Ignore'>1.<span = style=3D'font:7.0pt "Times New = Roman"'> = </span></span></span><![endif]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'>Yes all VMs have ovirt-guest-agent installed = and active, shutdown time is still about 90 seconds. Any other way to = reduce this? I see in the logs =E2=80=9CJun 28 11:49:03 pool python: = Shutdown scheduled for Wed 2017-06-28 11:50:03 CEST, use 'shutdown -c' = to cancel.=E2=80=9D And then a wait of 60 seconds. Is it possible to = adjust this delay?<o:p></o:p></span></p><p class=3DMsoListParagraph = style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if = !supportLists]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'><span style=3D'mso-list:Ignore'>2.<span = style=3D'font:7.0pt "Times New = Roman"'> = </span></span></span><![endif]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'>Clicking twice works. Thanks for the = tip!<o:p></o:p></span></p><p class=3DMsoListParagraph = style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if = !supportLists]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'><span style=3D'mso-list:Ignore'>3.<span = style=3D'font:7.0pt "Times New = Roman"'> = </span></span></span><![endif]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'><o:p> </o:p></span></p><p = class=3DMsoListParagraph = style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 = lfo1'><![if !supportLists]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'><span style=3D'mso-list:Ignore'>a.<span = style=3D'font:7.0pt "Times New = Roman"'> = </span></span></span><![endif]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'>More VMs per user: yes, could be a good = option<o:p></o:p></span></p><p class=3DMsoListParagraph = style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 = lfo1'><![if !supportLists]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'><span style=3D'mso-list:Ignore'>b.<span = style=3D'font:7.0pt "Times New Roman"'> = </span></span></span><![endif]><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'>I have some trouble with the = =E2=80=9Cconsole disconnect action=E2=80=9D and filed a bug for it last = week [1]. Any disconnect action (except shutdown) combined with = =E2=80=9Cstrict user checking=E2=80=9D (security wise recommended) = blocks and depletes pool resources and in my opinion jeopardizes the = pool functionality. I am curious what your thoughts are on = this.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'>Kind regards,<o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'>Paul<o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'>[1]:</span><span lang=3DEN-US> </span><span = lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'><a = href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1464396">https://bu= gzilla.redhat.com/show_bug.cgi?id=3D1464396</a><o:p></o:p></span></p><p = class=3DMsoNormal><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;= mso-fareast-language:EN-US'><o:p> </o:p></span></p><p = class=3DMsoNormal><b><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span><= /b><span lang=3DEN-US = style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'> Sharon = Gratch [mailto:sgratch@redhat.com] <br><b>Sent:</b> dinsdag 27 juni 2017 = 19:04<br><b>To:</b> Paul <paul@kenla.nl><br><b>Cc:</b> users = <users@ovirt.org><br><b>Subject:</b> Re: [ovirt-users] vm shutdown = long delay is a problem for users of pools<o:p></o:p></span></p><p = class=3DMsoNormal><o:p> </o:p></p><div><div><p class=3DMsoNormal = style=3D'margin-bottom:12.0pt'><span style=3D'font-family:"Comic Sans = MS"'>Hi,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span = style=3D'font-family:"Comic Sans MS"'>Please see comments = below.<o:p></o:p></span></p></div><div><p = class=3DMsoNormal><o:p> </o:p></p><div><p class=3DMsoNormal>On Thu, = Jun 22, 2017 at 7:15 PM, Paul <<a href=3D"mailto:paul@kenla.nl" = target=3D"_blank">paul@kenla.nl</a>> wrote:<o:p></o:p></p><blockquote = style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm = 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'>Hi,</span><o:p></o:p></p><p = class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'>Shutting down VM=E2=80=99s in the = portal with the red downfacing arrow takes quite some time (about 90 = seconds). I read this is mainly due to a 60 second delay in the = ovirt-guest-agent. I got used to right-click and use =E2=80=9Cpower = off=E2=80=9D instead of =E2=80=9Cshutdown=E2=80=9D, which is = fine.</span><o:p></o:p></p><p class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'> </span><o:p></o:p></p><p = class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'>My users make use of VM in a = VM-pool. They get assigned a VM and after console disconnect the VM = shuts down (default recommended behavior). My issue is that the users = stays assigned to this VM for the full 90 seconds and cannot do = =E2=80=9Cpower off=E2=80=9D. Suppose he disconnected by accident, he has = to wait 90 seconds until he is assigned to the pool again until he can = connect to another VM. </span><o:p></o:p></p><p class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'> </span><o:p></o:p></p><p = class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'>My questions = are:</span><o:p></o:p></p><p = class=3Dgmail-m-3539624712128639787msolistparagraph><span lang=3DEN-US = style=3D'color:#1F497D'>-</span><span lang=3DEN-US = style=3D'font-size:7.0pt;color:#1F497D'> &nb= sp; </span><span lang=3DEN-US = style=3D'color:#1F497D'>Is it possible to decrease the time delay of a = VM shutdown? 90 seconds is quite a lot, 10 seconds should be = enough</span><o:p></o:p></p></div></div></blockquote><div><div><p = class=3DMsoNormal>=E2=80=8B=E2=80=8B<span style=3D'font-family:"Comic = Sans MS"'><o:p></o:p></span></p></div><div><p = class=3DMsoNormal>=E2=80=8B<span style=3D'font-family:"Comic Sans = MS"'>I<span style=3D'color:black'>s ovirt-guest-agent installed on all = pool's VMs? Consider installing ovirt-guest-agent in all VMs in your = Pool to decrease the time taken for the VM shutdown. = </span><o:p></o:p></span></p></div><p = class=3DMsoNormal><o:p> </o:p></p></div><blockquote = style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm = 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p = class=3Dgmail-m-3539624712128639787msolistparagraph><span lang=3DEN-US = style=3D'color:#1F497D'>-</span><span lang=3DEN-US = style=3D'font-size:7.0pt;color:#1F497D'> &nb= sp; </span><span lang=3DEN-US = style=3D'color:#1F497D'>Is it possible for normal users to use = =E2=80=9Cpower = off=E2=80=9D?</span><o:p></o:p></p></div></div></blockquote><div><div><p = class=3DMsoNormal>=E2=80=8B<span style=3D'font-family:"Comic Sans = MS"'>There is no option in UserPortal to power-off a VM but you can = <o:p></o:p></span></p></div><div><p class=3DMsoNormal>=E2=80=8B<span = style=3D'font-family:"Comic Sans MS"'>try to click twice (sequential = clicks) on the 'shutdown' button. Two sequential shutdown requests are = handled in oVirt as "power = off".<o:p></o:p></span></p></div></div><blockquote = style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm = 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p = class=3Dgmail-m-3539624712128639787msolistparagraph><span lang=3DEN-US = style=3D'color:#1F497D'>-</span><span lang=3DEN-US = style=3D'font-size:7.0pt;color:#1F497D'> &nb= sp; </span><span lang=3DEN-US = style=3D'color:#1F497D'>Is it possible to =E2=80=9Cunallocate=E2=80=9D = the user from a VM if it is powering down? So he can allocate another = VM</span><o:p></o:p></p></div></div></blockquote><div><p = class=3DMsoNormal style=3D'margin-bottom:12.0pt'>=E2=80=8B<span = style=3D'font-family:"Comic Sans MS"'>You can consider assigning two VMs = per each user, if possible of-course (via WebAdmin->edit Pool -> = and set "Maximum number of VMs per user" field to = "2") so that way while one VM is still shutting down, the user = can switch and connect to a second VM without = waiting.<o:p></o:p></span></p></div><div><p class=3DMsoNormal = style=3D'margin-bottom:12.0pt'><span style=3D'font-family:"Comic Sans = MS"'>Another option is to create a pool with a different policy for = console disconnecting so that the VM won't shutdown each time the user = close the console (via WebAdmin->Pool->Console = tab->"Console Disconnect Action"). Consider changing this = field to "Lock screen" or "Logout user" instead of = "shutdown virtual machine". <br>This policy will avoid = accidentally console disconnection waiting each time...but on the other = hand the VM state will remain as is since no shutdown occurs, so it = really depends on your requirements.<o:p></o:p></span></p></div><div><p = class=3DMsoNormal><span style=3D'font-family:"Comic Sans = MS"'>Regards,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span = style=3D'font-family:"Comic Sans = MS"'>Sharon<o:p></o:p></span></p></div><blockquote = style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm = 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'> </span><o:p></o:p></p><p = class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'>Kind = regards,</span><o:p></o:p></p><p class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'> </span><span = style=3D'color:#888888'><o:p></o:p></span></p><p class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span = lang=3DEN-US style=3D'color:#1F497D'>Paul</span><span = style=3D'color:#888888'><o:p></o:p></span></p></div></div><p = class=3DMsoNormal = style=3D'margin-bottom:12.0pt'><br>______________________________________= _________<br>Users mailing list<br><a = href=3D"mailto:Users@ovirt.org">Users@ovirt.org</a><br><a = href=3D"http://lists.ovirt.org/mailman/listinfo/users" = target=3D"_blank">http://lists.ovirt.org/mailman/listinfo/users</a><o:p><= /o:p></p></blockquote></div><p = class=3DMsoNormal><o:p> </o:p></p></div></div></div></body></html> ------=_NextPart_000_00F2_01D2F006.E05802E0--
Hi, On Wed, 28 Jun 2017 12:05:46 +0200 "Paul" <paul@kenla.nl> wrote:
Hi Sharon,
Thanks for your comments. My findings on those:
1. Yes all VMs have ovirt-guest-agent installed and active, shutdown time is still about 90 seconds. Any other way to reduce this? I see in the logs “Jun 28 11:49:03 pool python: Shutdown scheduled for Wed 2017-06-28 11:50:03 CEST, use 'shutdown -c' to cancel.” And then a wait of 60 seconds. Is it possible to adjust this delay?
I've got good news for you... and, of course, some not so good news... The delay can be configured in engine by engine-config. The corresponding value is 'VmGracefulShutdownTimeout' and is in seconds (default is 30 seconds). I.e. you can run the following to disable the delay. # engine-config --set VmGracefulShutdownTimeout=0 The not so good news is that on linux (which is your case if I understood correctly) the delay only works by minutes and the value of VmGracefulShutdownTimeout is rounded *up* to whole minutes. That is anything between 1-59 seconds is turned into 60 seconds. Hope that helps, Tomas
2. Clicking twice works. Thanks for the tip!
3.
a. More VMs per user: yes, could be a good option
b. I have some trouble with the “console disconnect action” and filed a bug for it last week [1]. Any disconnect action (except shutdown) combined with “strict user checking” (security wise recommended) blocks and depletes pool resources and in my opinion jeopardizes the pool functionality. I am curious what your thoughts are on this.
Kind regards,
Paul
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1464396
From: Sharon Gratch [mailto:sgratch@redhat.com] Sent: dinsdag 27 juni 2017 19:04 To: Paul <paul@kenla.nl> Cc: users <users@ovirt.org> Subject: Re: [ovirt-users] vm shutdown long delay is a problem for users of pools
Hi,
Please see comments below.
On Thu, Jun 22, 2017 at 7:15 PM, Paul <paul@kenla.nl <mailto:paul@kenla.nl> > wrote:
Hi,
Shutting down VM’s in the portal with the red downfacing arrow takes quite some time (about 90 seconds). I read this is mainly due to a 60 second delay in the ovirt-guest-agent. I got used to right-click and use “power off” instead of “shutdown”, which is fine.
My users make use of VM in a VM-pool. They get assigned a VM and after console disconnect the VM shuts down (default recommended behavior). My issue is that the users stays assigned to this VM for the full 90 seconds and cannot do “power off”. Suppose he disconnected by accident, he has to wait 90 seconds until he is assigned to the pool again until he can connect to another VM.
My questions are:
- Is it possible to decrease the time delay of a VM shutdown? 90 seconds is quite a lot, 10 seconds should be enough
Is ovirt-guest-agent installed on all pool's VMs? Consider installing ovirt-guest-agent in all VMs in your Pool to decrease the time taken for the VM shutdown.
- Is it possible for normal users to use “power off”?
There is no option in UserPortal to power-off a VM but you can
try to click twice (sequential clicks) on the 'shutdown' button. Two sequential shutdown requests are handled in oVirt as "power off".
- Is it possible to “unallocate” the user from a VM if it is powering down? So he can allocate another VM
You can consider assigning two VMs per each user, if possible of-course (via WebAdmin->edit Pool -> and set "Maximum number of VMs per user" field to "2") so that way while one VM is still shutting down, the user can switch and connect to a second VM without waiting.
Another option is to create a pool with a different policy for console disconnecting so that the VM won't shutdown each time the user close the console (via WebAdmin->Pool->Console tab->"Console Disconnect Action"). Consider changing this field to "Lock screen" or "Logout user" instead of "shutdown virtual machine". This policy will avoid accidentally console disconnection waiting each time...but on the other hand the VM state will remain as is since no shutdown occurs, so it really depends on your requirements.
Regards,
Sharon
Kind regards,
Paul
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users
-- Tomáš Golembiovský <tgolembi@redhat.com>
participants (3)
-
Paul -
Sharon Gratch -
Tomáš Golembiovský