some function are now in Proxmox.Utils instead, so we have to use that
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This checkbox had not effect whatsoever:
* if the VM was online and offline was selected, the migration would fail
with the message that the --online flag is needed for running VMs
* if the the VM was offline and online was selected, the migration would
happen offline anyway
by mistake we checked if me.vtype is 'qemu'
but the property is me.vmtype, so we would always show
restart mode
note that this error was purely cosmetic, behaviour was correct
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
for now we have to explicitely define the
onlineHelp: 'blockid'
string, so that the parser picks it up
in the future we should refactor that window, so that we define the
blockid when declaring the component
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
As we cannot migrate to the source node do not show it in the
migration window's node selector.
Fixes#1049 partly
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
this also fixes the problem that the method
Ext.ComponentQuery.query() was outputting a warning
since it did not know if it should perform a lookup
for a class name or a xtype
