Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Trying to add support for OSX on virtualbox #770

Merged

Conversation

trinitronx
Copy link
Contributor

So don't merge this one just yet... I haven't gotten it totally working
yet. This PR is a WIP, and a plea to the community for some help getting
it working. Here's a screenshot to show how close I've gotten:

So close...

Almost there! I believe the problem is that the darwin kernel does not
recognize the root disk .vdi that VirtualBox has connected.
If anyone knows how to trick OSX into recognizing the disk or SATA
controller correctly, help would be appreciated!

@JeanMertz
Copy link

Can't really help you with your problem, but a 👍 from me. I've just now successfully started an osx image using veewee and vmware, but using virtualbox gave me a "not started" error (this is without using your PR).

I hope you can get this working. I don't mind paying the extra $$$ for vmware support in vagrant, but it makes it impossible to include a Vagrantfile with an oss project that requires tests to be run on osx.

edit: Using your fork, I got as far as you got, so at least you got one confirmation of it working for others the same as it did for you :)

schermafbeelding 2013-09-01 om 17 47 59

@mpapis
Copy link
Collaborator

mpapis commented Sep 30, 2014

closing in favor of #848

@mpapis mpapis closed this Sep 30, 2014
@trinitronx
Copy link
Contributor Author

@mpapis This one really isn't mutually exclusive with #848, so I suppose I'm not understanding why you say in favor of that one. This PR is actually more like #768, because it includes the commits that comprise #768.

So I'd ask whether you're looking to choose between these. I believe #768 is working fully to solve the problem it is meant to, and this one (#770) is adding on top of that in order to use the produced result of the prepare_veewee_iso.sh script with virtualbox.

So the way I figured it, the choice is whether or not to add semi-broken OSX virtualbox support or not. If you check the commits you should see what I mean, and that it's adding on the setting of OSTypes to tell virtualbox what type of OSX it is (since vmware fusion already has correct OSTypes, it is supported too, though I couldn't quite get that to boot either in #848).

Please forgive me if I'm just misunderstanding the thought process or not seeing it from your perspective. I just wanted to try and make sure I'm making the case for this PR considering I had not so great luck with OSX on either virtualbox or vmware fusion.

Though FWIW, my experience with Mountain Lion on vmware fusion was really good actually! If I recall... I think it was just the combo of Mavericks and VMWare and virtualbox with any version of OSX that didn't work. Sorry I can't give a full test matrix of what worked or didn't at this point, as it's been a while.

@mpapis
Copy link
Collaborator

mpapis commented Oct 1, 2014

oh ok, I'm sorry for confusing them - reopening

@mpapis mpapis reopened this Oct 1, 2014
mpapis added a commit that referenced this pull request Oct 1, 2014
…-templates

Trying to add support for OSX on virtualbox
@mpapis mpapis merged commit 85e856c into jedi4ever:master Oct 1, 2014
@mpapis
Copy link
Collaborator

mpapis commented Oct 1, 2014

merged - anything that moves us closer to the target is better ;) thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants