From owner-freebsd-virtualization@freebsd.org Sun Oct 29 21:45:28 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 87E88E4D49D for ; Sun, 29 Oct 2017 21:45:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 74B0868436 for ; Sun, 29 Oct 2017 21:45:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9TLjSvH080652 for ; Sun, 29 Oct 2017 21:45:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 218662] bhyve exposes CPU feature SDBG to guests, causing guest panic on OpenBSD 6.1 Date: Sun, 29 Oct 2017 21:45:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: freebsd@bdragon.rtk0.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 29 Oct 2017 21:45:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218662 Brandon Bergren changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd@bdragon.rtk0.net --- Comment #2 from Brandon Bergren --- Created attachment 187571 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187571&action= =3Dedit VMM patch (from HardenedBSD) This affects me too. HardenedBSD has the most elegant fix at https://github.com/HardenedBSD/hardenedBSD/commit/e76fcb77ba82649bc6aed808a= f06d6d2184847d8 -- I have attached a copy of the patch. I can confirm that with just that p= atch I can successfully run OpenBSD 6.1 in bhyve on my machine that is otherwise affected by this problem. I believe it makes a lot more sense than emulating the MSR (i.e. what https://github.com/HardenedBSD/hardenedBSD/commit/cc91b57f4d1dabddfbf8b1e76= 55 does.) My SuperMicro C7Z170-OCE board actually has bios options for enabling and disabling the silicon debug status and lock bit, so if I were to misconfigu= re my bios, the countermeasure would have actually been effective (when applie= d to the host). I can verify though that with it disabled in the bios, it is indeed locked down, without needing the countermeasure. root@narwhal:~ # kldload cpuctl root@narwhal:~ # cpucontrol -m 0xc80 /dev/cpuctl0 MSR 0xc80: 0x00000000 0x40000000 I still think the countermeasure is a good idea though! https://github.com/HardenedBSD/hardenedBSD/commit/da28546280938e19e866d2e11= a9ccda3c4ca82fa is a version of the countermeasure that checks the virtualization flag too = so it will avoid tickling the bhyve limitation while still providing protectio= n. But at the very least, filter the SDBG feature flag. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Nov 3 05:53:14 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 199E9E6CCDF for ; Fri, 3 Nov 2017 05:53:14 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id E270A7D3B8 for ; Fri, 3 Nov 2017 05:53:13 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 5C85C16E6F; Fri, 3 Nov 2017 05:53:13 +0000 (UTC) Date: Fri, 3 Nov 2017 05:53:13 +0000 To: freebsd-virtualization@freebsd.org From: "editor_callfortesting.org (Michael Dexter)" Reply-to: D5473+333+79492675d52ac1ab@reviews.freebsd.org Subject: [Differential] D5473: ATA/ATAPI6 device emulation in bhyve Message-ID: <3d38786660bf72447074babd08b7352f@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D5473: ATA/ATAPI6 device emulation in bhyve X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: ZmQ1YjBmNDNhNWVhZDYwNjJmNTU3Y2FmMjRkIFn8BEk= MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Nov 2017 05:53:14 -0000 ZWRpdG9yX2NhbGxmb3J0ZXN0aW5nLm9yZyBhZGRlZCBhIGNvbW1lbnQuCgoKICBJbiBteSB0ZXN0 aW5nLCB0aGlzIGFwcGVhcnMgdG8gYmUgYmFzZWQgb24gRnJlZUJTRCAxMC4xLCB3aGljaCBpcyB3 ZWxsIHN1cHBvcnRlZCBieSBBSENJIGVtdWxhdGlvbi4gU3VwcG9ydGluZyBiYWNrIHRvIDUuMCBv ciBlYXJsaWVyIHdvdWxkIG1ha2UgdGhpcyBtdWNoIG1vcmUgdXNlZnVsLgoKUkVWSVNJT04gREVU QUlMCiAgaHR0cHM6Ly9yZXZpZXdzLmZyZWVic2Qub3JnL0Q1NDczCgpFTUFJTCBQUkVGRVJFTkNF UwogIGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9zZXR0aW5ncy9wYW5lbC9lbWFpbHByZWZl cmVuY2VzLwoKVG86IGlhdGVhY2EsIGdyZWhhbiwgdHljaG9uLCBuZWVsLCBtYXYKQ2M6IGVkaXRv cl9jYWxsZm9ydGVzdGluZy5vcmcsIGZyZWVic2QtdmlydHVhbGl6YXRpb24tbGlzdAo= From owner-freebsd-virtualization@freebsd.org Sat Nov 4 15:45:47 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 41425E4E003 for ; Sat, 4 Nov 2017 15:45:47 +0000 (UTC) (envelope-from djfarid@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C678172E31 for ; Sat, 4 Nov 2017 15:45:46 +0000 (UTC) (envelope-from djfarid@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id y80so6477760wmd.0 for ; Sat, 04 Nov 2017 08:45:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Ux+GzHFcY4F3lteN+4LTZ61iUYIR/ajQ67gZmxAUZ3I=; b=IBRIA9FxGaExfUwngG4bJNg3dAtK1oEv+wUqcPCj1XK+jYJBojnLI4C9KxsmpD/B7N 0ICbR+CjXlp9feq8ZuRrH6ejWrGQ0bwRBZ7IBJFttpzcA+vpe9qaP6u/qafTY7pNZerb p3W2nqzHxW0nUoS6ZlIPkObJU0DHiWNYcs+LZ7zElGPRJKH1v+rDW386XBsgDQeOXNlR 3exA1P7kynJOdtZlkq0sTsnHhigswkjXt5HcNkiZ482fPQiocFZbA7GeNWga+bagNyjc OVQFmMi+Q24AzRC1W1yPZrsSD4nnLOQq8m2350Ou7RBkr4GNr3Httvutv0S33l+TUF4E h+yQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Ux+GzHFcY4F3lteN+4LTZ61iUYIR/ajQ67gZmxAUZ3I=; b=PqfKXoPansft0LxSBxU8Xm9+Erq2U7EWnqemau7h2qP8kl0FfPvp3cLb5mkIUlI83Q /Gxz8AH+kTlfebyBgS10SZAQOBGZmOQmuEy6Z4R/+KvFiw8OlJ7u7RwTY7xn9DqjtL9+ sTlg2wBd7mK9HQqRdEbzi+Y6foVTo11+J159IEm5lb3s/bIFO8/+cnmWW/iyYE7gWKjM CZHSLXrHBULzcMGq5Wxj7F1bucPRGlkBQsROuX1Z6+3sMUpSRx50HGebVCaKJWwhuH9B k/g01n4NmIx4hrsqVSRkKQIPXU5OvF1DDECA7W+uQpb3BONtH9DToDRf4pX16Zoot9Bw eb7g== X-Gm-Message-State: AMCzsaXWrUUYlYJdymRFF/wxvpO0aSr516PW17Xd6xutojBIRD0OX88d Tq7ZbHEw3cZCCVPl9AZEyaAVJpyabt4i5D0DPmYqOVT2 X-Google-Smtp-Source: ABhQp+T7uuVF626nRU1YtzmDlBhMddAd738uG2tQiZfFRgBgQtEXFLmvg2Puk9kzQ28x5hzvyCWDvMiUFfdBPTMUja8= X-Received: by 10.80.231.145 with SMTP id b17mr13432152edn.94.1509810344209; Sat, 04 Nov 2017 08:45:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.139.6 with HTTP; Sat, 4 Nov 2017 08:45:43 -0700 (PDT) From: Farid Joubbi Date: Sat, 4 Nov 2017 16:45:43 +0100 Message-ID: Subject: VNC and non-US keymap in bhyve To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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 15:45:47 -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? Or is it that the change was first made into FreeBSD and then from there found its way into FreeNAS? I could not find this information anywhere other than that FreeNAS is based on FreeBSD. 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 From owner-freebsd-virtualization@freebsd.org Sat Nov 4 18:55:58 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 6F16BE52C9B for ; Sat, 4 Nov 2017 18:55:58 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D7387D01C for ; Sat, 4 Nov 2017 18:55:58 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-pf0-x232.google.com with SMTP id z11so4680116pfk.4 for ; Sat, 04 Nov 2017 11:55:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=KOMhUxNi9BneWqj3PHioQomddskK8nnCFcF8xeXMQ/E=; b=DCqL4A3vUaRJ7NGa9/XPD871ifpWp+JdEAKTTXONdF3UfoRN3Fhf7326pihnsAYLlD ZoOj1LMbmVAVLh/mjMSqBV2gO3GaQadTttzCjq0L1N5KmWR+vy8ly27Kjy4Px0SbVVzG v5oOhAxCUh7+qHUKImBMroMPTuWCbzpppjF8fKzoFSfsw/kxYgz7gpGCIAh1fX0/q6eD uop6TjEX/ezHBVLCDUnevDHLD0PWgCRnxPVs0evHiivonBwewPBbH1GkT/e5xEf4oHLk M1fZu2FNrx9A4KxTZ1KmDqMU0VXU5OTs1MrrCbJTHhBBmAOSBnvXf27gZC9b47LF7/dy fEVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=KOMhUxNi9BneWqj3PHioQomddskK8nnCFcF8xeXMQ/E=; b=WtNC5VFjQVIt8YOtbwqh6CsosOw6+eNU6tYuSCGjWxrSiCT+dc3UxUY7yDCxuzJ4jj fEzPXRx0MdU1OLk6ziZWaBON/nArQKtM94p/PLTaFhbsG73WM1FtyIcVAc1lq2OhhH5b PvCNPxTU1ymOgcE0pgbENnDXzmIseeaTcyrLuYtwDW1ptFP2HVQ3nRs46whCzaOjoAdI yHyTzjbkyHXpGmfvv4bBFzWZgmdzyvFMO40pCAwLiSFceAEvNm8Vn0bALmufeWQUUbLw B8b0NnQSAm1PN6TFhW4PkqF3mRQXrVK3Ei0S/vzHjiInLWICIBGCsOPmqadO83yGTdbJ 8JrA== X-Gm-Message-State: AMCzsaXpPr8yXR6kKrvhg5EMm0jrDHTzX9pwxQOg34o4vEuXmloS4uio s9JdRNkhzV/JD2ofGx4ejISFASGW X-Google-Smtp-Source: ABhQp+TknOMhMYV/uqMvdq4x6F8ViFSQgWcH6qSaxqVf4geYisr8fk1fWkEXFJKcaIO32aftnqnqGg== X-Received: by 10.159.206.198 with SMTP id x6mr10243852plo.35.1509821757509; Sat, 04 Nov 2017 11:55:57 -0700 (PDT) Received: from ?IPv6:2601:2c2:880:6cc:f151:cc3:5b51:8a24? ([2601:2c2:880:6cc:f151:cc3:5b51:8a24]) by smtp.gmail.com with ESMTPSA id 66sm15318247pgh.31.2017.11.04.11.55.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Nov 2017 11:55:56 -0700 (PDT) To: freebsd-virtualization From: Rajil Saraswat Subject: Onboard USB controller passthrough Message-ID: <6721cf76-3d40-fa2c-4b84-8882f92fd6f1@gmail.com> Date: Sat, 4 Nov 2017 13:55:52 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US 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 18:55:58 -0000 Hello, I have an Supermicro X10DRi-T motherboard which has 2 EHCI controllers and 1 xHCI controller. I want to pass one of the EHCI controller to the VM running Ubuntu. Unfortunately, the VM immediately quits when i pass the USB controller. I am using vm-bhye to manage the VM's running on FreeBSD 11.1. The controllers looks like this # pciconf -l -BbcV ppt2@pci0:0:26:0 ppt2@pci0:0:26:0: class=0x0c0320 card=0x72708086 chip=0x8d2d8086 rev=0x05 hdr=0x00 bar [10] = type Memory, range 32, base 0xc6134000, size 1024, enabled cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14 cap 13[98] = PCI Advanced Features: FLR TP Any idea how to fix this? Thanks, Rajil From owner-freebsd-virtualization@freebsd.org Sat Nov 4 20:53:53 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 D102DE55739 for ; Sat, 4 Nov 2017 20:53:53 +0000 (UTC) (envelope-from djfarid@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 63A0981D5D for ; Sat, 4 Nov 2017 20:53:53 +0000 (UTC) (envelope-from djfarid@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id b9so7535495wmh.0 for ; Sat, 04 Nov 2017 13:53:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tlAqe9Lmqji/1A2f/Zf82ZjpJ3qqFAOx1t3SB33tVtM=; b=ljqrzeqp4xsiQ2I3ldzzR9SYHSrpHRaunnku+VP9A3QskhVKcwDGRmWGFI6tPhxyJg cizhOaHp0vQOq+n+qulSK64neW5r1/CiIyOIgFD/4FnemgWTaPMbMbwTyTDpds5jfDZ8 jFPo46/Hkl7L/RNUr1urbeDvs81hqBLOcDA7f7BG8BAijdzvoIFSKR+S/pYzPTH8J3BD qPz9hMEifG4BmkTMtBZsTLZyoxmXEc0WO5sEaoQG6kxzRO2SN4qmhD3wXQ6i8S+ria60 hgOIhGXoghphZ9z4Amz0qlOCzL2+qenfp/8AlWtmvasnCfotIVXHaWHB2FViAoCxV5o3 sLfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tlAqe9Lmqji/1A2f/Zf82ZjpJ3qqFAOx1t3SB33tVtM=; b=gnd5SiULa7Dy/LbmEJ6P2CoDSTaTUz9pS24flBQ/sNnj/xE3NYjuUVeF/9WYrCelqN 8LNWzgiGPpbApgcCXGAO4jEJ8OzbAkmIqshkScLjBa/uuM5Kcm8/hpME9Gix443qZTOr 7QpsmkSB9cl+CWZ5FaXvM5m3XBNFnlrPFLmvVQM82VE9uHZ5iSyrhiUq1UBwj4zhag6F 6z1I3NJd5fQtiAlQm46oHrQo2Wjsmmxz9Fy1/LSY7dzEzRYtDqgcU5cB7BARm35/GvJM x85f2SIzpNc1BPd5I4IFbHz1ljdETc/pPfte+g1JS9Q9UKmstzHvRmHzFy1UucMHmzcv CWAQ== X-Gm-Message-State: AMCzsaWPK1Dn1VdoAMOjuoPgWm4eAGDbwhqGzRKBrelIEzGb2utNeX5n oYI/4MwULHrBxCRtUT6/z1DdlrvDfaT/miRne/8JZA== X-Google-Smtp-Source: ABhQp+Q1ekTylGjeQHUHX7BJnT+Xh9VVD7VEkMnnRghfGjv45Poob2CwNAtnvHvJxJFnn8HqakDD1id730kEA/166t8= X-Received: by 10.80.214.136 with SMTP id r8mr14214875edi.17.1509828830536; Sat, 04 Nov 2017 13:53:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.139.6 with HTTP; Sat, 4 Nov 2017 13:53:49 -0700 (PDT) In-Reply-To: <201711041742.vA4HgsZP001453@pdx.rh.CN85.dnsmgr.net> References: <201711041742.vA4HgsZP001453@pdx.rh.CN85.dnsmgr.net> From: Farid Joubbi Date: Sat, 4 Nov 2017 21:53:49 +0100 Message-ID: Subject: Re: VNC and non-US keymap in bhyve To: "Rodney W. Grimes" Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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 20:53:53 -0000 Thanks for the reply! I'm running 11.1 Release. The fix is not there yet at least. I read the whole bug report and understood that he was involved on both sides. My question was a bit more general about the changes coming from FreeNAS to FreeBSD and the other way around. Is there a way for me to see when this particular change, or some other change that I might be interested about in the future will be available in FreeBSD release, stable or current? On Sat, Nov 4, 2017 at 6:42 PM, Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > 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 >