﻿ticket	summary	host	version	created	modified	_changetime	_description	_reporter
16273	Mouse Wheel Bug in FreeBSD/TrueOS guest	all	VirtualBox 5.1.10	2016-12-06T23:57:45Z	2016-12-07T00:01:20Z	2016-12-07T00:01:20Z	"Hi There,

Whats broken:
When running FreeBSD as a guest on any host for some reason the mouse scroll wheel issues back and forward browser (web browser such as Firefox or Chromium) commands in FreeBSD and TrueOS. 

Whats expected:
The Mouse wheel should only scroll up and down when using a web browser

Whats happening:
The mouse simultaneously issues backwards and forwards commands in addition to scrolling up and down when using a web browser.

Scope:
This issue affects FreeBSD/TrueOS VirtualBox additions for FreeBSD guests 5.1.10 and earlier /usr/ports/emulators/virtualbox-ose-additions
This issue has no effect on guests which do not use the FreeBSD OS type in Virtual Box host.
There is no effect switching between ps3/usb tablet settings on the host config.

I posted briefly in the Virtual Box forums on this issue
https://forums.virtualbox.org/viewtopic.php?f=4&t=80912&p=379748#p379748

And have had some nice folks in the TrueOS chatroom track down that this bug seems to be limited to Virtual Box's FreeBSD mouse driver.

Jeffrey Baitis @baitisj posted in the TrueOS chat the following:
so here's the proof. That's running xev and showing the mouse events when I'm scrolling the mouse wheel up and down., I tried the same test in a linux host, and it worked fine. There's clearly some issue with the freebsd virtualbox input driver

[[Image(1)]]


Thank you for your assistance!
Jason"	Oclair
21201	FreeBSD 12.3 and pfSense 2.6.0 networking no longer works with upgrade to VB 7.0.2 => fixed in SVN	Linux	VirtualBox-7.0.2	2022-10-24T17:12:33Z	2023-01-12T15:03:06Z	2023-01-12T15:03:06Z	"Hi,

After a recent upgrade from VirtualBox 6.1.40 to 7.0.2 on Arch Linux, all of my pfSense virtual machines hang at ""Configuring WAN interface"" during the boot process. Reverting VirtualBox back to 6.1.40 fixes it.

The pfSense VM (CE 2.6.0) is configured with EFI enabled and the WAN interface is a NAT virtual network adapter with ""virtio-net"". I've tried changing the adapter to either of the Intel PRO/1000 Server options and it does eventually boot after a 5 minute hang at the same point, but it is unable to get an IP and therefore doesn't work either.

I've also tried to create a brand new pfSense VM using the same settings as our currently running ones and while it installs properly, after the reboot it is stuck on ""Default interfaces not found -- Running interface assignment option."". This also works properly in 6.1.40. I've also tried setting the network interface to bridge mode and no change.

Edit: All other VM work properly, including other FreeBSD 13.1 virtual machines but same behavior with FreeBSD 12.3.

Any suggestions?"	rickga
19988	VM crashes or restarts during package upgrade on FreeBSD guest	Linux	VirtualBox 6.1.16	2020-10-21T17:57:43Z	2021-03-26T21:01:07Z	2021-03-26T21:01:07Z	"Hi,

my host machine is Debian GNU/Linux 10.6 latest and up to date (21 Oct 2020). VirtualBox version is 6.1.16.

I have a FreeBSD guest - FreeBSD 12.1-RELEASE-p10 GENERIC.

When I try to upgrade packages on guest (FreeBSD) the virtual machine restarts or vanishes.

I could not reproduce the issue with previous versions of VirtualBox (6.1.x) or with Linux guest including VirtualBox 6.1.16.

There is a video.

https://www.youtube.com/watch?v=dqjWNC7nPX0

Kind regards
Georgi
"	Georgi
20214	click close button freez machine	Linux	VirtualBox 6.1.18	2021-02-21T14:57:09Z	2021-03-19T19:54:28Z	2021-03-19T19:54:28Z	"Halo,

