- #Windows virtualbox install mac os x mac os x#
- #Windows virtualbox install mac os x install#
- #Windows virtualbox install mac os x Patch#
- #Windows virtualbox install mac os x full#
This allowed me to use a custom resolution.
#Windows virtualbox install mac os x install#
I managed to get a legacy install of clover with Sierra. OK hope this helps someone or even better that someone can help me! My host system in this case is Mavericks/64 bit. I tried with both Debian and upstream releases of Virtualbox (5.1.8, 5.0.26 and 5.0.0) before I found that 4.3.30 would work. Whether this means that they are not old enough, or something else 'new' is polluting my system and stopping them from working I don't know.įYI my host system is Debian/sid.
![windows virtualbox install mac os x windows virtualbox install mac os x](http://2.bp.blogspot.com/-dUvm8SqskwA/TyXC5aruxVI/AAAAAAAAAiQ/zKrngR1j2xE/s1600/virtualbox+storage.png)
I don't imagine the kernel or Virtualbox version numbers are critical, just that they are 'old'(-ish).īut what I find particularly intriguing is that the above error message still appears on a fresh VM with the old kernel and old Virtualbox.
#Windows virtualbox install mac os x Patch#
What I have found is that by booting my computer with an old kernel (3.2) and installing Virtualbox 4.3.30 (NB had to patch the installation file to handle cope with a changed kernel API, see: )I was able to boot my VM as it was (ie without the extradata items).
#Windows virtualbox install mac os x full#
I've now spent a full day looking into all this, and can't really afford to spend any more time. This seems to indicate that the machines can't be created in the same way any more. I then tried to create a new machine from scratch, and found exactly the same message. Ĭonfiguration error: Querying "UUID" failed (VERR_CFGM_VALUE_NOT_FOUND). had disappeared from the VM) I put them back and that's when I started getting the following message:įailed to open a session for the virtual machine. On investigating I found that all the extradata items (" VBoxInternal / Devices / efi / 0 / Config / DmiSystemProduct" etc. I generally don't ever shut them down but save the state, and I don't actually use them very often.Īnyway I recently rebooted one of them (wanted to reduce the memory allocated to the VM) and when I went to reboot, it hung at the 'boot0: done' stage. I've been running a couple of virtual Hackintoshes as described in this forum for a while now. Hello all, not sure if this is the best place to post but wanted to give some feedback on recent experiences. Thanks for the guide BTW, it was much appreciated. A custom resolution would be better, but this seems an acceptable workaround. The fonts are a bit small now, but you can increase them in quite a few places to compensate. "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" setextradata "Sera" "GUI/ScaleFactor" 0.875 "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" setextradata "Sera" "VBoxInternal2/EfiGopMode" 5
![windows virtualbox install mac os x windows virtualbox install mac os x](https://cdn.redmondpie.com/wp-content/uploads/2010/07/SnowLeopardinVirtualBox8.jpg)
So instead I used the 1920x1200 setting scaled down: Also the fonts end up a bit large and there isn't enough pixel resolution. "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" setextradata "Sera" "GUI/ScaleFactor" 1.15Īnd while it works, it's not all that sharp. "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" setextradata "Sera" "VBoxInternal2/EfiGopMode" 4 I tried scaling up the 1440x900 setting like this: Given that it simply isn't possible to get a custom screen resolution to work with booting El Capitan or Sierra via EFI in VB, I had to decide what to do with my 1680x1050 screen (1.6:1 aspect ratio).
![windows virtualbox install mac os x windows virtualbox install mac os x](https://techrechard.com/wp-content/uploads/2020/12/asdf-1024x585.jpg)
I think that this is a Mac-specific problem as Win and Linux guests have guest additions. I'm inclined to report this as a VB bug, but first I need to replicate this on a Mac host rather than a Win host, or they'll ignore me.
#Windows virtualbox install mac os x mac os x#
It's as if running the machine in a recent version of VB somehow does something to the install of Mac OS X in the virtual machine that can't be undone. But the fact that a downgrade of VB doesn't fix my problems suggests that it's more complex. The question is - is this a Mac OS X os issue or a VB one? The fact that you reported VMWare as having the same problems suggests a Mac OS X one. Moreover, if I downgrade to VB 4.3 and open that ML machine, the custom resolution doesn't work anymore - ML now has the same screen resolution problems. What is particularly frustrating is that I was running Mountain Lion in VB 4.3.30 and the custom resolution trick used to work. I've done a lot of searching and tried as many things as I could think of without success.
![windows virtualbox install mac os x windows virtualbox install mac os x](https://i2.wp.com/techsprobe.com/wp-content/uploads/2019/04/maxresdefault.jpg)
EfiGopMode works but not a custom resolution. I've just used this guide to successfully install Sierra in VB 5.1.6 and have exactly the same problem. For me VBoxManage setextradata "OS X VM" "VBoxInternal2/EfiGopMode" N works fine, but custom resolution (for widescreen) is not working, However, it seems there is a problem with ElCapitan, because VmWare has similar problems.