Project

General

Profile

Bug #26990

Fix regression that prevented VNC connection

Added by Bill Rousseau 11 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
Blocks Until Resolved
Assignee:
Marcelo Araujo
Category:
Middleware
Target version:
Seen in:
Sprint:
Severity:
New
Backlog Priority:
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

When trying to connect to VM created with 11.1-RC3 via VNC, an error is generated stating the connection is refused. This did not occur under 11.1-RC1 with the same hardware and network setup. Was using fresh install of 11.1-RC3.


Related issues

Related to FreeNAS - Bug #27019: Launching a VM crashes the (legacy) Web-GUIClosed: Duplicate2017-12-05

History

#1 Updated by Dru Lavigne 11 months ago

  • Status changed from Unscreened to 15

Bill: please attach a debug (System -> Advanced -> Save Debug).

#2 Updated by Bill Rousseau 11 months ago

I did not happen to save a debug (will be sure to next time). If you are unable to reproduce, I can try to do so when I return from business travel later this week.

#3 Updated by Dru Lavigne 11 months ago

  • Status changed from 15 to Unscreened
  • Assignee changed from Release Council to Marcelo Araujo

Bill: please send it along when you can as it will assist the developer.

#4 Updated by Darren VanBuren 11 months ago

I'm having a similar problem after upgrading to 11.1-RC3 today.
I was able to find the following log entries when I try to boot up a VM that I was not able to connect to with VNC (lines are wrapped manually for clarity):

[2017/12/05 02:24:30] (DEBUG) VMService.run():153 - ====> NIC_ATTACH: igb0
[2017/12/05 02:24:30] (DEBUG) VMService.run():229 - Starting bhyve: bhyve -H -w -c 12 -m 4096 -s 0:0,hostbridge -s 31,lpc -l com1,/dev/nmdm2A -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd
  -s 3,virtio-net,tap1,mac=fe:ed:00:42:69:d2 -s 29,fbuf,vncserver,tcp=172.16.69.161:5902,w=1280,h=1024,,wait -s 30,xhci,tablet -s 4,virtio-blk,/dev/zvol/datapool/vm/archvm/os
  -s 5,ahci-cd,/mnt/datapool/share/ISOs/archlinux-2017.09.01-x86_64.iso 2_archvm
[2017/12/05 02:24:30] (DEBUG) VMService.run():248 - archvm: 04/12/2017 18:24:30 ListenOnTCPPort: Can't assign requested address

Then, when trying to debug this I looked at at netstat, and there was nothing listening on that port, so I'm not sure I understand what would be causing this "Can't assign requested address error".

Let me know if there's anywhere else I can look for more details.

#5 Updated by Marcelo Araujo 11 months ago

Dru Lavigne wrote:

Bill: please send it along when you can as it will assist the developer.

Hi,

Thanks, there is a regression and I'm checking it now. I can reproduce it.

Darren VanBuren wrote:

I'm having a similar problem after upgrading to 11.1-RC3 today.
I was able to find the following log entries when I try to boot up a VM that I was not able to connect to with VNC (lines are wrapped manually for clarity):

[...]

Then, when trying to debug this I looked at at netstat, and there was nothing listening on that port, so I'm not sure I understand what would be causing this "Can't assign requested address error".

Let me know if there's anywhere else I can look for more details.

Thanks! There is a regression and I'm checking it now. I can reproduce it too.

#6 Updated by Marcelo Araujo 11 months ago

  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Blocks Until Resolved
  • Target version set to 11.1

#7 Updated by Tobias Müllauer 11 months ago

FYI

I have some time problem to conect to VM when it starts up. No connection but when i try agen it start to work. i feels like first time waking the VNC to life =P Nothing big things.

#8 Updated by Marcelo Araujo 11 months ago

  • Status changed from Screened to Ready For Release

Hi,

I made a fix for another ticket on libhyve-remote 0.1.4 that created a memory leak, this regression breaks vnc.
I did rollback today libhyve-remote to 0.1.3 and it is working now.

Best,

#9 Updated by Dru Lavigne 11 months ago

  • Subject changed from VNC Connection fails to Fix regression that prevented VNC connection

#10 Updated by Patrick M. Hausen 10 months ago

Is there a way to manually fit that library into a running RC3 installation as a quick workaround?

Thanks,
Patrick

#11 Updated by Nick Wolff 10 months ago

  • Needs QA changed from Yes to No
  • QA Status Test Passes FreeNAS added
  • QA Status deleted (Not Tested)

#12 Updated by Dru Lavigne 10 months ago

  • Related to Bug #27019: Launching a VM crashes the (legacy) Web-GUI added

#13 Updated by Chris Schuler 10 months ago

Another possible side effect of this. When I would connect to the vnc port I configured, I would get a connection refused like the issue states above. But as I dug into it I noticed the VNC port I entered into the gui(e.g. 5901) was not what the vnc web button would try to connect to, nor what the process was listening on. The actual port was 100 less, based on where the vncweb button took me and netstat. (5901 was actually 5801). This happened when the was port set via the legacy or new gui. When I tried to connect to this port I would get "The connection closed unexpectedly" in vncviewer 6.11.

I even used a port of 0 to let it auto assign the port and the same thing was observed. (semi-related, using 0 in the new gui did not auto-assign, I had to use the legacy gui for that)

#14 Updated by Dru Lavigne 10 months ago

  • Status changed from Ready For Release to Resolved

Also available in: Atom PDF