the problem is that click on red cross freezing machine. I believe it is mistake because after this click the menu shows up. So when I click it on VPN server machine, to hide it down (not to shout down) I lost the connection.[[Image()]]

So my suggestion is not to freeze machine until the required action is chosen. Please take a look at enclosed picture.
file:///home/swk/Obrazy/Zrzut%20ekranu%20z%202021-02-21%2015-40-25.png
I'm not sure if it enclosed "	PimCo
17529	VBoxManage and Guest Additions 5.x.y: Can't communicate with FreeBSD Guests	Linux	VirtualBox 5.2.6	2018-02-06T11:32:10Z	2021-03-18T09:37:39Z	2021-03-18T09:37:39Z	"I've been trying to get FreeBSD to work with VBoxManage for a while (in fact for several years, since 9.3).

This is the result of testing VirtualBox 5.2.6 on Ubuntu with FreeBSD-11.1-RELEASE-amd64 as guest. 

{{{
$ VBoxManage guestcontrol freebsd-11.1-amd64 --username root --password 2Hard2Crack stat /tmp --verbose
Creating guest session as user 'root'...
Waiting for guest session to start...
VBoxManage: error: The specified user was not able to logon on guest
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestSessionWrap, interface IGuestSession, callee nsISupports
VBoxManage: error: Context: ""WaitForArray(ComSafeArrayAsInParam(aSessionWaitFlags), 30 * 1000, &enmWaitResult)"" at line 938 of file VBoxManageGuestCtrl.cpp
Closing guest session ...
}}}

Guest Additions were installed with pkg:
{{{
[root@freebsd ~]# pkg install -y virtualbox-ose-additions
[root@freebsd ~]# sysrc vboxguest_enable=""YES""
vboxguest_enable: NO -> YES
[root@freebsd ~]# sysrc vboxservice_enable=""YES""
vboxservice_enable: NO -> YES
[root@freebsd ~]# reboot
}}}

Guest Additions kernel module is loaded in Guest:
{{{
[root@freebsd ~]# VBoxService --version
5.2.4r119758
[root@freebsd ~]# kldstat|grep vbox
 3    1 0xffffffff8221f000 2eacb    vboxguest.ko
}}}"	Jonas Almroth
20098	VM Selector GUI crash on Mojave	Mac OS X	VirtualBox 6.1.16	2020-12-19T15:34:02Z	2021-03-03T21:59:18Z	2021-03-03T21:59:18Z	"I am experiencing a crash of the VirtualBox GUI nearly every time I use a FreeBSD, XP, or Linux guest. The guests run fine. It's pretty annoying. It doesn't hinder my use of the VM's themselves - thankfully. This happens in:

VirtualBox 5.2, 6,0, and 6.1 lines: 5.2.44, 6.0.24 and 6.1.16, specifically.

My current setup:
MacOS 10.14.6 w/16GB RAM
VirtualBox 6.1.16
MacBook Pro 15"" mid 2012

