Description

"... you are granted a limited, non-transferable, non-exclusive license: [...] (iii) to install, use and run up to two (2) additional copies or instances of the Apple Software within virtual operating system environments on each Mac Computer you own or control that is already running the Apple Software."

Which would seem to explicitly permit running Mac OS X 10.7 (Lion) non-server version as a guest under VirtualBox provided the VirtualBox host is also running Mac OS X.

Attempts to boot the 10.7 installer under VirtualBox 4.1.0 running on a Mac OS X system that is supported by Lion results in a

Still testing, but the attached patch at least adds the most important stuff to make the install image boot and the installer start - both rely on the board ID.

I implemented the stuff to get the info from the host just for the darwin part, i hope other host platforms just break with this patch and i was a bit unsure about the VBOX_DMI_TABLE_SIZE. But at least it should be a good starting point :)

I can confirm that the attached patch allows a Lion VM to boot with EFI enabled and no need for a hacked bootloader. The only hiccup I have noticed so far is that on boot the VM does hang at "Waiting for DSMOS... macx_swapon SUCCESS" for half a minute or so before "DSMOS has arrived" shows up and the VM finishes booting.

The Lion installer does not operate similar to other operating system installers. Since it is set up to do a diskless install by downloading an app and then running it, a bunch of weird Apple-specific stuff happens.

As far as I can tell, the installer writes out a bunch of data to the disk and then sets startup disk and NVRAM properties that are not typically of the installation processes for other versions of OS X or other operating systems. The VM then has to reboot under these special conditions in order for the installation to complete.

So, passing board ID is pretty simple and allows Lion to boot---but there is a bunch of unknown voodoo that has to occur in order for the installer to succeed.

OK. But after the installation, should then everything else work OK? Specifically, here it is written that there are problems with shutdown and reboot. That computer is not automatically halted or rebooted. Also "About the Mac" does not work, they say.

OK. But after the installation, should then everything else work OK? Specifically, here it is written that there are problems with shutdown and reboot. That computer is not automatically halted or rebooted. Also "About the Mac" does not work, they say.

Startup/shutdown worked fine for me---aside from the half minute of hangtime while "Waiting for DSMOS". Did not try "About this Mac".

I don't see anything in that article that could be construed as "fully supported". If anything, they "look the other way" while the user does something illegal. It all comes down to trusting that having the user click on a box that says "I read the OS X SLA" will defend them in court. By contrast, VirtualBox is avoiding a lawsuit in the first place by explicitly supporting only those OS X versions for which the SLA allows virtualization.