Opened 15 months ago
Last modified 14 months ago
#22004 new defect
VirtualBox on MacOSX Host installs 'provisioning profile' signed with expired certificate.
| Reported by: | nesto | Owned by: | |
|---|---|---|---|
| Component: | VMM/HWACCM | Version: | VirtualBox-7.0.14 |
| Keywords: | VT-x, certificate, profile, expired | Cc: | nesto |
| Guest type: | all | Host type: | Mac OS X |
Description
On my Macbook Pro (OS Montery v 12.7.3), installing VirtualBox installs a profile, location:
System Preferences -> Profiles.
This profile turns up 'unverified'. Apparently it is signed with a now expired certificate.
Implications: the virtualization hardware VT-x on the system (intel chipset) is inaccessible.
Suggested solution: please sign the profile with a valid certificate.
Attachments (2)
Change History (9)
by , 15 months ago
| Attachment: | profile_screenshot.png added |
|---|
comment:1 by , 15 months ago
Confirmed (expired a year ago)... and it's lacking an up to date Apple signature, not an Oracle one.
Yet another task we have to do (through someone else at Oracle who actually has access) at least every 6 months to have a product which users can run. Apple's profile handling is really making their platform a pain (and it really doesn't help that Apple's developer portal doesn't show such expired profiles at all, instead it says that the profile can be downloaded until February 2027).
Let's see how quickly we can get this sorted.
follow-up: 4 comment:2 by , 15 months ago
Any idea why you're the only person who has reported this so far? The provisioning profile's signature by Apple didn't expire exactly yesterday, and we know there are many users of VirtualBox 7.0.x on macOS.
comment:3 by , 15 months ago
Can you attach a VBox.log file of a VM which fails to run? So that we can see the symptoms and maybe create better diagnostics.
comment:4 by , 15 months ago
Replying to Klaus Espenlaub:
Any idea why you're the only person who has reported this so far? The provisioning profile's signature by Apple didn't expire exactly yesterday, and we know there are many users of VirtualBox 7.0.x on macOS.
Maybe this problem does not exist in the newer Mac OS versions. I run a bit older OS (Montery 12.7.3) because my Macbook edition is mid 2015 and this OS is the newest one it allows me to install. Except for the VT-x issue, still working perfectly.
by , 15 months ago
follow-up: 6 comment:5 by , 15 months ago
The log proves that the VM is actually getting past the BIOS which means it is running in general. But there are some "AppleHV" messages which don't look entirely normal.
comment:6 by , 15 months ago
Well yes, the guest is running and I can still work in it (vim text editing), but without VT-x it is just not very fluent and it generates a high load on the host system. BTW, thank you Klaus for promptly picking up this issue! Not sure if it is helpful, I think this is the newer certificate referenced in the System->Profiles Certificate Error message: https://www.apple.com/certificateauthority/AppleWWDRCAG3.cer
Replying to Klaus Espenlaub:
The log proves that the VM is actually getting past the BIOS which means it is running in general. But there are some "AppleHV" messages which don't look entirely normal.
comment:7 by , 15 months ago
With VirtualBox 7.0 there is no direct use of VT-x any more, and I don't think our code should fall back all the way to software emulation (which currently would be one instruction at a time type emulation which is super slooooooow). Apple pulled the plug on using it directly through a kernel extension (7.0 does not come with kernel extensions from our team any more).
profile screen shot