I'm trying to set up a Windows 7 bhyve guest with sysutils/vm-bhyve on FreeBSD 13.1-RELEASE-p1. After running
The config data was generated with the UEFI template from https://klarasystems.com/articles/from-0-to-bhyve-on-freebsd-13-1/. I've previously used this template to set up a Windows 10 guest without any mouse problems.
vm install windows7-vm win7-pro.iso
and vncviewer localhost
the setup process starts and the mouse pointer appears on screen but does not move with my mouse. Moving the mouse just moves a small black dot around the screen and there's no response to mouse clicks.The config data was generated with the UEFI template from https://klarasystems.com/articles/from-0-to-bhyve-on-freebsd-13-1/. I've previously used this template to set up a Windows 10 guest without any mouse problems.
Code:
curlew:/bhyve/windows7-vm# cat windows7-vm.conf
# If you want to pull a graphical console, you'll need the UEFI loader,
# no matter what OS you're installing on the guest.
loader="uefi"
graphics="yes"
xhci_mouse="yes"
# If not specified, cpu=n will give the guest n discrete CPU sockets.
# This is generally OK for Linux or BSD guests, but Windows throws a fit
# due to licensing issues, so we specify CPU topology manually here.
cpu=2
cpu_sockets=1
cpu_cores=2
# Remember, a guest doesn’t need extra RAM for filesystem caching--
# the host handles that for it. 4G is ludicrously low for Windows on hardware,
# but it’s generally more than sufficient for a guest.
memory=4G
# put up to 8 disks on a single ahci controller. This avoids the creation of
# a new “controller” on a new “PCIe slot” for each drive added to the guest.
ahci_device_limit="8"
# e1000 works out-of-the-box, but virtio-net performs better. Virtio support
# is built in on FreeBSD and Linux guests, but Windows guests will need
# to have virtio drivers manually installed.
#network0_type="e1000"
network0_type="virtio-net"
network0_switch="public"
# bhyve/nvme storage is considerably faster than bhyve/virtio-blk
# storage in my testing, on Windows, Linux, and FreeBSD guests alike.
disk0_type="nvme"
disk0_name="disk0.img"
# This gives the guest a virtual "optical" drive. Specifying disk1_dev=”custom”
# allows us to provide a full path to the ISO.
disk1_type="ahci-cd"
disk1_dev="custom"
disk1_name="/bhyve/virtio-win-0.1.217.iso"
# windows expects the host to expose localtime by default, not UTC
utctime="no"
uuid="8fde5f0e-1bd1-11ed-8b64-408d5c843d74"
network0_mac="58:9c:fc:08:a0:3b"