-
Notifications
You must be signed in to change notification settings - Fork 1.1k
VirtualBox 6.1 does not support setting NVRAM parameters with VBoxManage setextradata (efi/0/LUN#0) #135
Comments
This issue looks like it depends on a specific CPU architecture on Mac hosts. You might want to report this issue to VirtualBox devs. |
Issue exists on all VirtualBox 6.1 platforms. This means that NVRAM parameters ( |
Workaround in version 0.76.8. This means iCloud, iMessage, and other Apple-connected services will not work. NVRAM works on VirtualBox 6.0 and 5.2, you may want to use those versions instead until the bug is resolved. |
https://www.virtualbox.org/wiki/Changelog-6.1
🤔 |
Must Run Virtualbox 6.1 due to Ubuntu 19.10 host and guests. Can't boot Mac guests 10.13, 10.14 or 10.15. Tried all of the above workarounds and still will not boot. Tried installing using your script and it will not boot the second restart when installing. Disabled sip in your script. Any other changes that can be implemented in order to install any recent version of MacOS? ERROR: Can't attach Nvram Storage driver (VERR_PDM_CFG_MISSING_DRIVER_NAME) |
@dadons7 What version of the script are you using? Version 0.76.8 (and version 0.77.0 I uploaded right now) works on VirtualBox 6.1 with macOS 10.13 and 10.14 guests, but nothing works with 10.15.2 guests at the moment due to EFI issues. macOS 10.15.0 and 10.15.1 guests work fine, but aren't available from Apple software update servers. Enabling/disabling SIP has no effect with the latest script version on VirtualBox 6.1 because the script skips |
Was running Version 0.76.8. Will try 0.77.0. Thank you for the LUN#0 suggestion. Will try that with existing VM. |
Please attach |
Was able to import backup VM's and then comment out the LUN#0 as you suggested. These do boot. Did try installing as the logged-in user and not root. Got a little further then errored out... |
@dadons7 There are no errors in the log, could you specify the last few errors that you received? |
If anyone knows what's the name of the NVRAM Storage driver VirtualBox is looking for, please post it. Apparently it is set with the variable |
Looks like this isn't a bug, it's a feature. Oracle removed the NVRAM driver from VirtualBox. |
What about this "NVRAM file" that's been added in that commit, could the properties be set in the file instead on 6.1? |
The new NVRAM code is here. I'm not a software developer, if someone wants to take a crack at it by all means. |
Hi, The changeset doesn't include an alternative and cleaned up this code, so the alternative might be already present. DevEFI driver [1] has a specific list of variable that can be set, so cannot be used instead here. However, it has a NvramFile which can be used to introduce the efi variables [2]. If I'm understanding the installation script correctly, that's why LUN#0 was used at the beginning. Maybe the way to fix it is to provide this NVRAM file for efivars? I didn't found a way to craft it though. [1] https://www.virtualbox.org/svn/vbox/trunk/src/VBox/Devices/EFI/DevEFI.cpp |
There's hope, I think I found a workaround using the EFI shell's |
Implemented binary NVRAM support in version 0.80.0 |
Hi, nice work ! Thank you very much ! Do you have details for the migration of an existing VM ? |
Migrating VBox 6.0 VMs to VBox 6.1
iMessage connectivity
|
I have followed these steps closely but am not seeing the new serial number or other metadat reflected in system profiler or "about this mac". The EFI shell output scrolls by too quickly to determine if The new values are reflected in the |
Since version 0.80.0 the script's ESP directory structure has changed to comply with OpenCore. See the documentation for up-to-date information. With version 0.90.0 the EFI files are stored in
|
OK, so repeated reboots never yielded updated values. However, a total shutdown of the VM and then re-starting it did reveal the new serial number etc in "About This Mac" |
Sorry I didn't see this before my second comment was posted somehow. I had the right commands and file locations. It just appears that a cold boot of the VM was necessary for them to take full effect. |
i am having trouble to understand this line cp -r /Volumes/path/to/VISO/ESP/* ESP/ |
|
So I was using the script downloaded around
2019-12-11 at 1PM EST
(revision 9b00b0240) and it didn't boot at all, with VirtualBox complaining aboutVERR_PDM_CFG_MISSING_DRIVER_NAME
.Aftrer a lot of trial and error I found out that removing the tag below from
macOS.vbox
"fixed" the issue:After this I was able to proceed with the installation.
The text was updated successfully, but these errors were encountered: