From nobody Thu Aug 17 17:31:09 2023 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RRYKD2Prcz4mW00 for ; Thu, 17 Aug 2023 18:23:12 +0000 (UTC) (envelope-from justin@rapidcity.net) Received: from filter2-outbound.ispservices.us (filter2-outbound.ispservices.us [64.251.188.104]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RRYKC084nz3QxL for ; Thu, 17 Aug 2023 18:23:10 +0000 (UTC) (envelope-from justin@rapidcity.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of justin@rapidcity.net designates 64.251.188.104 as permitted sender) smtp.mailfrom=justin@rapidcity.net; dmarc=pass (policy=quarantine) header.from=rapidcity.net Received: from localhost (localhost [127.0.0.1]) by filter2.ispservices.us (Postfix) with ESMTP id D237A2DC5101 for ; Thu, 17 Aug 2023 12:23:08 -0600 (MDT) X-Virus-Scanned: by SpamTitan at ispservices.us Received: from filter2.ispservices.us (localhost [127.0.0.1]) by filter2.ispservices.us (Postfix) with ESMTP id E57E12DC6232 for ; Thu, 17 Aug 2023 12:19:32 -0600 (MDT) Received: from smtpfarm-node1.gwis.io (smtpfarm-node1.gwis.io [64.251.188.93]) by filter2.ispservices.us (Postfix) with ESMTP id 1796B2DC7290 for ; Thu, 17 Aug 2023 11:31:21 -0600 (MDT) Received: from mail-proxy-ha2.gwis.io (mail-proxy-ha2.gwis.io [64.251.188.30]) by smtpfarm-node1.gwis.io (Postfix) with ESMTP id 008E02239D for ; Thu, 17 Aug 2023 11:31:21 -0600 (MDT) Received: from smtpclient.apple (c-98-237-207-210.hsd1.wa.comcast.net [98.237.207.210]) (Authenticated sender: justin@enetis.net) by mail-proxy-ha2.gwis.io (Postfix) with ESMTPSA id CD84F80379 for ; Thu, 17 Aug 2023 11:31:20 -0600 (MDT) From: Justin England Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: RFB doesn't use client's SetPixelFormat Message-Id: Date: Thu, 17 Aug 2023 10:31:09 -0700 To: "virtualization@freebsd.org" X-Mailer: Apple Mail (2.3731.600.7) X-Spamd-Result: default: False [-3.40 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[rapidcity.net,quarantine]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:64.251.188.0/23]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.251.188.104:from]; PREVIOUSLY_DELIVERED(0.00)[virtualization@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[virtualization@FreeBSD.org]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:6580, ipnet:64.251.176.0/20, country:US]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[64.251.188.104:from]; FREEFALL_USER(0.00)[justin]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4RRYKC084nz3QxL Greetings, I am using FreeBSD 13.2-STABLE and have recently attempted to get = noVNC=E2=80=99s web based VNC client to work with my bhyve VNC consoles, = but immediately realized that the colors are not correctly displayed = where essentially the reds and blues are reversed. After doing some research, that is exactly what is happening. Web = browsers seem to use BGR colors where bhyve=E2=80=99s RFB uses RGB. = Reading through the mailing lists / forums of noVNC, this appears to be = a common issue and usually means that the embedded RFB server does not = properly use the pixel format that the client requests. After quickly going through the RFB protocol and bhyve=E2=80=99s rfb.c = source, sure enough, when bhyve receives a SetPixelFormat from the = client, it basically ignores it and moves on. ( = rfb_recv_set_pixfmt_msg() ) At this point, I=E2=80=99m not sure what to do next. Does anybody have a work around for this? Is this something that will be added in a future release? Should I file a bug report as recommended by the noVNC developers? I appreciate any help I can get with this. Thanks, Justin England