Hi,
Please see comments below.
On Thu, Jun 22, 2017 at 7:15 PM, Paul <paul(a)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(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users