Jump to content
Donk

VMware Mac OS X Guest Package for ESX, Workstation, Player, Server and Fusion

2,213 posts in this topic

Recommended Posts

I have also added those but Leopard still fails to boot after installation. I can't catch what was the last line in verbose mode as VMware puts the screen black too fast.

 

Sorry I have no other solution. This seems to be a problem with many of the newer processors.

 

UPDATE: Can you take a look at this document and boot from the CD utility and post results here?

Share this post


Link to post
Share on other sites
Advertisement
Can you post the VMX file please? Possibly haven't set the adapter to emulate Intel E1000.

 

Found the answer by myself.

 

I think VMware Server2 just won't set intel E1000 as default emulated device.

 

add the following line to your vmx file, and everything goes well.

 

ethernet0.virtualDev = "e1000"

Share this post


Link to post
Share on other sites

I have an odd error that I suspect is related to the video (or maybe the video card in the laptop the image is running on). Everything seems to work fine except for iWork. In Pages, I can't see any text that I type (it acts like I'm typing white font on a white background). If I do a Print Preview and look at it in Preview, I can see everything just fine. Also, if I click on "Outline" I can see the text display for about 1 second and then it goes away. All other non-iWork apps display text just fine too. I've got Leopard 10.5.7 running on Workstation 6.5 and Windows Vista at the host. Hardware config is:

 

Dell Precision M6300

Core 2 Duo T7700 @ 2.4 GHz

4 GB Memory

NVIDIA Quadro FX 1600M video

 

Anyone else experienced this or have any ideas? Other than this one problem everything works great and it lets me run some of my Mac apps while I'm away at the office.

Share this post


Link to post
Share on other sites

Ezhiki, I am using Fusion on a Hackintosh, so we will see if I can make it work with a bit more twiddling. If I delete the extensions folder, I can get the disc to boot to the installer, but have no mouse support (probably lacks a hell of a lot else as well, but it tells us something)

Share this post


Link to post
Share on other sites
Found the answer by myself.

 

I think VMware Server2 just won't set intel E1000 as default emulated device.

 

add the following line to your vmx file, and everything goes well.

 

ethernet0.virtualDev = "e1000"

 

Actually just tried with Server 2 on Windows and it does set the correct settings if you create as FreeBSD-64 first.

 

I have an odd error that I suspect is related to the video (or maybe the video card in the laptop the image is running on). Everything seems to work fine except for iWork. In Pages, I can't see any text that I type (it acts like I'm typing white font on a white background). If I do a Print Preview and look at it in Preview, I can see everything just fine. Also, if I click on "Outline" I can see the text display for about 1 second and then it goes away. All other non-iWork apps display text just fine too. I've got Leopard 10.5.7 running on Workstation 6.5 and Windows Vista at the host. Hardware config is:

 

Dell Precision M6300

Core 2 Duo T7700 @ 2.4 GHz

4 GB Memory

NVIDIA Quadro FX 1600M video

 

Anyone else experienced this or have any ideas? Other than this one problem everything works great and it lets me run some of my Mac apps while I'm away at the office.

 

Haven't tried as use Office 2008. I am not surprised that there may be glitches though.

Share this post


Link to post
Share on other sites
Actually just tried with Server 2 on Windows and it does set the correct settings if you create as FreeBSD-64 first.

 

My guest is created as FreeBSD 32bit, maybe this is the key?

Also, I found the VMware tools won't work in my guest. Do you know how to slove this?

All I need is the VMware SVGA driver, otherwise the console will be freeze after hours.

Share this post


Link to post
Share on other sites
My guest is created as FreeBSD 32bit, maybe this is the key?

Also, I found the VMware tools won't work in my guest. Do you know how to slove this?

All I need is the VMware SVGA driver, otherwise the console will be freeze after hours.

 

That will be the answer then. Please read the manual as I have covered the tools in it. The driver does not work currently although there is a 3rd party hacked version available. I am about to test this and if OK will add it as a supported option.

Share this post


Link to post
Share on other sites
Sorry I have no other solution. This seems to be a problem with many of the newer processors.

 

UPDATE: Can you take a look at this document and boot from the CD utility and post results here?

 

I boot using the darwin.iso then connected the leopard ISO image. It shows:

Loading Darwin/x86