I'll attach the crash log from Apple, since it's directly relevant and the VM log from the VM that was running when it crashed (I don't know where to find the GUI log).
"	decuser
19764	paravirtualized adapter doesn't receive packets until a ping6 of the gateway	Mac OS X	VirtualBox 6.1.10	2020-07-25T11:30:11Z	2020-07-28T20:00:10Z	2020-07-28T20:00:10Z	"OpenBSD 6.7 guest on macOS Catalina, where the guest is configured for IPv6-only and a paravirtualized network bridged adapter. After booting the OpenBSD guest, and obtaining the IPv6 address by autoconfiguration, the Internet seems unreachable. Simultaneous packet captures on the guest and the host show, for example, a DNS request egress the guest and the host, and the DNS response ingress the macOS host but not the OpenBSD guest. A workaround is to ping6 the IPv6 gateway public address, then suddenly packets for the guest will start showing up in the guest packet capture.

However, the ping6 also inserts the neighbor entry for the IPv6 gateway public address. Otherwise, because of autoconfiguration, the Internet6 default route is the IPv6 gateway link-local address and there is only the gateway's link-local address in the neighbor mapping table."	jasonmader
18415	Guest time lags behind after an online snapshot deletion	other	VirtualBox 5.2.26	2019-02-06T08:31:34Z	2021-03-18T09:39:32Z	2021-03-18T09:39:32Z	"I had some mysterious cases of huge clock drifts, and other times it was perfect for days… I think I found the problem: it happens shortly after an online snapshot deletion.

Here's a log of a FreeBSD guest running on a FreeBSD host, being perfectly synchronized for the first 2h44, but then losing 60"" every 8 minutes after the snapshot is deleted."	Lapo Luchini
19027	iSCSI-attached disks of size 0 or which cannot be read lead to VBoxSVC going into a 100% CPU loop	other	VirtualBox 5.2.34	2019-10-18T15:00:56Z	2019-10-18T15:00:56Z	2019-10-18T15:00:56Z	"Scenario 1:
- FreeBSD 12.0 as iSCSI server (machine A), exporting several block devices
- Misconfiguration results in these devices being exported with size 0 (reason in this case: the blocksize argument in /dev/ctl.conf was missing and needed to reflect the underlying device block size of 4096)
- FreeBSD 12.0 (machine C) hosts various VirtualBox clients

Scenario 2:
- Linux openSUSE Leap 15.1 as iSCSI server (machine B), exporting a block device
- Firewall misconfiguration leads to read failures when accessing the exported device
- FreeBSD 12.0 (machine C) hosts various VirtualBox clients

Result (both scenarios):
- On machine C, VBoxSVC goes into a tight loop retrying accesses to these devices
- All running VirtualBox client instances hang, including those not accessing the misconfigured iSCSI exports
- On a multiprocessor system, VBoxSVC uses n x 100% CPU (don't know how n happens, probably the number of concurrently running clients)

Expected result:
- The error should be treated reasonably, probably forwarded to the client (as a read error of the device)

Note:
- The same issue also happened with earlier releases.
"	wonko1953
17817	Add support for OpenBSD in guest additions	other	VirtualBox 5.2.12	2018-06-12T19:40:14Z	2018-06-13T23:31:26Z	2018-06-13T23:31:26Z	"https://www.virtualbox.org/manual/ch03.html#guestossupport states no OpenBSD support in guest additions //yet//. OpenBSD support in VirtualBox has come a long way over the years and it's an attractive option for development/testing and virtual desktop use. Is guest addition support feasible?

Would be great to see support for some pressing usability enhancements, e.g. resizing guest display support, shared folders, shared clipboard, time synchronization. "	crater
20747	Memory can't be read after resuming VM from pause	Windows	VirtualBox 6.1.30	2021-12-23T23:25:05Z	2022-02-07T18:27:06Z	2022-02-07T18:27:06Z	Memory can't be read after resuming VM from pause	MikhailRokhin
20746	Memory can't be read	Windows	VirtualBox 6.1.30	2021-12-23T23:22:14Z	2021-12-23T23:22:14Z	2021-12-23T23:22:14Z	Memory can't be read	MikhailRokhin
20743	VBox 6.1.x does not boot FreeBSD EFI	Windows	VirtualBox 6.1.30	2021-12-23T00:22:56Z	2021-12-23T00:22:56Z	2021-12-23T00:22:56Z	"Vbox 6.0.24 (or older) boots (FreeBSD) EFI images just fine.
Vbox 6.1.x (I've tried all versions) does not boot EFI but instead goes to network boot even if that's disabled for the VM."	adwsklerjuihgweiop
20524	VirtualBox crashes with FreeBSD guest	Windows	VirtualBox 6.1.24	2021-08-25T12:50:16Z	2021-09-06T20:17:55Z	2021-09-06T20:17:55Z	See attached log.	DeGarden
20315	6.1.20 Fails to start guest : memory can't be written	Windows	VirtualBox 6.1.20	2021-04-22T14:32:55Z	2021-04-23T21:36:15Z	2021-04-23T21:36:15Z	As of 6.1.18 it succeeded.	MikhailRokhin
20306	VirtualBox crashes on IO in FreeBSD 13	Windows	VirtualBox 6.1.18	2021-04-20T09:42:24Z	2021-04-20T10:01:34Z	2021-04-20T10:01:34Z	"I started up a FreeBSD 13 VM that I've had for a little bit on VB 6.1.16, started installing some packages, and suddenly the VM crashed and displayed ""Aborted"" on the management interface.

I upgraded VB to 6.1.18, booted the VM, started installing the same packages again, and lo and behold, it died again.

I've attached the log from the VM dying on 6.1.18."	rincebrain
19420	mount -t vboxsf Operation not supported by device	Windows	VirtualBox 6.1.4	2020-03-21T21:27:52Z	2020-04-06T17:10:27Z	2020-04-06T17:10:27Z	"When use `mount -t vboxsf ...`as suggested by VB-host SharedFolders hint, it fails, but writes nothing in dmesg. And there is mistake in the hint - it should be vboxVFS not vboxSF. Because vboxSF triggers nothing and vboxVFS triggers kldload of /boot/modules/vboxvfs.ko . [[BR]][[BR]]

When use `mount -t vboxvfs ...` and `mount_vboxvfs ...` it shows:[[BR]]

link_elf_obj: symbol bcmp undefined[[BR]]
linker_load_file: /boot/modules/vboxvfs.ko - unsupported file type  [[BR]][[BR]]

FreeBSD 13-Current[[BR]]
Additions: 5.2.34_2 (installed via pkg, not compiled) [[BR]][[BR]]
"	MikhailRokhin
19422	VirtualBox Host-Only Ethernet Adapter DHCP settings proper apply need restart of VB	Windows	VirtualBox 6.1.4	2020-03-22T20:28:05Z	2020-03-28T13:29:46Z	2020-03-28T13:29:46Z	"Changing DHCP properties of VirtualBox Host-Only Ethernet Adapter (Ctrl+H) need restart of the whole VB to be applied properly. If not, settings VB was started with are applied (whatsoever user changes them), after just guest is restarted.


It should work in other way: user stops guest, changes DHCP properties of VirtualBox Host-Only Ethernet Adapter (Ctrl+H), starts guest and changes are properly applied.


Now it needs to stop all guests, main window of VB should be closed, VB should be started again."	MikhailRokhin
18882	OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.	Windows	VirtualBox 6.0.10	2019-08-29T23:17:56Z	2020-02-18T22:35:57Z	2020-02-18T22:35:57Z	"(This looks like a repeat of the Bug #9889, but is probably unrelated.)

I'm using VirtualBox on a Windows 10 host to run a FreeBSD and some Linux VMs (guests). The FreeBSD VM is my main desktop -- and the only guest with GUI (X11) configured.

My access to the Windows host itself is through Remote Desktop -- from a ""dumb"" terminal capable of running only the Remote Desktop client.

Things were working fine until the recent upgrade of the hardware -- the same disk was moved into a new machine, with faster CPUs and bigger RAM. There were no software configuration-changes.

VMs also came up Ok, but, upon starting X11 session in the FreeBSD guest, I started getting the error in subject from various X11-clients.

Since then I tried the following changes, to no avail:
 1. Upgrade the host software (including the extras pack) from 5.x to 6.0.10
 2. Change the ""Graphics Controller"" to ""VBoxSVGA"" in the VM's definition.
 3. Upgrade the virtualbox-ose-additions inside the VM from 5.x to 6.0.10

Nothing helped -- the machine comes up fine, simpler X11-clients (like xterm) work, but many (including Qt5-using programs) fail with the same message about 3D-acceleration...

I'm attaching the X-server's log from inside the VM, and VM's log from the host.

At the very least, the error should be more detailed. At best, it should not happen :)"	mi
13083	Always On Top option for guest window in Windows host	Windows	VirtualBox 4.3.12	2014-06-01T12:06:03Z	2016-04-22T13:11:50Z	2016-04-22T13:11:50Z	Would you be so kind and make Always On Top option for guest window of Windows host? Thank you in advance.	MikhailRokhin
