Project

General

Profile

Actions

Feature #13844

closed

bhyve VNC server could differentiate VMs

Added by Andy Fiddaman 6 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
bhyve
Start date:
Due date:
% Done:

100%

Estimated time:
Difficulty:
Bite-size
Tags:
Gerrit CR:

Description

At present, the bhyve VNC server always presents the server name as bhyve, which makes it hard to differentiate them when one has multiple VNC clients open, since they all look the same
(here's an example browser tab using zadm's noVNC integration to connect to a Windows guest)


Files

vnctab.png (19.8 KB) vnctab.png Andy Fiddaman, 2021-06-01 09:54 AM
clipboard-202106011021-syemg.png (18.3 KB) clipboard-202106011021-syemg.png Andy Fiddaman, 2021-06-01 10:22 AM
Actions #1

Updated by Electric Monk 6 months ago

  • Gerrit CR set to 1526
Actions #2

Updated by Andy Fiddaman 6 months ago

And after the referenced gerrit change:
(The VM name here is windows)

Actions #3

Updated by Electric Monk 6 months ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

git commit 37fc8a1f73579421d8ec5a9ffdbfb472c71b6fac

commit  37fc8a1f73579421d8ec5a9ffdbfb472c71b6fac
Author: Andy Fiddaman <omnios@citrus-it.co.uk>
Date:   2021-06-04T10:32:56.000Z

    13844 bhyve VNC server could differentiate VMs
    Reviewed by: Jorge Schrauwen <sjorge@blackdot.be>
    Reviewed by: Dan Cross <cross@oxidecomputer.com>
    Approved by: Robert Mustacchi <rm@fingolfin.org>

Actions

Also available in: Atom PDF