[Bug 255386] FreeBSD 13 virtualbox guest reboot when trying to acces the mounted shared folder

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon May 10 18:44:05 UTC 2021


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

--- Comment #13 from mauro <x.ricci at tiscali.it> ---
(In reply to Guido Falsi from comment #11)

yes.

-Ubuntu host system amd64 = 20.04 LTS. 
-Storage memory* = 128 Gb
-RAM = 16 Gb
-swap space = 6 Gb
-CPU = Intel i7 dual core
-Video adapter = dual Intel HD 5500 integrated + AMD Radeon M330 2Gb
-VirtualBox installation = v. 6.1.19, with Extensions Pack, 
-VirtualBox .deb package downloaded from the Virtualbox site page

Virtual Machine config:
-Storage memory** = 256 Gb
-RAM = 8 Gb
-Video Memory = 128 Mb
-cpu cores = 1
-Video adapter = VBoxSVGA  (also works with VBoxVGA)
-USB filter = enabled
-Shared folder = enabled on /home/myuser/  with automount and complete control,
also added user permissions for vboxsf with "sudo adduser $USER vboxsf"

Hardware config (HP laptop):
-Storage memory = SSD 1 Tb
-RAM = 16 GB
-CPU = Intel i7 dual core 
-Video adapter = dual Intel HD 5500 integrated + AMD Radeon M330 2Gb
-system booting on SSD disk = Windows 10 20H2
-Bios UEFI + Legacy

Freebsd 13 guest config:
-Storage memory** = 256 Gb
-RAM = 8 Gb
-swap space = 2 Gb
-VBox Guest Additions = latest update of virtualbox-ose-additions  from FreeBSD
packages repository


*Ubuntu host system 20.04 LTS is installed in a bootable USB3 pendrive of 128
Gb

**FreeBSD 13 guest system is installed in a USB3 pendrive of 256 Gb which can
also be booted from inside a Virtualbox session even hosted in a smaller
storage space. Works same both as a physical USB3 bootable volume, and also as
virtual machine handled in a VirtualBox session.

A NomadBSD 1.4 system installed in same mode (physical USB3 bootable also
handled by a VirtualBox session) does not give this issue when used as virtual
machine in VirtualBox Ubuntu hosted. Shared folders are normally accessible in
Ubuntu like in Windows. Guest Additions are already included in this release,
version 5.2.44_3 (legacy).
Thank you

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


More information about the freebsd-emulation mailing list