To keep existing spice connections alive.

and make sure we do not open inotify handle twice

This is the preferred/default event loop for AnyEvent. This is faster and
better tested than the native perl loop.

Signed-off-by: Tobias Doerffel <tobias.doerffel@ed-chemnitz.de>

Signed-off-by: Tobias Doerffel <tobias.doerffel@ed-chemnitz.de>

It's now possible to make VZDump only send a mail in case of a failure.
Signed-off-by: Tobias Doerffel <tobias.doerffel@ed-chemnitz.de>

add check if START Parameter is set in FILE: /etc/default/pve-manager
If START="no" NO VM will start if pve-manager start is called
If START!="no" or not present, VMs will use the boot_at_start Flag
Signed-off-by: Wolfgang Link <wolfgang@linksystems.org>

Signed-off-by: Stefan Priebe <s.priebe@profihost.ag>

older versions are considered insecure, for example search for "Poodle"-Attac

With the new mobile interface, we need to implement UI changes in two
places.  This lets us simplify our mobile interface so it isn't cluttered
with options that mobile browsers can't easily handle, usually due to size.
This patch implements Suspend and Resume of VMs and CTs via the mobile
web UI.
Signed-off-by: Dan Hunsaker <danhunsaker@gmail.com>

The PVE2 API supports suspend/resume of VMs (and now CTs), but the web UI
doesn't make these options available.  This patch adds Suspend and Resume
items to the CmdMenus of OpenVZ and QEMU guests.  I considered adding the
options to the toolbar, but since it is already pretty full, I opted
against doing so for the moment.  Perhaps the various startup options can
be combined into a dropdown menu similar to how the console options are
set up, and the various shutdown opitons combined into another.  That
would provide the necesarry space to add the Suspend and Resume options
there.

This patch also provides descriptions for Suspend and Resume tasks in the
task logs, bringing full suspend/resume support to the web GUI.
Signed-off-by: Dan Hunsaker <danhunsaker@gmail.com>

Now that the API supports CT suspend/resume, it makes sense to have pvectl
support it, too.  It *does* use different names than vzctl does, but it
seems to make sense to be consistent with the API naming in a PVE utility.
Signed-off-by: Dan Hunsaker <danhunsaker@gmail.com>

Suspend/resume support for VMs has been in the PVE2 API for some time,
but even though vzctl supports suspend/resume (what they call checkpoint/
restore), the API doesn't yet support suspend/resume for CTs.  This patch
adds that support.
Signed-off-by: Dan Hunsaker <danhunsaker@gmail.com>

Signed-off-by: Stanislav German-Evtushenko <ginermail@gmail.com>