#16570 closed defect (invalid)
Os X on AMD processor (AMD-v enabled and HyperV installed) failing to boot
| Reported by: | AleksAndros | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.18 |
| Keywords: | Cc: | ||
| Guest type: | OSX Server | Host type: | Windows |
Description
I guess this is piece of cake for you, but still couldn't find the exact thing that causes the Guru crash. As of subject, AMD-V is enabled in Bios, and Hyper-V is installed (though not active, or it'll just give me 32-bit versions of OSs). I report my log, hoping for you to explain me what's happening. I guess it's the
00:00:04.105234 IEM: wrmsr(0x8b,0x0`00000000) -> #GP(0)
piece of code, but I have no idea how to solve it, and I could probably be wrong too.
Attachments (1)
Change History (5)
by , 8 years ago
comment:1 by , 8 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
I'm sorry, Mac OS X guests are not supported on non-Apple hardware for legal reasons.
comment:2 by , 8 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
I know that and I'm assuming the risk. Besides that, I don't think that it matters in my case. For apparently the same reason (but still to find), I cannot virtualize an Android on AndroidStudio, I can't emulate any VM on Hyper-V console, etc. I just chose this because I observed you seem to know a lot more of what's happening behind the curtains than the other ones. So please, forget the fact that that's an OSx (if necessary, I'll report a log of some other OS) and help me figure out what's going on.
comment:3 by , 8 years ago
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
This defect is about Mac OS X guests running on AMD hardware. This setup is not supported for legal reasons, period. It's not only your risk, it's also our risk.
comment:4 by , 8 years ago
If Oracle (which owns VirtualBox) helps you, the Apple can sue Oracle. It's not about you. You're not assuming any risk at all. You're simply going to be the spark responsible for a (potential) fire.
Plus, IMHO, if you want to play it a hacker, start hacking. Sorry for not sugar coating it for you, but those are the facts. Plain cold and simple.
Log