Invalid front side bus frequency 66000000Hz

Disabling the CPU ...

 

And VMware returns an error stating processor being disabled. Returns the same error even with "busratio=20" flag.

Share this post


Link to post
Share on other sites
I boot using the darwin.iso then connected the leopard ISO image. It shows:

Loading Darwin/x86

Invalid front side bus frequency 66000000Hz

Disabling the CPU ...

 

And VMware returns an error stating processor being disabled. Returns the same error even with "busratio=20" flag.

 

As I said this is a known problem and I don't have a solution. I assume you are using a vanilla retail Leopard DVD image?

Share this post


Link to post
Share on other sites

One problem I am having is that every now and then I will press a key and VMWare will get stuck pressing that key. So whenever I click on a text field it just keeps entering that key. I cant delete them either because as soon as I let go of the delete key it just keeps spamming them.

 

The only solution I have to this is to restart OSX (not the VM) and its sorts it out until it strikes again!

Share this post


Link to post
Share on other sites
One problem I am having is that every now and then I will press a key and VMWare will get stuck pressing that key. So whenever I click on a text field it just keeps entering that key. I cant delete them either because as soon as I let go of the delete key it just keeps spamming them.

 

The only solution I have to this is to restart OSX (not the VM) and its sorts it out until it strikes again!

 

In the manual!!! Revert to PS2 Controller.

 

 

So after months of testing here is a new version of the package to run retail Mac OS X in VMware. This release supports the following products:
  • VMware Workstation 6.5 (Windows & Linux)
  • VMware Player 2.5 (Windows & Linux)
  • VMware Server 2.0 (Windows & Linux)
  • VMware Fusion 2.0 (Mac OS X)
  • VMware ESX 4.0
  • VMware ESXi 4.0

It is compatible with the other methods that have been previously described in the forums. I have attached the manual to the post and the package is available at http://www.mediafire.com/?sharekey=2528947...04e75f6e8ebb871.

 

A plea to everyone to please read the manual as I am getting several questions that are answered in the PDF; e.g. screen resolution and keys repeating. I know there are a couple of issues not mentioned:

 

1. vCenter won't power on the guest only via connecting directly to ESX host can you do this.

2. Nehalem/Core i7 and Quad Core processors are having issues. Currently still researching the problem

 

Please remember to give me the information I requested previously in the thread and that I do not use distros only original software from Apple. Also remember that DVDs that come with a machine are likely to be locked to that machine and probably won't work.

Share this post


Link to post
Share on other sites
I boot using the darwin.iso then connected the leopard ISO image. It shows:

Loading Darwin/x86

Invalid front side bus frequency 66000000Hz

Disabling the CPU ...

 

And VMware returns an error stating processor being disabled. Returns the same error even with "busratio=20" flag.

 

 

Make sure the guestos is set to 'darwin' or 'darwin64' in your vmx file.

Share this post


Link to post
Share on other sites

Followed the instructions and got 10.5.6 retail on a i7 running nicely. Pretty amazing.

 

Updating to 10.5.7, unfortunately, is causing problems booting after the update. I assume this is related to previous posts about vmware issues with i7 processors.

 

Jul 25 19:02:27.466: vcpu-0| [msg.log.monpanic] *** VMware Workstation internal monitor error ***
Jul 25 19:02:27.466: vcpu-0| vcpu-0:ASSERT vmcore/vmm/cpu/segment.c:540 bugNr=19580
Jul 25 19:02:27.466: vcpu-0| [msg.log.monpanic.beta.report] There is a problem in this version of VMware Workstation.
Jul 25 19:02:27.466: vcpu-0| We rely on your feedback to improve the quality of our product. Please submit a support request that describes the problem at our Web page "http://vmware.com/info?id=8". Do not forget to attach the log file (C:\Work\Virtual Machines\My Mac\vmware.log) and the core file(s) (C:\Work\Virtual Machines\My Mac\vmware-core[0-1].gz, C:\Work\Virtual Machines\My Mac\vmware64-core[0-1].gz, C:\Work\Virtual Machines\My Mac\vmware-vmx-debug-4456.dmp).
Jul 25 19:02:27.467: vcpu-0| [msg.log.monpanic.vmSupport.windowsOrLinux] To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.
Jul 25 19:02:27.467: vcpu-0| [msg.log.monpanic.finish] We appreciate your feedback,
Jul 25 19:02:27.467: vcpu-0|   -- the VMware Workstation team.

 

