Bug 203198

Summary:	HVM should not use static VNC port numbers
Product:	[Fedora] Fedora	Reporter:	Stephen Tweedie <sct>
Component:	xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED RAWHIDE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	berrange, bstein, katzj
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-09-21 17:53:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	150224

Description Stephen Tweedie 2006-08-18 20:50:12 UTC

Description of problem:
Running a fully-virt HVM domain with VNC results by default in a VNC port being
opened on port 5900+$DOMAINID.  This is unscalable past the first 100 domains
created on a host, beyond which point the port will clash with the primary X
server port.

This default is good for developers who constantly reboot but not suitable for
production.

Version-Release number of selected component (if applicable):
xen-3.0.2-23

How reproducible:
100%

Additional info:
The domain ID is available from xenstore and there is a xen option in current
upstream, "vncunused=1", to let it choose the first free port.  This probably
wants to be enabled by default.

Comment 1 Jeremy Katz 2006-08-22 21:25:37 UTC

We need to ensure whatever we do here is consistent for paravirt guests as well

Comment 2 Jeremy Katz 2006-09-21 17:53:33 UTC

There's support for vncunused for both PV and FV guests that can be set both in
the xen config and with libvirt (and xenguest-install)