[Bug 255208] FATAL crash/reboot upon trying to mount a VirtualBox shared folder in FreeBSD guest (13.0 RELEASE)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Apr 23 13:13:12 UTC 2021


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255208

--- Comment #20 from Guido Falsi <madpilot at FreeBSD.org> ---
(In reply to bourne.identity at hotmail.com from comment #18)

> The shared clipboard simply does not work. I am using VMSVGA as the graphics
> controller, and my host's VirtualBox complains of Invalid Settings if I try to 
> switch to VBoxSVGA.

This is two separate things.

First about the "invalid settings"

The "invalid settings" error is a generic one, the graphics setting we are
talking aboutsetting is not actually invalid, and the advice can be ignored I
don't know why virtualbox has such a scary warning about this, because, if you
install additions inside the virtual machine, the correct driver ALWAYS IS
VBoxSVGA, for any OS.

SO if both your guests have additions 6.1. installed please disregard the
"invalid settings warning" and just use VBoxSVGA, this has anyway advantages.


About the validity of the issue when using VMSVGA, I'm not stating or implying
that your issue is invalid, and that there is no bug. Unluckily, when I noticed
this issue (crash with vboxvfs) I had a suspect of what the cause could be and
where to look at. Regarding the clipboard issue I really have no clue, and the
fact that I have zero Xorg programming experience does not help. Starting with
no clue like this even if I started looking at this it would take time.


So, if you want a functional VM fast (as in here and now) you can just use
VBoxSVGA, install additions in the guest (clipboard would not work without
additions anyway) and you will get all the functionality, without any issue.
The warning for this setting IS bogus.

If you really don't want to use VBoxSVGA (or even test it) your only option
will be waiting for someone to find a fix, or fixing it yourself.


> Should I file another PR for this ?

In general replying to closed bug reports is a problem, not for any ideological
issue, but because comments have an high chance to not be noticed. So in
general it's better to file a new issue than piggy backing an existing one.

Anyway for the virtualbox guest clipboard there is already an issue opened at
bug #254266 so this discussion should be held there.

> Please note my vm is dual-boot Linux+FreeBSD. When I boot into Linux, the 
> shared clipboard works flawlessly. But FreeBSD does not - so this is a 
> FreeBSD-specific problem.

As stated above this makes no difference, linux guests with additions work
perfect with VBoxSVGA.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-emulation mailing list