﻿ticket,summary,host,version,created,modified,_changetime,_description,_reporter
9390,Mac OS X guest video memory remains on 4MB. It does not use the video memory setting of the guest configuration.,Mac OS X,VirtualBox 4.1.0,2011-08-06T09:12:58Z,2015-09-10T02:57:35Z,2015-09-10T02:57:35Z,It does not matter what setting you choose for video memory (0 - 128 MB) for a Mac OS X server guest. The guest OS always reports that there is only 4MB screen memory available. Please see my attached screen shots for the guest Os report. This is evident when trying to use screen share to the guest OS. The screen share quality is in very low. This also could be the cause of the jerky graphics inside the guest OS normal operation eg. the menu navigation. ,Pieter
15727,Add HiDPI Support for macOS guests,Mac OS X,VirtualBox 5.1.2,2016-08-02T20:49:40Z,2016-08-02T20:49:40Z,2016-08-02T20:49:40Z,"When running VirtualBox on a MacBook Pro Retina, the Chrome of VirtualBox (Window Frames and the Icons at the Bottom of the Window) are rendered in HiDPI just fine, but the macOS Guest doesn't run in HiDPI mode.",Lars Sonchocky-Helldorf
16847,Incomplete DMG support,Mac OS X,VirtualBox 5.1.22,2017-06-19T08:56:04Z,2017-06-19T08:56:04Z,2017-06-19T08:56:04Z,"Some DMG cannot be mounted in a VM with a ""`VERR_VD_DMG_INVALID_HEADER`"" error. Example [https://dl.bintray.com/xquartz/downloads/XQuartz-2.7.11.dmg XQuartz-2.7.11.dmg], but there are actually the majority. The validity of each of the DMGs has been verified. Full error message:

> ''Could not open the medium '''""/Users/Shared/_Downloads/_System/XQuartz-2.7.11.dmg""'''. [[br]] [[br]]
> VD: error VERR_VD_DMG_INVALID_HEADER opening image file '''""/Users/Shared/_Downloads/_System/XQuartz-2.7.11.dmg""''' (VERR_VD_DMG_INVALID_HEADER)''

