because we also do not set KRBD flag by default.

Currently,if we have vms on lvm on top of iscsi,

pve-manager service start them too early at host boot,
before open-iscsi daemon, and vm don't start.
Reported-by: Philippe Guy <ph.guy@decidem.fr>
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>

and increase git release key retrieval.
(ceph.com git seem to be quite slow currently)
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>

This is necessary because CPU are not hot-plug-able and memory are hot-plug-able.
also this will be useful for the new resource window.

The check used was completely wrong and so the startall and stopall
API calls touched HA managed service, which they shouldn't.

Using the vm_is_ha_managed call from the HA stack fixes that.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

When adding the new LXC config format we forgot to adapt the
get_start_stop_list and do s/pve.startup/onboot/

This fixes that qemu VMs were started always before LXC CTs,
irregardless of the defined order.

This also let's us simplify the surrounding code and reduce code
reuse.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

correct brand name

As we, for now, default to exclude ext5 from our build it's better
to make an check if its directory exists, and only then allow to
load from it. Else we can get errors on proxy startup, and when
someone passes the ext5 parameter.

Also make a indent/whitespace cleanup.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

verify_blockdev_path didn't check the result of abs_path
causing commands like `pveceph createosd bad/path` to error
with a meaningless "Use of uninitialized value" message.