From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: from tb-ob0.topicbox.com (tb-ob0.topicbox.com [64.147.108.117]) by inbox.vuxu.org (Postfix) with ESMTP id 4756021FB8 for ; Sun, 24 Nov 2024 13:23:02 +0100 (CET) Received: from tb-mx0.topicbox.com (tb-mx0.nyi.icgroup.com [10.90.30.73]) by tb-ob0.topicbox.com (Postfix) with ESMTP id 2550219FB0 for ; Sun, 24 Nov 2024 07:23:00 -0500 (EST) (envelope-from bounce.mMff1d99e10f2149161aa87a0d.r81958daa-7202-11ef-bbf2-18142b2d11b0@illumos.bounce.topicbox.com) Received: by tb-mx0.topicbox.com (Postfix, from userid 1132) id 3276C3DC45E; Sun, 24 Nov 2024 07:23:00 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lists.illumos.org; h= from:to:message-id:in-reply-to:references:date:mime-version :content-type:content-transfer-encoding:list-help:list-id :list-post:list-subscribe:reply-to:subject:list-unsubscribe; s= dkim-1; t=1732450980; x=1732537380; bh=DxGk/fnyBj1elmvr4v5RGXNj/ xPA0JYg9KAtfXRoKV4=; b=EhiaJgK84kPggBJlFLsFJeb60bCvPOPajL6ZszQwz WhwJ+9kKblUrIe2dGFTTb9JsO/xCITbMkG4Bu5pyt/3M0CcBik6hPVKAvx7uoogp B3P8el5QjLNY2BN7I9CqQNZbIlsVW8nS09VfXyr5KULCWZ+d9Tc6+lRWhiKL5Z2Q 2c= From: gernot.strasser@freenet.de To: illumos-discuss Message-Id: <17324509100.022FAa836.38570@composer.illumos.topicbox.com> In-Reply-To: <17322949160.CbAAe.625812@composer.illumos.topicbox.com> References: <17322949160.CbAAe.625812@composer.illumos.topicbox.com> Date: Sun, 24 Nov 2024 07:21:50 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=17324509101.2c2E3ea9.38570 Content-Transfer-Encoding: 7bit Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: ae7c7a1a-aa5e-11ef-ac2b-bad040decc0b Archived-At: =?UTF-8?B?PGh0dHBzOi8vaWxsdW1vcy50b3BpY2JveC5jb20vZ3JvdXBz?= =?UTF-8?B?L2Rpc2N1c3MvVDc0OWFkZTY5MmE2Mjc4OWYtTWZmMWQ5OWUxMGYyMTQ5MTYx?= =?UTF-8?B?YWE4N2EwZD4=?= List-Help: List-Id: "illumos-discuss" List-Post: List-Software: Topicbox v0 List-Subscribe: Precedence: list Reply-To: illumos-discuss Subject: [discuss] Re: bhyve, Server 2022 and vnc List-Unsubscribe: , Topicbox-Delivery-ID: 2:illumos:a9ae1d0a-2aea-11e7-965f-d98f9f16e227:81958daa-7202-11ef-bbf2-18142b2d11b0:Mff1d99e10f2149161aa87a0d:1:DYXYU2XaYsoyLIXFPzlCXlL52U9720VMBEP4G1D05Jw --17324509101.2c2E3ea9.38570 Date: Sun, 24 Nov 2024 07:21:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable After several test on different hardware platfoms I believe I found a patte= rn: - Win10, Server 2019 vnc input works as expected, both Intel or AMD hardware - Win11, Server 2022 and 2025=C2=A0 vnc input works as expected on AMD plat= forms - Win11, Server 2022 and 2025=C2=A0vnc input does not work on any Intel pla= tforms I tested Here is stripped down version of my above startup script, requiring only a = server2022.iso in case somebody wants to confirm/deny my findings: #!/bin/sh bootrom=3D/usr/share/bhyve/uefi-rom.bin WINDOWS_INSTALL_CD=3D/zones/iso/server2022.iso [ "$1" =3D "-k" ] || pfexec bhyvectl --vm=3Dwindows --destroy bhyve -H -w \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -s 0,hostbridge,model=3Di440fx \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -B "1,product=3DSmartOS HVM" \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -l bootrom,$bootrom \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -l com1,stdio \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -c 2 \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -m 4G \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -s 4:0,ahci-cd,$WINDOWS_INSTALL_= CD=C2=A0 \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -s 28,fbuf,vga=3Doff,tcp=3D0.0.0= .0:5801,w=3D1024,h=3D768,wait \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -s 29,xhci,tablet \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -s 31,lpc \ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 windows thx ------------------------------------------ illumos: illumos-discuss Permalink: https://illumos.topicbox.com/groups/discuss/T749ade692a62789f-Mf= f1d99e10f2149161aa87a0d Delivery options: https://illumos.topicbox.com/groups/discuss/subscription --17324509101.2c2E3ea9.38570 Date: Sun, 24 Nov 2024 07:21:50 -0500 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
After several test on different hardware platf= oms I believe I found a pattern:

- Win10, = Server 2019 vnc input works as expected, both Intel or AMD hardware
- Win11, Server 2022 and 2025  vnc input works as expected on AMD p= latforms
- Win11, Server 2022 and 2025 vnc input does not wo= rk on any Intel platforms I tested

Here is= stripped down version of my above startup script, requiring only a server2= 022.iso in case somebody wants to confirm/deny my findings:

#!/bin/sh
bootrom=3D/usr/share/bhyve/uefi= -rom.bin
WINDOWS_INSTALL_CD=3D/zones/iso/server2022.iso
[ "$1" =3D "-k" ] || pfexec bhyvectl --vm= =3Dwindows --destroy
bhyve -H -w \
 &n= bsp;      -s 0,hostbridge,model=3Di440fx \
        -B "1,product=3DSm= artOS HVM" \
       = ; -l bootrom,$bootrom \
      = ;  -l com1,stdio \
      = ;  -c 2 \
        -= m 4G \
        -s 4:0,ah= ci-cd,$WINDOWS_INSTALL_CD  \
    &= nbsp;   -s 28,fbuf,vga=3Doff,tcp=3D0.0.0.0:5801,w=3D1024,h=3D768,= wait \
        -s 29,xhc= i,tablet \
        -s 31= ,lpc \
        windows

thx
= --17324509101.2c2E3ea9.38570--