...or I didn't do something right - which is quite possible.

 

 

Great manual and great achievement though. Congrats.

 

-SM-

 

 

 

Vista x64, vmware workstation 6.5.2, leopard retail 10.5.6

 

guestOS = "darwin-64"
ich7m.present = "TRUE"
smc.present = "FALSE"
keyboard.vusb.enable = "FALSE"
mouse.vusb.enable = "FALSE"
monitor.virtual_exec="hardware"
monitor.virtual_mmu="software"
monitor = "debug"
...

Share this post


Link to post
Share on other sites

Can you do 2 things:

 

1. Edit vmx file and remove:

 

monitor = "debug"

 

2. When boot use -v -f -x flags for the first boot

Share this post


Link to post
Share on other sites

Yes, I read that as well just after I had posted my message here. Unfortunately, I just now tried it again and booted using the three switches you mentioned but the result is the same. It still dies.

 

It appears to die right after it resizes the window to match my target resolution ("Graphics Mode"). Below is again the debug log from a second attempt with debugging enabled.

 

Jul 25 20:44:28.991: mks| SVGA: display status changed, using optimizations for local consoles.
Jul 25 20:44:32.549: mks| MKSHostOps_Exit3D: 0, 1
Jul 25 20:44:46.871: mks| MKS ungrab warp to (992, 454)
Jul 25 20:45:10.131: mks| MKS enabling SVGA
Jul 25 20:45:10.256: vcpu-0| Monitor64_PowerOn()
Jul 25 20:45:10.303: vcpu-0| vmm64-modules: [vmm.vmm64 .data:0xfffffffffc04b000-0xd00 .sdata:0xfffffffffc04c000-0x9b8 .statvars:0xfffffffffc04d000-0x1e4 .peer:0xfffffffffc04e000-0x26a80 .shared:0xfffffffffc077000-0x17540 .bss:0xfffffffffc08f000-0x109c8 .rodata:0xfffffffffc200000-0x15c80 .text:0xfffffffffc21c000-0xa539c .kstatvars:0x3000-0x0 .eh_frame:0xfffffffffc2f8000-0x16590, mmu-hv.vmm64 .rodata:0xfffffffffc215c80-0x575 .data:0xfffffffffc04bd00-0x20 .peer:0xfffffffffc074a80-0x1700 .shared:0xfffffffffc08e540-0x2c0 .bss:0xfffffffffc09f9e0-0xa15 .text:0xfffffffffc2c13a0-0x19983 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .scb:0x3b40-0x180 .shared_meta:0x4020-0x3c0 .peer_meta:0x1230-0x240 .eh_frame:0xfffffffffc30e590-0x2740 .comment:0xd4a-0x10e, sharedmmu-none.vmm64 .text:0xfffffffffc2dad24-0x1e .eh_frame:0xfffffffffc310cd0-0x138 .comment:0xe58-0x12, pv-none.vmm64 .shared:0xfffffffffc08e800-0x180 .bss:0x1000-0x0 .text:0xfffffffffc2dad44-0x4 .shared_meta:0x43e0-0x90 .eh_frame:0xfffffffffc310e08-0x48 .comment:0xe6a-0x48, vprobe-none.vmm64 .text:0xfffffffffc2dad48-0x6a .eh_frame:0xfffffffffc310e50-0x2d0 .comment:0xeb2-0x12, hv-vt.vmm64 .rodata:0xfffffffffc216200-0x319c .data:0xfffffffffc04bd20-0x20 .peer:0x5000-0x0 .shared:0x5000-0x0 .bss:0xfffffffffc0a0400-0x9d80 .text:0xfffffffffc2dadc0-0x1842a .statvars:0x5000-0x0 .kstatvars:0x5000-0x0 .eh_frame:0xfffffffffc311120-0x2208 .comment:0xec4-0x36, gphys-sw.vmm64 .rodata:0xfffffffffc2193a0-0x5a3 .data:0xfffffffffc04bd40-0x4 .peer:0xfffffffffc076180-0x40 .shared:0xfffffffffc08e980-0x140 .bss:0xfffffffffc0aa180-0x22 .text:0xfffffffffc2f31f0-0x4428 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .scb:0x3cc0-0x60 .shared_meta:0x4470-0x2a0 .peer_meta:0x1470-0x60 .eh_frame:0xfffffffffc313328-0x818 .comment:0xefa-0x12, vassert-none.vmm64 .text:0xfffffffffc2f7618-0xf .eh_frame:0xfffffffffc313b40-0x78 .comment:0xf0c-0x12, vmsafe-none.vmm64 .text:0xfffffffffc2f7628-0x6 .eh_frame:0xfffffffffc313bb8-0x78 .comment:0xf1e-0x12,  .rodata:0xfffffffffc219943-0x1d49| 0x57000]
Jul 25 20:45:10.303: vcpu-0| APIC: version = 0x15, max LVT = 6
Jul 25 20:45:10.303: vcpu-0| APIC: LDR = 0x80000000, DFR = 0xffffffff
Jul 25 20:45:10.303: vcpu-0| VMX Basic (0x00da04000000000e)
Jul 25 20:45:10.303: vcpu-0|   VMCS revision ID:                 14
Jul 25 20:45:10.303: vcpu-0|   VMCS Region Length:             1024 bytes
Jul 25 20:45:10.303: vcpu-0|   VMX Physical-Address Width:    natural
Jul 25 20:45:10.303: vcpu-0|   SMI Parallel Monitor:            yes
Jul 25 20:45:10.303: vcpu-0|   Advanced INS/OUTS info:          yes
Jul 25 20:45:10.303: vcpu-0|   True VMX MSRs:                   yes
Jul 25 20:45:10.303: vcpu-0|   VMCS Memory Type:                 WB
Jul 25 20:45:10.303: vcpu-0| Pin-Based VM-Execution Controls (0x0000007f00000016)
Jul 25 20:45:10.303: vcpu-0| Processor-Based VM-Execution Controls (0xfff9fffe04006172)
Jul 25 20:45:10.303: vcpu-0| Secondary VM-Execution Controls (0x0000007f00000000)
Jul 25 20:45:10.303: vcpu-0| VM-Exit Controls (0x007fffff00036dfb)
Jul 25 20:45:10.303: vcpu-0| VM-Entry Controls (0x0000ffff000011fb)
Jul 25 20:45:10.303: vcpu-0| EPT and VPID Capabilities (0x00000f0106114141)
Jul 25 20:45:10.303: vcpu-0| VMX Misc (0x00000000000401c5)
Jul 25 20:45:10.303: vcpu-0|   TSC:Preemption Timer Ratio:       32
Jul 25 20:45:10.303: vcpu-0|   Activity State HLT:                1
Jul 25 20:45:10.303: vcpu-0|   Activity State Shutdown:           1
Jul 25 20:45:10.303: vcpu-0|   Activity State Wait-for-SIPI:      1
Jul 25 20:45:10.303: vcpu-0|   CR3 Targets Supported:             4
Jul 25 20:45:10.303: vcpu-0|   Maximum MSR List Size:           512
Jul 25 20:45:10.303: vcpu-0|   MSEG Revision ID:                  0
Jul 25 20:45:10.303: vcpu-0| CR0 Controls (0x0000000080000021/0x00000000ffffffff)
Jul 25 20:45:10.303: vcpu-0|   Fixed to 0:       0xffffffff00000000
Jul 25 20:45:10.303: vcpu-0|   Fixed to 1:       0x0000000080000021
Jul 25 20:45:10.303: vcpu-0|   Variable:         0x000000007fffffde
Jul 25 20:45:10.303: vcpu-0| CR4 Controls (0x0000000000002000/0x00000000000027ff)
Jul 25 20:45:10.303: vcpu-0|   Fixed to 0:       0xffffffffffffd800
Jul 25 20:45:10.303: vcpu-0|   Fixed to 1:       0x0000000000002000
Jul 25 20:45:10.303: vcpu-0|   Variable:         0x00000000000007ff
Jul 25 20:45:10.303: vcpu-0| VMCS Enumeration (0x000000000000002a)
Jul 25 20:45:10.303: vcpu-0|   Highest Index:                  0x15
Jul 25 20:45:10.303: vcpu-0|   Encoding Bits:            0x00006c00
Jul 25 20:45:10.303: vcpu-0| BUSMEM: Initialization (boot-vcpu=1 vmm32=0)
Jul 25 20:45:10.303: vcpu-0| BUSMEM: Beginning additional initialization
Jul 25 20:45:10.303: vcpu-0| BUSMEM: Allocating frames for slot 0
Jul 25 20:45:10.303: vcpu-0| BUSMEM: Allocating frames for slot 1
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 2
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 3
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 4
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 5
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 6
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 7
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 8
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 9
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 10
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 11
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 12
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 13
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 14
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 15
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Allocating frames for slot 16
Jul 25 20:45:10.381: vcpu-0| BUSMEM: Done with additional initialization
Jul 25 20:45:10.381: vcpu-0| BranchTracingInit (before): debugCtlLow: 0x1 debugCtlHigh: 0x0
Jul 25 20:45:10.381: vcpu-0| BranchTracingInit (after) : debugCtlLow: 0x1 debugCtlHigh: 0x0
Jul 25 20:45:10.381: vcpu-0| Init modules.
Jul 25 20:45:10.381: vcpu-0| HV enabled
Jul 25 20:45:10.396: vcpu-0| VMM64 initialized
Jul 25 20:45:10.396: vcpu-1| APIC: version = 0x15, max LVT = 6
Jul 25 20:45:10.396: vcpu-1| APIC: LDR = 0x40000000, DFR = 0xffffffff
Jul 25 20:45:10.396: vcpu-1| VMX Basic (0x00da04000000000e)
Jul 25 20:45:10.396: vcpu-1|   VMCS revision ID:                 14
Jul 25 20:45:10.396: vcpu-1|   VMCS Region Length:             1024 bytes
Jul 25 20:45:10.396: vcpu-1|   VMX Physical-Address Width:    natural
Jul 25 20:45:10.396: vcpu-1|   SMI Parallel Monitor:            yes
Jul 25 20:45:10.396: vcpu-1|   Advanced INS/OUTS info:          yes
Jul 25 20:45:10.396: vcpu-1|   True VMX MSRs:                   yes
Jul 25 20:45:10.396: vcpu-1|   VMCS Memory Type:                 WB
Jul 25 20:45:10.396: vcpu-1| Pin-Based VM-Execution Controls (0x0000007f00000016)
Jul 25 20:45:10.396: vcpu-1| Processor-Based VM-Execution Controls (0xfff9fffe04006172)
Jul 25 20:45:10.396: vcpu-1| Secondary VM-Execution Controls (0x0000007f00000000)
Jul 25 20:45:10.396: vcpu-1| VM-Exit Controls (0x007fffff00036dfb)
Jul 25 20:45:10.396: vcpu-1| VM-Entry Controls (0x0000ffff000011fb)
Jul 25 20:45:10.396: vcpu-1| EPT and VPID Capabilities (0x00000f0106114141)
Jul 25 20:45:10.396: vcpu-1| VMX Misc (0x00000000000401c5)
Jul 25 20:45:10.396: vcpu-1|   TSC:Preemption Timer Ratio:       32
Jul 25 20:45:10.396: vcpu-1|   Activity State HLT:                1
Jul 25 20:45:10.396: vcpu-1|   Activity State Shutdown:           1
Jul 25 20:45:10.396: vcpu-1|   Activity State Wait-for-SIPI:      1
Jul 25 20:45:10.396: vcpu-1|   CR3 Targets Supported:             4
Jul 25 20:45:10.396: vcpu-1|   Maximum MSR List Size:           512
Jul 25 20:45:10.396: vcpu-1|   MSEG Revision ID:                  0
Jul 25 20:45:10.396: vcpu-1| CR0 Controls (0x0000000080000021/0x00000000ffffffff)
Jul 25 20:45:10.396: vcpu-1|   Fixed to 0:       0xffffffff00000000
Jul 25 20:45:10.396: vcpu-1|   Fixed to 1:       0x0000000080000021
Jul 25 20:45:10.396: vcpu-1|   Variable:         0x000000007fffffde
Jul 25 20:45:10.396: vcpu-1| CR4 Controls (0x0000000000002000/0x00000000000027ff)
Jul 25 20:45:10.396: vcpu-1|   Fixed to 0:       0xffffffffffffd800
Jul 25 20:45:10.396: vcpu-1|   Fixed to 1:       0x0000000000002000
Jul 25 20:45:10.396: vcpu-1|   Variable:         0x00000000000007ff
Jul 25 20:45:10.396: vcpu-1| VMCS Enumeration (0x000000000000002a)
Jul 25 20:45:10.396: vcpu-1|   Highest Index:                  0x15
Jul 25 20:45:10.396: vcpu-1|   Encoding Bits:            0x00006c00
Jul 25 20:45:10.396: vcpu-1| BUSMEM: Initialization (boot-vcpu=0 vmm32=0)
Jul 25 20:45:10.396: vcpu-1| BUSMEM: Beginning additional initialization
Jul 25 20:45:10.396: vcpu-1| BUSMEM: Allocating frames for slot 0
Jul 25 20:45:10.396: vcpu-1| BUSMEM: Allocating frames for slot 1
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 2
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 3
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 4
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 5
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 6
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 7
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 8
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 9
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 10
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 11
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 12
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 13
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 14
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 15
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Allocating frames for slot 16
Jul 25 20:45:10.474: vcpu-1| BUSMEM: Done with additional initialization
Jul 25 20:45:10.474: vcpu-1| BranchTracingInit (before): debugCtlLow: 0x1 debugCtlHigh: 0x0
Jul 25 20:45:10.474: vcpu-1| BranchTracingInit (after) : debugCtlLow: 0x1 debugCtlHigh: 0x0
Jul 25 20:45:10.474: vcpu-1| Init modules.
Jul 25 20:45:10.474: vcpu-1| HV enabled
Jul 25 20:45:10.490: vcpu-1| VMM64 initialized
Jul 25 20:45:10.521: vcpu-0| MonitorInitNumaUnmapVMM64
Jul 25 20:45:10.552: vcpu-0| VMM64: TestPeerAndVMKCalls
Jul 25 20:45:10.568: vcpu-0| VMM64: peer call: 30255 cycles
Jul 25 20:45:10.568: vcpu-0| VMM64: TestPeerAndVMKCalls - nested peer calls
Jul 25 20:45:10.599: vcpu-0| RDMSR: unknown MSR[0x35] (read as zero): rip=0x19a439 count=1
Jul 25 20:45:10.599: vcpu-0| RDMSR: unknown MSR[0x179] (read as zero): rip=0x1a4e9b count=1
Jul 25 20:45:10.615: vcpu-0| GPhysGuestPgWalk4Work: paRsvd=fff0000000000
Jul 25 20:45:10.615: vcpu-0| RDMSR: unknown MSR[0x194] (read as zero): rip=0x1ac6fb count=1
Jul 25 20:45:10.615: vcpu-0| RDMSR: unknown MSR[0xce] (read as zero): rip=0x1ac703 count=1
Jul 25 20:45:10.615: vcpu-0| NOT_TESTED vmcore/vmm64/cpu/segment.c:401
Jul 25 20:45:10.615: vcpu-0| NOT_TESTED vmcore/vmm64/cpu/segment.c:630
Jul 25 20:45:10.615: vcpu-0| NOT_TESTED vmcore/vmm64/cpu/segment.c:401
Jul 25 20:45:10.615: vcpu-0| NOT_TESTED vmcore/vmm64/cpu/segment.c:630
Jul 25 20:45:10.615: vcpu-0| Triple fault.
Jul 25 20:45:10.615: vcpu-0| MONITOR PANIC: vcpu-0:ASSERT vmcore/vmm/cpu/segment.c:540 bugNr=19580
Jul 25 20:45:10.615: vcpu-0| Core dump with build build-156735
Jul 25 20:45:10.646: vcpu-0| Writing monitor corefile "C:\Work\Virtual Machines\My Mac\vmware-core0.gz"

 

