vnc-listen value ignored in /etc/xen/xend-config.sxp

Bug #1643983 reported by Trev Peterson
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xen (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When configuring Xen host the vnc-listen value seems to be completely ignored. Whether I enter '0.0.0.0', 0.0.0.0 (no quotes as in the old conf files), or the specific ip of the interface '192.168.2.53' it only binds to the localhost IP 127.0.0.1.

PID/Program name
tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 3623/qemu-system-x8

Revision history for this message
Trev Peterson (trev-advanced-reality) wrote :

This should be against package xen-utils-common but I'm unable to select that.

affects: ubuntu → xen-common (Ubuntu)
affects: xen-common (Ubuntu) → xen (Ubuntu)
Revision history for this message
Trev Peterson (trev-advanced-reality) wrote :

After several attempts at using apport-collect and failing, I'm just attaching the config file here manually. Let me know if I can provide any other info or config files necessary to troubleshoot.

FYI, the package names we can assign to this do not seem acceptable to apport-collect (in specific xen-common and xen are not shown as loaded on my system so I can not attach apport info to this bug as a result).

Revision history for this message
Trev Peterson (trev-advanced-reality) wrote :
Revision history for this message
Trev Peterson (trev-advanced-reality) wrote :

root@cloud2:/etc/xen# netstat -nlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 3623/qemu-system-x8

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xen (Ubuntu):
status: New → Confirmed
Revision history for this message
Phillip Susi (psusi) wrote :

I had no trouble with this under 14.04 but since upgrading to 16.04, the IP address part is ignored and it always uses 127.0.0.1, so I can not connect over the network. It does seem to respect the port part though.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.