Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

update VirtualBox settings to match current built-in OS X template #45

Merged
merged 2 commits into from
Nov 9, 2015
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -130,16 +130,6 @@ Vagrant.configure("2") do |config|
end
```

#### Additional VM configuration for Packer

So far we've seen that the `--cpuidset` option needs to be passed to `modifyvm` as a line in the packer template if a Haswell Intel Mac is used to build the VM, at least as of VirtualBox 4.3.12. It seems to cause a VM crash on at least one older Mac, a Core 2 Duo-based 2010 Mac Mini, though did not cause issues on an Ivy Bridge 2013 iMac I tested. If it's missing on a Haswell Mac, however, the VM hangs indefinitely. This behaviour is likely to change over time as Oracle keeps up with support for OS X guests.

```json
"vboxmanage": [
["modifyvm", "{{.Name}}", "--cpuidset", "00000001", "000306a9", "00020800", "80000201", "178bfbff"],
]
```


## Box sizes

Expand Down
11 changes: 6 additions & 5 deletions packer/template.json
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@
"boot_wait": "2s",
"disk_size": 40960,
"guest_additions_mode": "disable",
"guest_os_type": "MacOS109_64",
"guest_os_type": "MacOS1011_64",
"hard_drive_interface": "sata",
"iso_checksum_type": "md5",
"iso_checksum": "{{user `iso_checksum`}}",
Expand All @@ -77,13 +77,14 @@
["modifyvm", "{{.Name}}", "--boot1", "dvd"],
["modifyvm", "{{.Name}}", "--boot2", "disk"],
["modifyvm", "{{.Name}}", "--chipset", "ich9"],
["modifyvm", "{{.Name}}", "--cpuidset", "00000001", "000306a9", "00020800", "80000201", "178bfbff"],
["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"],
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ha! That was totally it.

["modifyvm", "{{.Name}}", "--vram", "16"],
["storagectl", "{{.Name}}", "--name", "IDE Controller", "--remove"]
]
}
],
Expand Down Expand Up @@ -131,8 +132,8 @@
"facter_version": "latest",
"hiera_version": "latest",
"install_vagrant_keys": "true",
"iso_checksum": "aff67f81dfbad7afda56c423473d61a6",
"iso_url": "OSX_InstallESD_10.9.3_13D65.dmg",
"iso_checksum": "b78fef812ca50da24381e45e56fb9285",
"iso_url": "OSX_InstallESD_10.11.1_15B42.dmg",
"password": "vagrant",
"puppet_version": "latest",
"update_system": "true",
Expand Down