...VMware snapshots are great :-)

 

 

Can you do 2 things:

 

1. Edit vmx file and remove:

 

monitor = "debug"

 

2. When boot use -v -f -x flags for the first boot

Share this post


Link to post
Share on other sites

Did you take the monitor statement out of the VMX file, as that log file is definitely from a debug VMX monitor? What happens is that a triple fault on a debug version of the monitor always stops the VM. If the release version is used it will quite often work.

Share this post


Link to post
Share on other sites

I tried first, like you suggested, without monitor=debug and with -x -f -v. Then, to get some debug info that might help you, I added monitor=debug back again and produced that log file. Yes, I did try without the monitor statement. After screen resize, the error dialog about a failure pops up and the virtual machine is rebooted.

 

Update: Tried various Execution Mode settings with either one or two processors configured. No improvement.

 

Did you take the monitor statement out of the VMX file, as that log file is definitely from a debug VMX monitor? What happens is that a triple fault on a debug version of the monitor always stops the VM. If the release version is used it will quite often work.

 

It's shocking how nicely 10.5.6 runs - even though I also *fail* at getting audio working. It just won't recognize any sound device even if I load that AC97 kext. But otherwise it's really running nice and smoothly. Quite amazing.

Share this post


Link to post
Share on other sites

hi, i'm stuck with this error (vmware workstation 6.5)

