xm: Fix xm start -c / --vncviewer

In xm start the --vncviewer option has no effect, instead -c tries to
both connect to the console and start vncviewer. Additionally, to
start vncviewer it uses the domid variable which is only defined a few
lines later. Thus xm start -c doesn't work at all.

This patch fixes both problems.

Signed-off-by: Kevin Wolf <kwolf@suse.de>
This commit is contained in:
Keir Fraser committed 2008-09-25 13:07:43 +01:00
1 parent 270fdae556
commit 0ae658ea9f
1 file changed
+4 -3
+4 -3
View File
@@ -1224,9 +1224,6 @@ def xm_start(args):
if console_autoconnect:
start_do_console(dom)
if console_autoconnect:
console.runVncViewer(domid, vncviewer_autopass, True)
try:
if serverType == SERVER_XEN_API:
server.xenapi.VM.start(get_single_vm(dom), paused)
@@ -1241,6 +1238,10 @@ def xm_start(args):
if domid == -1:
raise xmlrpclib.Fault(0, "Domain '%s' is not started" % dom)
if vncviewer:
console.runVncViewer(domid, vncviewer_autopass, True)
def xm_delete(args):
arg_check(args, "delete", 1)
dom = args[0]
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.