update VirtualBox settings to match current built-in OS X template #45
Conversation
|
I was curious to test this myself and keep hitting a VBox error. I'm assuming this is a typical VBox stability bug, and I've rebooted a couple times and re-installed the VBox installer pkg: Which version of VBox are you running? I'm running 5.0.8 on the latest 10.11.2 seed (15C31f). |
|
@timsutton can you run with PACKER_LOG=1 and gist the log.
|
|
@timsutton: 5.0.8 on 10.11.1. If @rickard-von-essen's suggestion will tell me what the |
|
I just reset my working tree to prior to this commit and it worked - it does indeed seem to be the |
|
Hm, it looks like it's not the I can look at this more later, but if removing the |
| ["modifyvm", "{{.Name}}", "--firmware", "efi"], | ||
| ["modifyvm", "{{.Name}}", "--hpet", "on"], | ||
| ["modifyvm", "{{.Name}}", "--keyboard", "usb"], | ||
| ["modifyvm", "{{.Name}}", "--memory", "2048"], | ||
| ["modifyvm", "{{.Name}}", "--mouse", "usbtablet"], | ||
| ["modifyvm", "{{.Name}}", "--vram", "9"] | ||
| ["modifyvm", "{{.Name}}", "--usbehci", "on"], |
There was a problem hiding this comment.
This --usbehci option seems to be the one that causes the storageattach error I just mentioned. I can set all other values in this diff and it boots, but I get the VBoxManage error with --usbehci on.
There was a problem hiding this comment.
Hang on, I just had a thought—have you installed the VirtualBox extension pack?
I bet it’s failing because the EHCI components are separately licensed and only available in the extension pack.
|
Great. Merging! |
update VirtualBox settings to match current built-in OS X template
|
Awesome! Should we document that the extension pack is required?
|
|
Yes, I think so. I'm glad both this and VBox itself are in homebrew-cask - might be worth mentioning that as well. |
Did this on the way to fixing #43. It didn't fix the issue, but I think it's worth tracking VirtualBox's default OS X template closely.
Of note, I removed the
cpuidsetthat we used to need for Haswell support (cf. #13 (comment)) We clearly don't need it anymore. 👍🏻