http://img190.imageshack.us/img190/7283/errorofx.jpg

 

i already tried guestOS = "darwin-64" and guestOS = "darwin"

 

also tried:

1)

ich7m.present = "TRUE"

smc.present = "FALSE"

keyboard.vusb.enable = "FALSE"

mouse.vusb.enable = "FALSE"

 

2)ich7m.present = "TRUE"

smc.present = "FALSE"

keyboard.vusb.enable = "TRUE"

mouse.vusb.enable = "TRUE"

 

what's wrong? i'm using kalyway 10.5.1 and if i try the 10.5.6 from xXx i get a stack + reboot

 

i have a Q6600 + P5K-SE

thank you

Share this post


Link to post
Share on other sites

You need to use vanilla Leopard (I see ToH in that pic). I had nearly the same error trying 10.4.11v2 XXX, though originally I thought that was because of using 10.4.

Share this post


Link to post
Share on other sites

For those running Core i7 and Core2 Quad processors, I want to try an experiment with a kernel inserted into the darwin.iso image. The installation will be a little more involved as will need to use the boot options command line to ensure correct booting of the DVD for installation. The question is which one:

 

10.5.6 Retail

10.5.6 Retail fixed for Core i7 (in the new Releases forum)

10.5.7 Retail

Voodoo 2 alpha 3

 

