From: gernot.strasser@freenet.de
To: illumos-discuss <discuss@lists.illumos.org>
Subject: [discuss] Re: bhyve, Server 2022 and vnc
Date: Sun, 24 Nov 2024 07:21:50 -0500 [thread overview]
Message-ID: <17324509100.022FAa836.38570@composer.illumos.topicbox.com> (raw)
In-Reply-To: <17322949160.CbAAe.625812@composer.illumos.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
After several test on different hardware platfoms 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 platforms
- Win11, Server 2022 and 2025 vnc input does not work on any Intel platforms 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=/usr/share/bhyve/uefi-rom.bin
WINDOWS_INSTALL_CD=/zones/iso/server2022.iso
[ "$1" = "-k" ] || pfexec bhyvectl --vm=windows --destroy
bhyve -H -w \
-s 0,hostbridge,model=i440fx \
-B "1,product=SmartOS HVM" \
-l bootrom,$bootrom \
-l com1,stdio \
-c 2 \
-m 4G \
-s 4:0,ahci-cd,$WINDOWS_INSTALL_CD \
-s 28,fbuf,vga=off,tcp=0.0.0.0:5801,w=1024,h=768,wait \
-s 29,xhci,tablet \
-s 31,lpc \
windows
thx
------------------------------------------
illumos: illumos-discuss
Permalink: https://illumos.topicbox.com/groups/discuss/T749ade692a62789f-Mff1d99e10f2149161aa87a0d
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
[-- Attachment #2: Type: text/html, Size: 2531 bytes --]
next prev parent reply other threads:[~2024-11-24 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 17:01 [discuss] " gernot.strasser
2024-11-24 12:21 ` gernot.strasser [this message]
2024-11-29 8:31 ` [discuss] " gernot.strasser
2024-11-29 8:32 ` gernot.strasser
2024-12-13 3:41 ` mark.gilbert via illumos-discuss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17324509100.022FAa836.38570@composer.illumos.topicbox.com \
--to=gernot.strasser@freenet.de \
--cc=discuss@lists.illumos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).