Mac OS X guest
-
- Volunteer
- Posts: 3342
- Joined: 10. May 2007, 16:59
- Location: Israel
mjc:
>has this actually been tested in court yet?
>it not, then it isn't illegal yet, judges strike conditions in contracts alot
I'm not psystar, and have no will to fight Apple in court.
But I show, how to make it strict according to Apple's restrictive license, and still run Mac OS X as a guest inside VirtualBox.
I want people to understand, that it is possible.
-Technologov
>has this actually been tested in court yet?
>it not, then it isn't illegal yet, judges strike conditions in contracts alot
I'm not psystar, and have no will to fight Apple in court.
But I show, how to make it strict according to Apple's restrictive license, and still run Mac OS X as a guest inside VirtualBox.
I want people to understand, that it is possible.
-Technologov
Running OSX inside virtual machine inside OSX must be allowed for OSX Server:
http://www.appleinsider.com/articles/08 ... erver.html
Also, it doesn't seem like the job of one piece of software to enforce licenses of other software, which can change at any time.
http://www.appleinsider.com/articles/08 ... erver.html
Also, it doesn't seem like the job of one piece of software to enforce licenses of other software, which can change at any time.
-
- Volunteer
- Posts: 3342
- Joined: 10. May 2007, 16:59
- Location: Israel
-
- Posts: 6
- Joined: 13. Aug 2008, 18:25
- Location: Montreal, Quebec, Canada
- Contact:
What is this?
I've been reading this thread, and it seems quite a bit of work has been done to get MacOSX to run in VirtualBox, VMWare, QEmu and other virtualization software. Question is, does it really work?
Now, I run Ubuntu Linux 8.04. Vbox (latest, non-OSE) is on it. It runs WinXPSP2 like a charm. But reading the whole thread, I can see there are many problems, just from hardware protection (the hidden dongle and keys and all), so is it really worth all this trouble?
I've never used Mac-OSX; I would like to try, but I am not willing to dual boot my system. This is WHY I have VirtualBox to begin with - to test out different OSes.
If someone in the thread has managed to get it running, no bugs, decent speed, etc, then please, post a howto, or point us to the site where it is explained. I'd like to give it a whirl.
I'm sure I'm not the only one.
Now, I run Ubuntu Linux 8.04. Vbox (latest, non-OSE) is on it. It runs WinXPSP2 like a charm. But reading the whole thread, I can see there are many problems, just from hardware protection (the hidden dongle and keys and all), so is it really worth all this trouble?
I've never used Mac-OSX; I would like to try, but I am not willing to dual boot my system. This is WHY I have VirtualBox to begin with - to test out different OSes.
If someone in the thread has managed to get it running, no bugs, decent speed, etc, then please, post a howto, or point us to the site where it is explained. I'd like to give it a whirl.
I'm sure I'm not the only one.
Last edited by couzin2000 on 13. Aug 2008, 19:49, edited 1 time in total.
Couzin2000
-
- Volunteer
- Posts: 3342
- Joined: 10. May 2007, 16:59
- Location: Israel
-
- Posts: 3
- Joined: 4. Dec 2007, 14:46
Afraid
It seems obvious the virtualbox developers don´t want to make a virtual environment for the Mac OS X to run. I think this is the wrong way to do. If i can run windows 98/XP/Vista on a virtualbox system, it is correct others systems must run on it like Mac OS X. Maybe i´m wrong, but this what i think.
Re: Afraid
ok, tell that to apple, not vbox developers... try to make apple change their EULA... go on, I'll be waiting for you answer from themFuncky_Para wrote:It seems obvious the virtualbox developers don´t want to make a virtual environment for the Mac OS X to run. I think this is the wrong way to do. If i can run windows 98/XP/Vista on a virtualbox system, it is correct others systems must run on it like Mac OS X. Maybe i´m wrong, but this what i think.
I do not see Apple's policy or licensing changing in the near or distant future. There is not much incentive for anyone except those who wish to "Test" out various OS's.
The Apples licensing does not give much incentive to develop Virtualization for OS X, and Apple has no interest in allowing people to "Build" their own "macinstien" for fear of tarnishing their entire "User Experience".
( Like taking a mercedes engine and fitting it into a chev. With alot of work and tinkering you will be able to get the transmission to match up 'Fairly Good' and with enough customization possibly get a really good 'Ride' but it will not be the same as driving a mercedes. - Just a metaphor from Apples point of view )
If anyone MUST try OSX on their own X86 box, without setting up a dualboot system try PearPC.
The Apples licensing does not give much incentive to develop Virtualization for OS X, and Apple has no interest in allowing people to "Build" their own "macinstien" for fear of tarnishing their entire "User Experience".
( Like taking a mercedes engine and fitting it into a chev. With alot of work and tinkering you will be able to get the transmission to match up 'Fairly Good' and with enough customization possibly get a really good 'Ride' but it will not be the same as driving a mercedes. - Just a metaphor from Apples point of view )
If anyone MUST try OSX on their own X86 box, without setting up a dualboot system try PearPC.
tested with vb 2.0.2 - crash
i did use a well known patched version of 10.5, and vb crashes around the same place as before (when the screen size changes at boot time) :
00:02:07.251 Guest Log: BIOS: Booting from CD-ROM...
00:02:07.256 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00000000 w=720 h=400 bpp=0 cbLine=0x0
00:02:33.886 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=b139e000 w=1024 h=768 bpp=32 cbLine=0x1000
00:02:34.500 VERR_REM_TOO_MANY_TRAPS -> uTrap=e error=3 next_eip=001a8e7e eip=001a8e7e cr2=000fff3c
00:02:07.251 Guest Log: BIOS: Booting from CD-ROM...
00:02:07.256 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00000000 w=720 h=400 bpp=0 cbLine=0x0
00:02:33.886 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=b139e000 w=1024 h=768 bpp=32 cbLine=0x1000
00:02:34.500 VERR_REM_TOO_MANY_TRAPS -> uTrap=e error=3 next_eip=001a8e7e eip=001a8e7e cr2=000fff3c
-
- Volunteer
- Posts: 129
- Joined: 16. Sep 2008, 23:22
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Ubuntu, Chromium OS, Windows
- Location: Internet
- Contact:
I think you'll find mercedes doesn't give a damn who buys their engines, or what they do with them, provided they don't show up expecting warranty service.amagine wrote:Like taking a mercedes engine and fitting it into a chev. With alot of work and tinkering you will be able to get the transmission to match up 'Fairly Good' and with enough customization possibly get a really good 'Ride' but it will not be the same as driving a mercedes. - Just a metaphor from Apples point of view
I used a 'Kalyway' 10.5.2 Leopard ISO.
Even QEMU gets past where VirtualBox 2.0.2 cannot. I get to Darwin's verbose logging screen, and it stops at:
Forever apparently.
With VirtualBox 2.02, with -x (safe mode, where it does not change VESA state until all drivers are loaded) as a command line it successfully loads all drivers then VirtualBox responds with 'Guru Meditation' error message, to which I click OK because Ignore does nothing.
Exception from log:
Still the same issue as a lot of people it seems. Even if OS X does get to its GUI, it will run dog slow like the Deadmoo image did for VMWare, until Guest Additions are created for it. The performance between the Deadmoo image on VMWare and PearPC running 10.4 was comparable, because they were almost exactly the same speed, yet PearPC is running PPC code on x86, and VMWare is putting most of the code it can into ring 0 of an already existent x86 processor.
I can always be hopeful.
Even QEMU gets past where VirtualBox 2.0.2 cannot. I get to Darwin's verbose logging screen, and it stops at:
Code: Select all
ACPI CA 20051117 [debug level=0 layer=0]
dsmos: Initializing...
dsmos: Hook and decryption contexts set!
dsmos: Starting...
With VirtualBox 2.02, with -x (safe mode, where it does not change VESA state until all drivers are loaded) as a command line it successfully loads all drivers then VirtualBox responds with 'Guru Meditation' error message, to which I click OK because Ignore does nothing.
Exception from log:
Code: Select all
00:01:31.116 VERR_REM_TOO_MANY_TRAPS -> uTrap=e error=3 next_eip=00000000001a86f5 eip=00000000001a86f5 cr2=000fff3c
00:01:31.116 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:31.116 !!
00:01:31.116 !! Guru Meditation -2304 (VERR_REM_TOO_MANY_TRAPS)
00:01:31.116 !!
00:01:31.116 !!
00:01:31.116 !! {mappings, <NULL>}
00:01:31.116 !!
00:01:31.116
00:01:31.116 The mappings are FLOATING.
00:01:31.116 00000000a0000000 - 00000000a07fffff Hypervisor Memory Area
00:01:31.116 !!
00:01:31.116 !! {hma, <NULL>}
00:01:31.116 !!
I can always be hopeful.