Any thoughts? What have you had success with? Do you want all 3 and give me feedback? Remember I do not have access to a system with these processors.

Share this post


Link to post
Share on other sites

10.5.6 Retail works very well for me on my i7 quad:

Intel® Core i7 CPU 920 @ 2.67GHz

 

I'd be mostly interested in getting 10.5.7 Retail up and running - which currently isn't.

 

-SM-

 

 

For those running Core i7 and Core2 Quad processors, I want to try an experiment with a kernel inserted into the darwin.iso image. The installation will be a little more involved as will need to use the boot options command line to ensure correct booting of the DVD for installation. The question is which one:

 

10.5.6 Retail

10.5.6 Retail fixed for Core i7 (in the new Releases forum)

10.5.7 Retail

Voodoo 2 alpha 3

 

Any thoughts? What have you had success with? Do you want all 3 and give me feedback? Remember I do not have access to a system with these processors.

Share this post


Link to post
Share on other sites
10.5.6 Retail works very well for me on my i7 quad:

Intel® Core™ i7 CPU 920 @ 2.67GHz

 

I'd be mostly interested in getting 10.5.7 Retail up and running - which currently isn't.

 

-SM-

 

So what the plan would be would be to use the 10.5.6 kernel from the darwin.iso, but the rest of the system would be 10.5.7. The other possibility is that if it is bus ratio related to try and build something around Chameleon 2.

Share this post


Link to post
Share on other sites

does the 10.5.7 retail is the same then updating from the 10.5.6 or its like the windows builds?

 

if is just a update, then its better to use the 10.5.6 retail for compatibility, and btw i just cant find a working 10.5.7 retail so i'm downloading the .6 one

Share this post


Link to post
Share on other sites

System Preferences seems to hang a lot for me. It is not always the same page and not always the same time. Nothing else seems to have problems.

Screensaver is set to never.

Harddrives, monitor, and computer are all set to never suspend.

Anyone else see this?

Apologies if this is a repeat.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×