Adding experimental support for OSX Mavericks via "Install OS X Mavericks.app" #848
Conversation
|
Since I've still yet to ever get VirtualBox to boot a 10.7+ VM (and they don't list it as officially supported), I've not spent time trying to deal with VirtualBox, and only use VMware. But as far as Mavericks is concerned, Apple changed the layout in terms of where the installation packages are located relative to the dmg that contains the actual OS being booted for the installer. So, that may be part of your issue here. Since Packer was released, I consolidated my OS X build script and template into its own repo and have been maintaining it here: https://github.com/timsutton/osx-vm-templates So, you could check that to see what's done to make a bootable installation image for 10.9. The TL;DR is that you copy the Packages folder into the BaseSystem.dmg and replace the symlink, making a new single dmg. I haven't merged changes back into VeeWee's 'OSX' template since earlier this year, but if anyone would like to, please feel free to. There aren't any template-specific changes that should be required to continue supporting VeeWee here, most of the changes have been in in the prepare_iso script and the postinstall scripts. |
|
looks like progress, could you rebase it for merging? |
| @@ -275,7 +302,7 @@ if [ -n "$DEFAULT_ISO_DIR" ]; then | |||
| msg_status "Setting ISO file in definition "$DEFINITION_FILE".." | |||
| ISO_FILE=$(basename "$OUTPUT_DMG") | |||
| # Explicitly use -e in order to use double quotes around sed command | |||
| sed -i -e "s/%OSX_ISO%/${ISO_FILE}/" "$DEFINITION_FILE" | |||
| sed -i '' -e "s/%OSX_ISO%/${ISO_FILE}/" "$DEFINITION_FILE" | |||
There was a problem hiding this comment.
can you change it to sed -i'' -e ... - it is more portable
Just like #770, this one is semi-working... it produces an InstallESD.dmg output for OSX Mavericks, but VMWare Fusion refuses to boot from the disk...
There must be something that changed between Mountain Lion and Mavericks, but it's not immediately apparent to me, as I don't think I fully understand how the UEFI boot process determines whether a boot disk is bootable...
I'm getting a very similar problem to what I was seeing in VirtualBox for #770
@timsutton : Do you have any insights here?