Jump to content
29 posts in this topic

Recommended Posts

Hi All, 

 

I am trying to get Mac OS X Server 10.4 Tiger installed on a virtual machine. 

  • I have the original installation disc for Mac OS X Server 10.4 Tiger
  • Macbook late 2011 - OS X 10.10 - Intel i7 2.4GHz (Sandy Bridge) - Fusion 7 Installed
  • ESXi 6.0 Hosts - Intel Xeon E5-2680 v3 (Haswell) (these hosts can be downgraded to run 5.5 if needed)

I can create a machine under my Fusion as Mac OS X 10.5 and boot to the physical 10.4 Tiger disk, but then it fails with;

  • "the cpu has been disabled by the guest operating system"

I know to get around this I have to change the CPUID of the virtual machine in the VMX file, which is fine. However I cannot find the correct CPUID to use, 

 

VMware offer a CPU identification tool (https://my.vmware.com/web/vmware/details?productId=136&downloadGroup=CPU%20IDENTIFICATION%20UTILITY)

 

But this will not boot on a Server running OS X 10.4 Tiger, due to the EFI, if you boot this tool on any machine with BIOS, it works perfectly. 

 

I am unaware of any other tools or commands I can run to identify the CPUID on the hardware running tiger to help me figure out the correct CPUID to run the VM in fusion. 

 

Once up and running in fusion, I hope to port it over to ESXi 6.0. 

 

Can anyone help me with with the correct CPUID? If possible, we'd like to do it this way rather than using any unlocker tools, as we need the OS for a custom application, so are trying to keep everything working as untouched as possible.

 

Thank you in advance

Hi All, 

 

I am trying to get Mac OS X Server 10.4 Tiger installed on a virtual machine. 

  • I have the original installation disc for Mac OS X Server 10.4 Tiger
  • Macbook late 2011 - OS X 10.10 - Intel i7 2.4GHz (Sandy Bridge) - Fusion 7 Installed
  • ESXi 6.0 Hosts - Intel Xeon E5-2680 v3 (Haswell) (these hosts can be downgraded to run 5.5 if needed)

I can create a machine under my Fusion as Mac OS X 10.5 and boot to the physical 10.4 Tiger disk, but then it fails with;

  • "the cpu has been disabled by the guest operating system"

I know to get around this I have to change the CPUID of the virtual machine in the VMX file, which is fine. However I cannot find the correct CPUID to use, 

 

VMware offer a CPU identification tool (https://my.vmware.com/web/vmware/details?productId=136&downloadGroup=CPU%20IDENTIFICATION%20UTILITY)

 

But this will not boot on a Server running OS X 10.4 Tiger, due to the EFI, if you boot this tool on any machine with BIOS, it works perfectly. 

 

I am unaware of any other tools or commands I can run to identify the CPUID on the hardware running tiger to help me figure out the correct CPUID to run the VM in fusion. 

 

Once up and running in fusion, I hope to port it over to ESXi 6.0. 

 

Can anyone help me with with the correct CPUID? If possible, we'd like to do it this way rather than using any unlocker tools, as we need the OS for a custom application, so are trying to keep everything working as untouched as possible.

 

Thank you in advance

 

Hi

 

I used these VMX parameters to boot a 10.4 desktop version of OS X.

 

board-id.reflectHost = "TRUE"
hw.model.reflectHost = "FALSE"
hw.model = "iMac5,1"


cpuid.inhibitDarwinMasks = "TRUE"
monitor_control.enable_fullcpuid = "TRUE"
cpuid.0.eax = "0000:0000:0000:0000:0000:0000:0000:1010"
cpuid.0.ebx = "0111:0101:0110:1110:0110:0101:0100:0111"
cpuid.0.ecx = "0110:1100:0110:0101:0111:0100:0110:1110"
cpuid.0.edx = "0100:1001:0110:0101:0110:1110:0110:1001"
cpuid.1.eax = "0000:0000:0000:0000:0000:0110:1111:0110"
cpuid.1.ebx = "0000:0001:0000:0010:0000:1000:0000:0000"
cpuid.1.ecx = "0000:0000:0000:0000:1110:0011:1011:1101"
cpuid.1.edx = "1011:1111:1110:1011:1111:1011:1111:1111"
cpuid.2.eax = "0000:0101:1011:0000:1011:0001:0000:0001"
cpuid.2.ebx = "0000:0000:0101:0110:0101:0111:1111:0000"
cpuid.2.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.2.edx = "0010:1100:1011:0100:0011:0000:0100:1001"
cpuid.3.eax = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.3.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.3.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.3.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.0.eax = "0000:0100:0000:0000:0000:0001:0010:0001"
cpuid.4.0.ebx = "0000:0001:1100:0000:0000:0000:0011:1111"
cpuid.4.0.ecx = "0000:0000:0000:0000:0000:0000:0011:1111"
cpuid.4.0.edx = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.4.1.eax = "0000:0100:0000:0000:0000:0001:0010:0010"
cpuid.4.1.ebx = "0000:0001:1100:0000:0000:0000:0011:1111"
cpuid.4.1.ecx = "0000:0000:0000:0000:0000:0000:0011:1111"
cpuid.4.1.edx = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.4.2.eax = "0000:0100:0000:0000:0100:0001:0100:0011"
cpuid.4.2.ebx = "0000:0011:1100:0000:0000:0000:0011:1111"
cpuid.4.2.ecx = "0000:0000:0000:0000:0000:1111:1111:1111"
cpuid.4.2.edx = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.4.3.eax = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.3.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.3.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.3.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.5.eax = "0000:0000:0000:0000:0000:0000:0100:0000"
cpuid.5.ebx = "0000:0000:0000:0000:0000:0000:0100:0000"
cpuid.5.ecx = "0000:0000:0000:0000:0000:0000:0000:0011"
cpuid.5.edx = "0000:0000:0000:0010:0010:0010:0010:0000"
cpuid.6.eax = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.6.ebx = "0000:0000:0000:0000:0000:0000:0000:0010"
cpuid.6.ecx = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.6.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.7.0.eax = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.7.0.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.7.0.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.7.0.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.8.eax = "0000:0000:0000:0000:0000:0100:0000:0000"
cpuid.8.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.8.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.8.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.9.eax = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.9.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.9.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.9.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.a.eax = "0000:0111:0010:1000:0000:0010:0000:0010"
cpuid.a.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.a.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.a.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000000.eax = "1000:0000:0000:0000:0000:0000:0000:1000"
cpuid.80000000.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000000.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000000.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000001.eax = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000001.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000001.ecx = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.80000001.edx = "0010:0000:0001:0000:0000:1000:0000:0000"
cpuid.80000002.eax = "0110:0101:0111:0100:0110:1110:0100:1001"
cpuid.80000002.ebx = "0010:1001:0101:0010:0010:1000:0110:1100"
cpuid.80000002.ecx = "0111:0010:0110:1111:0100:0011:0010:0000"
cpuid.80000002.edx = "0100:1101:0101:0100:0010:1000:0110:0101"
cpuid.80000003.eax = "0100:0011:0010:0000:0011:0010:0010:1001"
cpuid.80000003.ebx = "0010:0000:0010:0000:0101:0101:0101:0000"
cpuid.80000003.ecx = "0010:0000:0010:0000:0010:0000:0010:0000"
cpuid.80000003.edx = "0101:0100:0010:0000:0010:0000:0010:0000"
cpuid.80000004.eax = "0011:0000:0011:0000:0011:0110:0011:0111"
cpuid.80000004.ebx = "0010:0000:0100:0000:0010:0000:0010:0000"
cpuid.80000004.ecx = "0011:0011:0011:0011:0010:1110:0011:0010"
cpuid.80000004.edx = "0000:0000:0111:1010:0100:1000:0100:0111"
cpuid.80000005.eax = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000005.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000005.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000005.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000006.eax = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000006.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000006.ecx = "0001:0000:0000:0000:1000:0000:0100:0000"
cpuid.80000006.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000007.eax = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000007.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000007.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000007.edx = "0000:0000:0000:0000:0000:0000:0000:0000"
#cpuid.80000008.eax = "0000:0000:0000:0000:0011:0000:0010:0100"
#cpuid.80000008.ebx = "0000:0000:0000:0000:0000:0000:0000:0000"
#cpuid.80000008.ecx = "0000:0000:0000:0000:0000:0000:0000:0000"
#cpuid.80000008.edx = "0000:0000:0000:0000:0000:0000:0000:0000"

It was more complex than just the usual CPUID mask for other OS X variants. This should work without an unlocker on Fusion on real Mac hardware. However you do not say if the ESXi servers are Apple hardware. If not they will need the unlocker. Remember the unlocker does not change anything inside the guest OS, just the virtual hardware presented tot he guest, specifically the SMC controller needed to run OS X.

 

 

Hi, 

 

I've ran the unlocker 2.0.8 tool on ESXi 6.0 build 3380124

 

The installation seems to have run fine, as using vCenter I can power on a Mac OS X screen, but I hit two issues, 

 

I get a MKS failure when viewing the console, the process crashes, constantly, whenever I boot the VM and it loads, I see a VMware screen, then apple screen, then then "VMware remote MKS has stopped responding". This doesn't happen with the Windows and Linux VMs I am running on the system.

 

If i look at events for the VM, I can see constant reboots of the VM, with lines logged such as

 

Message on Mac OS X Server 10.4.7 (Retail-Disc): Click OK to restart the virtual machine or
Cancel to power off the virtual machine.
info
28/01/2016 15:11:55
Mac OS X Server 10.4.7 (Retail-Disc)
User

 

 

It's worth noting, I am running Mac OS X Server10.4.7 built off the retail disc, and using the CPUID from above.

 

The ESXi CPU is Intel Xeon E5-2680 v3 (Haswell)

 

The VM was built and running in Fusion 7, then I've connected my Fusion 7 machine to the ESXi server to upload the VM. The CPUID settings are stripped out, which I believe is a known issue. So I enter them again using WINSCP to browse the datastore and edit the VMX file, 

 

I also add the SMC.version = "0" line 

 

I've attached a copy of the VMX in a  zip file

 

Any help would be appreciated

 

mac os x 10.4.7 retail disc install.zip

Hi, 

 

I've ran the unlocker 2.0.8 tool on ESXi 6.0 build 3380124

 

The installation seems to have run fine, as using vCenter I can power on a Mac OS X screen, but I hit two issues, 

 

I get a MKS failure when viewing the console, the process crashes, constantly, whenever I boot the VM and it loads, I see a VMware screen, then apple screen, then then "VMware remote MKS has stopped responding". This doesn't happen with the Windows and Linux VMs I am running on the system.

 

If i look at events for the VM, I can see constant reboots of the VM, with lines logged such as

 

 

It's worth noting, I am running Mac OS X Server10.4.7 built off the retail disc, and using the CPUID from above.

 

The ESXi CPU is Intel Xeon E5-2680 v3 (Haswell)

 

The VM was built and running in Fusion 7, then I've connected my Fusion 7 machine to the ESXi server to upload the VM. The CPUID settings are stripped out, which I believe is a known issue. So I enter them again using WINSCP to browse the datastore and edit the VMX file, 

 

I also add the SMC.version = "0" line 

 

I've attached a copy of the VMX in a  zip file

 

Any help would be appreciated

 

Can't see anything wrong with the VMX. Can you zip up  the vmware.log file and post please?

 

Belay that: there are no  

cpuid.inhibitDarwinMasks = "TRUE"
ich7m.present = "TRUE"
monitor_control.enable_fullcpuid = "TRUE"
smc.present = "TRUE"
lines in the VMX file.

 

Wow thanks, that looks to have worked, 

 

I'm sure I checked out the config between fusion and ESXi after the upload, but they again I've bene doing that much testing and playing around between fusion and VMware, its very very hard to to keep up with myself. 

 

My initial machine I had working on fusion is now working within ESXi! Yay.

 

I'll go through the rest of the machines etc tomorrow. 

 

I'll try and get around to doing a write up on here about everything I've done, what the environment is etc, so others know in the future. It's been such a learning curve understanding the Mac OS X boot checks etc, the security procedures in place. And I spent days trying to find a way to work out the CPUID Mask myself! luckily I came to here and someone had done it!

 

Thank you both for your help

 

Can't see anything wrong with the VMX. Can you zip up  the vmware.log file and post please?

 

Belay that: there are no  

cpuid.inhibitDarwinMasks = "TRUE"
ich7m.present = "TRUE"
monitor_control.enable_fullcpuid = "TRUE"
smc.present = "TRUE"
lines in the VMX file.

 

 

 

Do you know why if I've created an ISO of the retail disc, I cannot boot to it? I'm attaching it as a ISO on my local machine and from the datastore with no luck

 

it was the same in fusion, however in fusion i can boot from a disc physically in my machine which works, for both the retail disc, and a DVD-R with the retail disc iso burnt to it,

Does anyone know which fusion product I need to get a copy of vmware tools that will install on 10.4.11? I've installed fusion 2.0.8 inside of my Mac VM (funnily enough) to get access to the darwin.iso file from that install, 

 

I launch the VMware tools package from inside the first level .pkg file going to /Contents/Resources/VMware Tools.pkg, but it hangs on "Finishing installation" "Running VMware Tools Installer Script" and goes no further

 

If I launch the VMware tools installer from direct from the mounted disk, it doesn't do anything. Hence going into the installer itself to dig out the pkg file

Does anyone know which fusion product I need to get a copy of vmware tools that will install on 10.4.11? I've installed fusion 2.0.8 inside of my Mac VM (funnily enough) to get access to the darwin.iso file from that install, 

 

I launch the VMware tools package from inside the first level .pkg file going to /Contents/Resources/VMware Tools.pkg, but it hangs on "Finishing installation" "Running VMware Tools Installer Script" and goes no further

 

If I launch the VMware tools installer from direct from the mounted disk, it doesn't do anything. Hence going into the installer itself to dig out the pkg file

 

VMware never supported Tiger (10.4) only from Leopard (10.5). I just looked and the tools installer has a check to see if the OS version is 10.5 as a minimum. Options may be to fix the package check, or manually extract on host OS X and install. I will take a look but busy with work at the moment.

 

Update: I have hacked the installer package to allow 10.4. I don't have a Tiger system to test, but feel free to give it a go.

 

http://daveparsons.net/downloads/VMware%20Tools%20Tiger.pkg

Hey cheers for that, unfortuantely that package still throws the 10.5 error, I guess I'll do a bit more research, 

 

I found that I can download the fusion tools up to version 5.0.5 which will install into the OS, ESXi still doesnt pick this up as having VMware tools installed. 

 

https://softwareupdate.vmware.com/cds/vmw-desktop/fusion/

Hey cheers for that, unfortuantely that package still throws the 10.5 error, I guess I'll do a bit more research, 

 

I found that I can download the fusion tools up to version 5.0.5 which will install into the OS, ESXi still doesnt pick this up as having VMware tools installed. 

 

https://softwareupdate.vmware.com/cds/vmw-desktop/fusion/

Does it show the error during installation or after it has installed? (I wouldn't bother looking around for other tools, they actually ship in ESXi.)

Does it show the error during installation or after it has installed? (I wouldn't bother looking around for other tools, they actually ship in ESXi.)

No it literally just said, needs to be installed on 10.5 or higher again for the package you give me, 

 

and the fusion 5.0.5 tools installs fine, but in the VMware vCenter application, when I click on the VM, it says "VMware tools not installed" 

 

Ive not seen any errors about it, maybe they will be contained in the VMware.log file, which I can check tomorrow

From my experience running Tiger in VMware Fusion on a haswell based rMBP14,2, the TLB CPUID information is the only one required.

I've ran into this recently and the bare minimal is:

 

cpuid.2.eax="00000101101100001011000100000001"

cpuid.2.ebx="00000000010101100101011111110000"
cpuid.2.ecx="00000000000000000000000000000000"
cpuid.2.edx="00101100101101000011000001001000"
 
Regarding the video driver, I've patched version 1.2.5 of Zenith's video driver (just the FB) and it works like a charm. The only functions that need replacing are:
IOConnectCallMethod and PE_parse_boot_arg. For the GL Driver, some attention needs to be payed to the GCC Atomic operations, which are not supported on the Tiger Xcode. Since the kernel doesn't support weak linking, you need a separate build for Tiger. Let me know if you want a copy of the working FrameBuffer and the source code.
We still need a port of the open-vm-tools to mac os x as the VMware provided tools depend on newer APIs at the IOKit level. Maybe someone can grab zenith432's GL branch and work on porting it to Tiger further on. Regarding iconv, I've tried replacing libiconv.2.dylib and realized that just replacing the import table is sufficient as no newer APIs are needed.
  • Like 1

 

From my experience running Tiger in VMware Fusion on a haswell based rMBP14,2, the TLB CPUID information is the only one required.

I've ran into this recently and the bare minimal is:

 

cpuid.2.eax="00000101101100001011000100000001"

cpuid.2.ebx="00000000010101100101011111110000"
cpuid.2.ecx="00000000000000000000000000000000"
cpuid.2.edx="00101100101101000011000001001000"
 
Regarding the video driver, I've patched version 1.2.5 of Zenith's video driver (just the FB) and it works like a charm. The only functions that need replacing are:
IOConnectCallMethod and PE_parse_boot_arg. For the GL Driver, some attention needs to be payed to the GCC Atomic operations, which are not supported on the Tiger Xcode. Since the kernel doesn't support weak linking, you need a separate build for Tiger. Let me know if you want a copy of the working FrameBuffer and the source code.
We still need a port of the open-vm-tools to mac os x as the VMware provided tools depend on newer APIs at the IOKit level. Maybe someone can grab zenith432's GL branch and work on porting it to Tiger further on. Regarding iconv, I've tried replacing libiconv.2.dylib and realized that just replacing the import table is sufficient as no newer APIs are needed.

 

 

 

 

 

hey cheers for this, going to be honest, after the CPUID bit non of that made much sense to me, other than most of the VMtools won't work, which is a shame, 

 

I just want ESXi to see the OS for performance stuff. 

 

I'll try the shorter CPUID stuff and see if that works on my environment, do you know anything about getting 10GB working on Tiger in a VM?

hey cheers for this, going to be honest, after the CPUID bit non of that made much sense to me, other than most of the VMtools won't work, which is a shame, 

 

I just want ESXi to see the OS for performance stuff. 

 

I'll try the shorter CPUID stuff and see if that works on my environment, do you know anything about getting 10GB working on Tiger in a VM?

 

Agree very useful information. The data I used was captured from an old iMac of mine and a cpuid utility I modified to save in VMX format. Finding the essential info helps me understand what is important.

 

@d3vi1-alter - I don't have any free time to look at compiling the tools as too busy with work and family at present. However happy to test and also package into the unlocker if that helps.

 

@macbootissues22 - I will load a Tiger VM onto ESXi (currently using Fusion and Workstation) and see if I can see the OS correctly. Also not sure what the issue with 10GB of memory is, can you explain a bit more please? Is it just impossible to assign 10GB to the VM, or Tiger not seeing that amount of memory?

Agree very useful information. The data I used was captured from an old iMac of mine and a cpuid utility I modified to save in VMX format. Finding the essential info helps me understand what is important.

 

@d3vi1-alter - I don't have any free time to look at compiling the tools as too busy with work and family at present. However happy to test and also package into the unlocker if that helps.

 

@macbootissues22 - I will load a Tiger VM onto ESXi (currently using Fusion and Workstation) and see if I can see the OS correctly. Also not sure what the issue with 10GB of memory is, can you explain a bit more please? Is it just impossible to assign 10GB to the VM, or Tiger not seeing that amount of memory?

 

Sorry I was referring to 10GB networking, the only adapter I can add to the VM in ESXi is the e1000, 

 

If I change the VM OS type, to anything other than Apple 10.5 32bit, the VM refuses to boot,

If I change to 10.6 32/64bit, I just get a black screen when booting 

10.7 32bit it shows your apple hardware has changed you need to reboot your system.

 

All other options, I get the EFI boot options screen

 

What tools did you use to capture the data from your iMac ?

Sorry I was referring to 10GB networking, the only adapter I can add to the VM in ESXi is the e1000, 

 

If I change the VM OS type, to anything other than Apple 10.5 32bit, the VM refuses to boot,

If I change to 10.6 32/64bit, I just get a black screen when booting 

10.7 32bit it shows your apple hardware has changed you need to reboot your system.

 

All other options, I get the EFI boot options screen

 

What tools did you use to capture the data from your iMac ?

 

Ah go it. I wonder if manually changing the hardware type in the VMX will work? Will have to check out the test VM I have available.

 

Update: Maybe this compiled for Tiger would work. http://www.insanelymac.com/forum/topic/205771-appleintele1000ekext-for-108107106105/

 

The  tests on the OS type do not surprise me as they change settings for various parameters on the virtual hardware chassis, and as they are hidden it is hard to know what they are doing. Best bet is to stick with 10.5.

 

The tool is on my GitHub repository https://github.com/DrDonk/cpuid. It is forked from another tool and I updated the ability to dump in VMware format. Have some additional changes which haven't pushed yet but can send an executable if you want one, except for Windows at present, so OS X and Linux/ESXi.

  • 4 weeks later...

A while back I had a nicely set up VM for Tiger running under VMware Fusion. But I had no backups and the disk crashed.

 

Today, I built another one. But I am lacking the audio driver that can be installed on 10.4. Most of the AppleAC97Audio drivers I found require 10.5 and up. I found one that loaded ok with kextload -t, but it is not working anyway.

 

Help would be appreciated.

 

I also do not seem to be able to change the display setting using Graphics Mode in com.boot.plist. Any other approaches?

 

Thanks.

 

  • 4 weeks later...

Hi guys Itried to get Tiger on VMWARE with your help but to no avail. I found VirtualBox to work better with it... I have everything working except for proper QE/CI, but it still works pretty decently without it. Is there any knowledge you could take from VMWARE and apply it to VIRTUALBOX?

 

Check out the video I made as proof of concept of waht I've achieved.

It's practically a vanilla installation.. The only error I get is on boot is GFX0 family matching specific fails

Anyone knows how to extract acpi tables from VirtualBox or from OSX Tiger? Any ioreg utilities? I cant find any for Tiger.. If I could, at least I could try and do something about the graphics... Thanks for your help!

 

  • 2 weeks later...
  • 3 weeks later...

So its been a while since I've been able to sit down and work on this environment, 

 

The VM's themselves run happily in ESXi 6.0, 

 

I'm going to see if I get another adapter working on the VM by editing the VMX file, and I also have issues with the graphics, I need a way to change them from 1024x768 but no options appear, and of course there is no vmware tools support.


Ah go it. I wonder if manually changing the hardware type in the VMX will work? Will have to check out the test VM I have available.

 

Update: Maybe this compiled for Tiger would work. http://www.insanelymac.com/forum/topic/205771-appleintele1000ekext-for-108107106105/

 

The  tests on the OS type do not surprise me as they change settings for various parameters on the virtual hardware chassis, and as they are hidden it is hard to know what they are doing. Best bet is to stick with 10.5.

 

The tool is on my GitHub repository https://github.com/DrDonk/cpuid. It is forked from another tool and I updated the ability to dump in VMware format. Have some additional changes which haven't pushed yet but can send an executable if you want one, except for Windows at present, so OS X and Linux/ESXi.

 

If you could send me this tool it would be pretty useful, 

 

thank you

So its been a while since I've been able to sit down and work on this environment, 

 

The VM's themselves run happily in ESXi 6.0, 

 

I'm going to see if I get another adapter working on the VM by editing the VMX file, and I also have issues with the graphics, I need a way to change them from 1024x768 but no options appear, and of course there is no vmware tools support.

 

If you could send me this tool it would be pretty useful, 

 

thank you

Here you go http://daveparsons.net/downloads/cpuid.zip

 

To get a format for VMware VMX files use: cpuid -d -o vmware

×
×
  • Create New...