VNC and non-US keymap in bhyve

[Rodney W. Grimes]

> Hello,
> 
> I use bhyve and have a problem with non-US keymap and the VNC server.
> This is a bug that was reported at least to FreeNAS and was fixed a few
> weeks ago according to the bug report here:
> https://bugs.freenas.org/issues/24450
> 
> When will this fix come into FreeBSD?
> How does the process work for changes into FreeNAS and then into FreeBSD?

For this specific instance Marcelo, the person working the bug from the
FreeNAS side, is also a member of the FreeBSD developers group working
on bhyve so he tends to make sure his fixes get brought over.


> Or is it that the change was first made into FreeBSD and then from there
> found its way into FreeNAS?

I am unclear in this case, but from reading the full text of the
bugs.freenas.org report it is clear that he is working on both
FreeBSD and FreeNAS to resolve the issue.   

> I could not find this information anywhere other than that FreeNAS is based
> on FreeBSD.

I think if you read the bug report carefully you should find the
following text excerpt:
-- begin excerpt --

 Updated by Marcelo Araujo 5 months ago

    Priority changed from No priority to Important
    Status changed from Unscreened to Investigation
    Target version set to 49

Hi all,

It is a know issue with bhyve, I'm working to import libvncserver to replace the current implementation of rfb on FreeBSD. It will take a bit of time as I need first commit it on FreeBSD and then merge it to FreeNAS.

The process to commit on FreeBSD can take a bit of time, because we have a review process and a merge process as well.

But I will keep you guys updated about my progress.

Best,
-- end excerpt --
-- begin excerpt --
Updated by Marcelo Araujo about 1 month ago

    Target version changed from 11.2 to 11.1
    Status changed from Fix In Progress to Ready For Release

I added libhyve-remote and all the bits necessary to improve VNC server.
Python bits were reviewed by williamgr and C bits by kris.
-- begin excerpt --

In this second one 11.2 and 11.1 are refering to FreeBSD releases,
I do believe this is fixed in FreeBSD 11.1.

-- 
Rod Grimes                                                 rgrimes at freebsd.org