From owner-freebsd-virtualization@freebsd.org Sat Nov 4 17:42:55 2017 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC874E5158A for ; Sat, 4 Nov 2017 17:42:55 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E94877051 for ; Sat, 4 Nov 2017 17:42:55 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id vA4Hgs5V001454; Sat, 4 Nov 2017 10:42:54 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id vA4HgsZP001453; Sat, 4 Nov 2017 10:42:54 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201711041742.vA4HgsZP001453@pdx.rh.CN85.dnsmgr.net> Subject: Re: VNC and non-US keymap in bhyve In-Reply-To: To: Farid Joubbi Date: Sat, 4 Nov 2017 10:42:54 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Nov 2017 17:42:56 -0000 > 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@freebsd.org