From: Jim Fehlig <jfehlig@novell.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] [xm] Fix vncdisplay for hvm guests
Date: Tue, 15 May 2007 17:14:25 -0600 [thread overview]
Message-ID: <464A3ED1.1010904@novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
'vncdisplay=N' in hvm config file is ignored when building qemu-dm
arguments.
xm create or xm new -> xm start with hvm config file containing
vnc=1
vncdisplay=5
results in '-vncunused' being passed to qemu-dm. There are several
approaches
for a fix - this patch defaults vncdisplay to None in xm options. It
currently defaults to 1 and is always included in the image config
created by configure_hvm() in tools/python/xen/xm/create.py. In xend
(tools/python/xen/xend/image.py - parseDeviceModelArgs), vncunused takes
precedence over vncdisplay.
This patch is against 3.1.0-testing but looks like problem exists in
unstable as well - even with recent changes to
tools/python/xen/xend/image.py when moving to qemu 0.9.0
Regards,
Jim
[-- Attachment #2: xm-vncunused.patch --]
[-- Type: text/x-patch, Size: 1066 bytes --]
# HG changeset patch
# User Jim Fehlig <jfehlig@novell.com>
# Date 1179270277 21600
# Node ID b6a56d49c45c7ae82851e04e6322f18aa6e2c481
# Parent aee991c7723a0c2fb88811c7c8b3cbdcb89f2bb9
'vncdisplay=N' in hvm config file is ignored when building qemu-dm arguments.
xm create or xm new -> xm start with hvm config file containing
vnc=1
vncdisplay=5
results in '-vncunused' being passed to qemu-dm. There are several approaches
for a fix - this patch defaults vncdisplay to None in xm options.
Signed-off-by: Jim Fehlig <jfehlig@novell.com>
diff -r aee991c7723a -r b6a56d49c45c tools/python/xen/xm/create.py
--- a/tools/python/xen/xm/create.py Wed May 09 16:34:47 2007 +0100
+++ b/tools/python/xen/xm/create.py Tue May 15 17:04:37 2007 -0600
@@ -474,7 +474,7 @@ gopts.var('vnclisten', val='',
use="""Address for VNC server to listen on.""")
gopts.var('vncunused', val='',
- fn=set_bool, default=1,
+ fn=set_bool, default=None,
use="""Try to find an unused port for the VNC server.
Only valid when vnc=1.""")
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2007-05-15 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 23:14 Jim Fehlig [this message]
2007-05-24 14:31 ` [PATCH] [xm] Fix vncdisplay for hvm guests Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2007-05-24 16:42 Jim Fehlig
2007-05-31 22:26 Jim Fehlig
2007-06-25 13:53 ` jd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=464A3ED1.1010904@novell.com \
--to=jfehlig@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.