Bug 203198 - HVM should not use static VNC port numbers
Summary: HVM should not use static VNC port numbers
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: FC6Blocker
TreeView+ depends on / blocked
 
Reported: 2006-08-18 20:50 UTC by Stephen Tweedie
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-21 17:53:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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)


Note You need to log in before you can comment on or make changes to this bug.