From: Dan Hunsaker <danhunsa...@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 <danhunsa...@gmail.com>
---
bin/pvectl | 2 ++
1 file changed, 2 insertions(+)
diff --git a/bin/pvectl b/bin/pvectl
index f8ae3ad..8f2643d 100755
--- a/bin/pvectl
+++ b/bin/pvectl
@@ -74,6 +74,8 @@ my $cmddef = {
}],
start => [ 'PVE::API2::OpenVZ', 'vm_start', ['vmid'], { node => $nodename
}, $upid_exit],
+ suspend => [ 'PVE::API2::OpenVZ', 'vm_suspend', ['vmid'], { node =>
$nodename }, $upid_exit],
+ resume => [ 'PVE::API2::OpenVZ', 'vm_resume', ['vmid'], { node =>
$nodename }, $upid_exit],
shutdown => [ 'PVE::API2::OpenVZ', 'vm_shutdown', ['vmid'], { node =>
$nodename }, $upid_exit],
stop => [ 'PVE::API2::OpenVZ', 'vm_stop', ['vmid'], { node => $nodename },
$upid_exit],
mount => [ 'PVE::API2::OpenVZ', 'vm_mount', ['vmid'], { node => $nodename
}, $upid_exit],
--
1.9.1
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