[[br]]
Other examples include:
* Any DMG created from the Disk Utility will not mount. I believe I've tried all possible combinations, but they all fail with the above error message.
* [http://adcdownload.apple.com/Developer_Tools/Xcode_7.3.1/Xcode_7.3.1.dmg Xcode 7.3.1], that's actually the weirdest. The VM (OSX) shows a ""`The disk you inserted was not readable by this computer. Ignore | Eject`"". If you copy the same exactly DMG in the VM, it is mounted and works as expected.
",Socratis
9987,Provide Additions for Mac OS X guests,Mac OS X,VirtualBox 4.1.6,2011-12-04T01:00:15Z,2017-08-05T02:27:14Z,2017-08-05T02:27:14Z,There are no guest additions for Mac OS X for server editions or regular additions.,Matthew Sedam
17313,Feature: Keyboard scancode translation,other,VirtualBox 5.1.30,2017-11-26T06:16:09Z,2017-11-26T06:16:09Z,2017-11-26T06:16:09Z,"Most modern keyboards use IBM scancodes, and so VirtualBox users are likely to get fairly consistent behavior when sending these scancodes to just about every VM, via VBoxManage controlvm <vm> keyboardputscancode <hexpair>... However, macOS guest VM's use a different scancode set, one for Apple keyboards. This does not present a problem for most graphical VirtualBox users, however it does break some things for command line driven systems such as packer.io. In particular, systems like packer that are built on top of VirtualBox and want to send key codes to macOS VM's are faced with the nuisance of performing scancode translation. I propose that VirtualBox offer a VM configuration option like:

VBoxManage modifyvm <VM> --fromscancodes ibm --toscancodes apple

or similar flag syntax, that declares that VirtualBox should automatically remap scancodes sent via VBoxManage controlvm <VM> keyboardputscancode <hexpair>..., relieving packer and other tools from having to worry about such low level details (packer could then simply use IBM scancodes all the time).

I've also filed a ticket with packer to select more appropriate scancode sets for different kinds of VM's:

https://github.com/hashicorp/packer/issues/5635

As a mac user, I really don't care which of these is implemented, I just want to be able to use macOS guest VM's without having to hack around keyboard incompatibility issues!",mcandre
18196,OSX GAs binaries not in OSX guest path,Mac OS X,VirtualBox 6.0.0,2018-12-18T21:04:40Z,2018-12-18T21:04:40Z,2018-12-18T21:04:40Z,"On Linux based systems the Guest Additions are installed in several places, one being the actual binary (`/opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl`), with two additional links:
{{{
$ whereis VBoxControl
VBoxControl: /usr/bin/VBoxControl /usr/bin/X11/VBoxControl /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl

 $ ls -al /usr/bin/VBoxControl /usr/bin/X11/VBoxControl /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl
-rwxr-xr-x 1 root root 911520 Dec  18 13:45 /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl
lrwxrwxrwx 1 root root     45 Dec  18 22:27 /usr/bin/VBoxControl -> /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl
lrwxrwxrwx 1 root root     45 Dec  18 22:27 /usr/bin/X11/VBoxControl -> /opt/VBoxGuestAdditions-6.0.0/bin/VBoxControl
}}}
On an OSX guest however only the actual binary(ies) are installed, with no additional links in the Path:
{{{
$ locate VBoxControl
/Library/Application Support/VirtualBox Guest Additions/VBoxControl
/Library/Application Support/VirtualBox Guest Additions/VBoxControl-amd64

$ ls -al /Library/Application\ Support/VirtualBox\ Guest\ Additions/VBoxControl \
         /Library/Application\ Support/VirtualBox\ Guest\ Additions/VBoxControl-amd64 
-rwxr-xr-x  1 root  wheel  907364 Dec 18 13:45 /Library/Application Support/VirtualBox Guest Additions/VBoxControl
-rwxr-xr-x  1 root  wheel  907364 Dec 18 13:45 /Library/Application Support/VirtualBox Guest Additions/VBoxControl-amd64
}}}
Please consider adding symbolic links for the !VirtualBox programs in the Path, wherever this is allowed by the OSX policy (most probably ""`/usr/local/bin`""):
{{{
$ echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
}}}
It's going to make it easier/less awkward...",Socratis
19487,macOS 10.15.4 - VM hang if allocated more than 6 CPU or > 32Gb of memory,Mac OS X,VirtualBox 6.1.4,2020-04-14T13:57:49Z,2020-04-14T13:57:49Z,2020-04-14T13:57:49Z,Installed VirtualBox 6.1.4 and extensions on MacOS Catalina 10.15.4. Created VM through vagrant (macinbox) or via ISO and VM will hang if 32Gb or more memory allocated to VM or if 6 logical cores (out of 12 on a 6 physical core MacMini 2018) are allocated to VM. Never starts boot of machine past initial EFI startup. Reducing to 32700Mb or 6 cores and the machine starts up successfully.,nycnewman
19491,have errors showing up trying to get into macOS Catalina,Windows,VirtualBox 6.1.4,2020-04-14T22:44:21Z,2020-04-16T09:49:23Z,2020-04-16T09:49:23Z,This is the first time I am trying to get into Catalina from my windows 10-64 bit environment.  I have tried several times but I am getting error codes.as shown.  ,esams2
19692,not compatible with dual display with different dpi scaling,Windows,VirtualBox 6.1.10,2020-07-01T01:11:30Z,2020-07-09T03:26:34Z,2020-07-09T03:26:34Z,"I launched virtualbox in display 1 with 200% dpi scaling, when I drag the window to second screen with 100% dpi scaling the title of the window become very large.
instead, when drag from 100% to 200% every thing in 200% become very small.",liurunliang
19864,OVERHEATING AND HIGH RISK TO DAMAGE MACHINE - MacBook Pro 2018 CATALINA OS,other,VirtualBox 6.1.14,2020-09-06T12:53:48Z,2020-09-07T10:22:59Z,2020-09-07T10:22:59Z,"THE VIRTUALBOX WITH CATALINA AND MACBOOK PRO 2018 CREATES OVERHEATING PROBLEMS. THE PROCESSOR COMES TO WORK AT 80 90 CELSIUS DEGREES, THE PROCESS AS YOU CAN SEE WORKS AT> 160% OF THE CPU, WE ARE NOT THERE, SOMETHING IS NOT WORKING WITH THE SOURCE FOR MACOS CHECK THANK YOU CAN DAMAGE THE MACHINE!",nickslay@…
20044,IP Duplicate with MacOS 11.0.1 (Big Sur) and VBox 6.1.16,Windows,VirtualBox 6.1.16,2020-11-17T06:08:36Z,2020-11-17T06:08:36Z,2020-11-17T06:08:36Z,"After installing MacOS X 11.0.1 and reinstalling VBox 6.1.16 to fix the kernel issue.

Now all Guest OS cannot connect to network (Bridged Adapter), since it detect a conflict IP address.

Looking in Windows Event Viewer and the duplication of 0.0.0.0 is identified with the MAC address of the Host MacOS server

I think we should have a new release to correct this issue in MacOSX Big Sur
Thank you",BDelorme
20054,network problems under bigsur macOS version,Windows,VirtualBox 6.1.16,2020-11-20T14:05:49Z,2020-12-01T11:59:52Z,2020-12-01T11:59:52Z,"I have problems getting a working network connection when I transferred from Catalina to Bigsur

Sometimes VBOX crashes when I use NAT option for the adapter, normally use bridged option",pbvbox
20427,can't start the virtual machine,Windows,VirtualBox 6.1.22,2021-06-21T16:18:33Z,2021-06-21T16:40:00Z,2021-06-21T16:40:00Z,"when i start virtual machine i have got this error

{{{
Failed to open a session for the virtual machine Mac.

Could not launch the VM process for the machine 'Mac' (VERR_INVALID_UTF16_ENCODING).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

}}}

how can i fix it?

",gihan
20543,macOS Guest Additions do not include mount.vboxsf,Mac OS X,VirtualBox 6.1.26,2021-09-11T17:47:16Z,2021-09-13T10:47:16Z,2021-09-13T10:47:16Z,"When successfully installing the Darwin guest additions, the mount.vboxsf tool is not included, while there is a source tree available and seemingly being built.

Steps to reproduce:
- Disable all security on macOS Catalina guest
- Insert the Guest Additions ISO
- Install Guest Additions
- `mount -t vboxsf VboxShared /Users/Shared/Host` result in a File Not Found error because /Library/Filesystems/vboxsf.fs does not exist

I also checked the contents of the .pkg and as far as I can tell, it does not contain any tools for mounting file systems. The source tree on the other hand does contain some kind of implementation in src/Vbox/Additions/darwin/VboxSF, which I unfortunately can't seem to manage to build because the build system does not seem to be compatible with Xcode 12.

As for some context:
I am trying to set up a macOS Catalina build system to build Unreal Engine games on a Big Sur (and Windows) host. The VM should have a minimally sized main disk and should share the actual build tree with the host. I already have all this set up, using SMBFS to share the build tree and it is working ok, but network performance is only about 30MB/s, so builds take forever.

Therefore I am trying to mount shared folders in the macOS 10.15 Catalina guest in hopes they will give me better performance, somewhere in the range of the 400MB/s, the virtual disk in the VM provides. I already installed the guest additions successfully, but as far as I can see, they are missing the mount.vboxsf tool to actually mount the shared folders. I also tried to unpack the VboxDarwinAdditions.pkg, contained on the additions iso of multiple VirtualBox version, but the tool simply isn't there and is not being created. As per the source tree, there should be a tool available to mount the shared folders though, so I am guessing this is a bug in the build environment.
",HI_Paul
20719,VirtualBox-6.1-6.1.31_148688_el7-1.x86_64.rpm fail to build on Kylin Linux Advanced Server V10,Linux,VirtualBox 6.1.30,2021-12-10T01:19:11Z,2021-12-13T10:08:50Z,2021-12-13T10:08:50Z,"Installing VirtualBox-6.1-6.1.31_148688_el7-1.x86_64.rpm work fine, but sudo /sbin/vboxconfig fails with kernel-4.19.90-25.8.v2101.ky10.x86_64",Nuyoah
21216,Recovery Mode is not Accessible in Newer MacOS Guests,Mac OS X,VirtualBox-7.0.2,2022-10-29T17:34:03Z,2022-10-29T17:34:03Z,2022-10-29T17:34:03Z,"IF you install Monterey on VirtualBox, you're not able to boot into Recovery Mode via the VB BIOS (e.g. ""Boot from file"") because there's no boot.efi file shown under the GUID in the Recovery Mode partition.  This issue appears to have started with BIg Sur.  If you access the filesystem with the UEFI Shell, you'll see that there are a bunch of files names boot.efi.<some string> in that partition, but this new naming system is obviously not recognized by VirtualBox.

This problem reproduces with the latest VirtualBox, VB 7.",ThomasF
