Jump to content

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

Donk

By Donk,
in Multi-booting and Virtualisation

 Share
2,213 posts in this topic

Recommended Posts

Donk
Donk
Posted
  • Author
Posted
Nick, It may be because your T2400 CPU does not support 64-bit at the CPU level, so you may need to run with guestOS = "darwin10" rather than "darwin10-64", whereas your Q6600 will support 64-bit at the CPU level, so will run the guestOS in 64-bit mode.

 

Give it a try!

 

Can you post the output of Securable from www.grc.com?

Link to comment
Share on other sites
its
its
Posted
Posted
You can't run SL on Workstation 6.5 this way you need Workstation 7 or Player 3. look for the Zenith432 Snow Kitty topic for one possible solution.

 

I tried a leopard.iso as well and get the same error.. the vmware.log is like

 

......

Feb 10 10:58:11.981: vmx| VMXVmdbLoadUsbDevices: New set of 1 USB devices

Feb 10 10:58:11.981: vmx| USB: Found device [name:Logitech\ USB\ Composite\ Device vid:046d pid:0a0c path:1/6/1 speed:full family:audio,hid autoclean:1]

Feb 10 10:58:12.355: vcpu-0| BIOS-UUID is 56 4d 1d 7d ae 5a b8 81-4d bb 0d 52 0d 8b 4c be

Feb 10 10:58:12.554: vcpu-0| TOOLS INSTALL entering BEGINNING state.

Feb 10 10:58:12.554: vcpu-0| TOOLS INSTALL Scanning device ide0:0 ((null)).

Feb 10 10:58:12.554: vcpu-0| TOOLS INSTALL Scanning device ide0:1 ((null)).

Feb 10 10:58:12.554: vcpu-0| TOOLS INSTALL Scanning device ide1:0 (D:\ISO\leopard.iso).

Feb 10 10:58:12.554: vcpu-0| TOOLS INSTALL Scanning device ide1:1 ((null)).

Feb 10 10:58:12.554: vcpu-0| TOOLS INSTALL Attempting image mount.

Feb 10 10:58:12.554: vcpu-0| TOOLS INSTALL using device 'ide1:0'.

Feb 10 10:58:12.700: vcpu-0| CDROM: Disconnected cdrom: ide1:0

Feb 10 10:58:12.723: vcpu-0| TOOLS INSTALL entering INSERTED state.

Feb 10 10:58:12.724: vcpu-0| CDROM: Connecting ide1:0 to 'C:\Program Files (x86)\VMware\VMware Workstation\darwin.iso'. img=1 raw=0 remote=0

Feb 10 10:58:12.724: vcpu-0| CDROM: Reset guest state on ide1:0. Invalidating last disconnect time.

Feb 10 10:58:12.732: vcpu-0| TOOLS INSTALL attempted to begin tools install while tools image was not in the correct state (idle). Ignoring...

Feb 10 10:58:12.740: vcpu-0| TOOLS INSTALL attempted to begin tools install while tools image was not in the correct state (idle). Ignoring...

Feb 10 10:58:12.752: mks| Ignoring update request in VGA_Expose (mode change pending).

Feb 10 10:58:13.041: vcpu-0| CDROM: switching CDROM state from 5 to 1 using error sense key.

Feb 10 10:58:13.041: vcpu-0| CDROM ide1:0: CMD 0x43 (READ TOC) FAILED (key 0x6 asc 0x28 ascq 0)

Feb 10 10:58:13.744: vmx| CDROM: Guest eject on ide1:0. Cancelling tools install.

Feb 10 10:58:13.745: vmx| TOOLS INSTALL cancelling tools installation.

Feb 10 10:58:13.745: vmx| CDROM: Disconnected cdrom: ide1:0

Feb 10 10:58:13.745: vmx| TOOLS INSTALL entering ENDING state.

Feb 10 10:58:13.765: vmx| CDROM: Connecting ide1:0 to 'D:\ISO\leopard.iso'. img=1 raw=0 remote=0

Feb 10 10:58:13.765: vmx| TOOLS INSTALL entering IDLE state.

Feb 10 10:58:13.766: vcpu-0| CDROM: switching CDROM state from 2 to 3 using error sense key.

Feb 10 10:58:13.766: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x2

Feb 10 10:58:13.766: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.766: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.766: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.766: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.766: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.767: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.767: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.767: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.767: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.767: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.767: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.767: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.768: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.768: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.768: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.768: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.768: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.768: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.768: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.768: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.769: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.769: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.769: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.769: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.769: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.769: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.769: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.769: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.770: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.770: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.770: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.770: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.770: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.770: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.770: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.771: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.771: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.771: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.771: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.771: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.771: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.771: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.772: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.772: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.772: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.772: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.772: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.772: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.772: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.772: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.773: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.773: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.773: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.773: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.773: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.773: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.773: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.773: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.775: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.775: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.775: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.775: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.776: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.776: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.776: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.776: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.776: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.776: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.777: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.777: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.777: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.777: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.777: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.778: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.778: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.778: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.778: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.778: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.778: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.779: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.779: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.779: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.779: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.779: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.780: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.780: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.780: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.780: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.781: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.782: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.782: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.782: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.782: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.782: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.783: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.783: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.783: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.783: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.783: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.784: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.784: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.784: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.784: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.784: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.785: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.785: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.785: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.785: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.785: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.786: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.786: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.786: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.786: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.786: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.787: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.787: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.787: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.787: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:13.788: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.758: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.758: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.758: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.758: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.758: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.759: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.759: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.759: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.759: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.759: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.759: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.759: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.759: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.760: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.760: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.760: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.760: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.760: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.760: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.760: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.761: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.761: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.761: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.761: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.761: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.761: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.761: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.761: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.762: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.762: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.762: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.762: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.762: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.762: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.762: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.762: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.763: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.763: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.763: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.763: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.763: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.763: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.763: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.763: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.763: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.764: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.764: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.764: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.764: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.764: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.764: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.764: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.764: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.765: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.765: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.765: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.765: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.765: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.765: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:14.765: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:15.747: vcpu-0| CDROM: switching CDROM state from 3 to 4 using error sense key.

Feb 10 10:58:15.747: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x3a, ascq 0x0

Feb 10 10:58:15.747: vcpu-0| CDROM: switching CDROM state from 4 to 5 using error sense key.

Feb 10 10:58:15.747: vcpu-0| CDROM ide1:0: CMD 0x28 (READ(10)) FAILED (key 0x2 asc 0x4 ascq 0x1)

Feb 10 10:58:15.747: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x2, asc 0x4, ascq 0x1

Feb 10 10:58:15.747: vcpu-0| CDROM: switching CDROM state from 5 to 1 using error sense key.

Feb 10 10:58:15.747: vcpu-0| CDROM ide1:0: CMD 0x28 (READ(10)) FAILED (key 0x6 asc 0x28 ascq 0)

Feb 10 10:58:15.747: vcpu-0| VIDE: ATAPI 0x28 Failed: key 0x6, asc 0x28, ascq 0x0

Feb 10 10:58:16.191: mks| SVGA: display status changed, using optimizations for local consoles.

Feb 10 10:58:20.832: mks| MKSHostOps_Exit3D: 0, 1

Feb 10 10:58:36.703: vmx| VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOff without reset

Feb 10 10:58:36.704: vmx| Stopping VCPU threads...

Feb 10 10:58:36.724: mks| Detaching from window system.

Feb 10 10:58:36.725: mks| MKSHostOps_Exit3D: 1, 0

Feb 10 10:58:36.725: mks| Async MKS thread is exiting

Feb 10 10:58:36.725: vmx| USB: Disconnecting device 0x600000010e0f0006

Feb 10 10:58:36.725: vmx| USB: Disconnecting device 0x400000010e0f0003

Feb 10 10:58:36.725: vmx| USB: Disconnecting device 0x200000010e0f0002

Feb 10 10:58:36.725: vmx| TOOLS received request in VMX to set option 'enableDnD' -> '0'

Feb 10 10:58:36.725: vmx| TOOLS received request in VMX to set option 'copypaste' -> '0'

Feb 10 10:58:36.725: vmx| TOOLS received request in VMX to set option 'copypaste' -> '0'

Feb 10 10:58:36.729: vmx| MKS local poweroff

Feb 10 10:58:36.729: vmx| scsi0:0: numIOs = 2 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)

Feb 10 10:58:36.730: vmx| AIOWIN32C: asyncOps=3 syncOps=0 bufSize=0Kb fixedOps=0 sgOps=3 sgOn=1

Feb 10 10:58:36.730: aioCompletion| AIO thread processed 3 completions

Feb 10 10:58:36.730: vmx| AIOWIN32: asyncOps=0 syncOps=0 bufSize=0Kb delayed=0 fixed=0 sgOp=0 sgOn=1

Feb 10 10:58:36.743: vmx| WORKER: asyncOps=378 maxActiveOps=1 maxPending=0 maxCompleted=0

Feb 10 10:58:36.766: vmx| Transitioned vmx/execState/val to poweredOff

Feb 10 10:58:36.834: vmx| vmdbPipe_Streams: Couldn't read

Feb 10 10:58:36.834: vmx| VMX idle exit

Feb 10 10:58:36.834: vmx| Flushing VMX VMDB connections

Feb 10 10:58:36.834: vmx| IPC_exit: disconnecting all threads

Feb 10 10:58:36.834: vmx| VMX exit (0).

 

is it corrupt ISO?? i made it to DMG on a mac from a retail disk and converted to iso via hdutil??

Link to comment
Share on other sites
nick8462
nick8462
Posted
Posted
Nick, It may be because your T2400 CPU does not support 64-bit at the CPU level, so you may need to run with guestOS = "darwin10" rather than "darwin10-64", whereas your Q6600 will support 64-bit at the CPU level, so will run the guestOS in 64-bit mode.

 

Give it a try!

Thanks but that's not the problem. I have 32-bit win 7 on the Q6600 & 32-bit vmware 7. I made sure the vmx is 32-bit.

 

Can you post the output of Securable from www.grc.com?

Max bit length -- 32 bit

Hardware D.E.P. -- Yes

Hardware Virtualization -- Locked On:

Virtualization Locked On

This processor's advanced hardware support for virtualization has been enabled and "locked on" to prevent virtual machine penetration compromise. This was probably done by your system's BIOS or by whatever desktop virtual machine system you are using, if any. But if neither are the case you may wish to determine what has done this since it could be a sign of an advanced root kit compromise.

Thanks again,

 

Nick

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted
Thanks but that's not the problem. I have 32-bit win 7 on the Q6600 & 32-bit vmware 7. I made sure the vmx is 32-bit.

 

 

Max bit length -- 32 bit

Hardware D.E.P. -- Yes

Hardware Virtualization -- Locked On:

Virtualization Locked On

This processor's advanced hardware support for virtualization has been enabled and "locked on" to prevent virtual machine penetration compromise. This was probably done by your system's BIOS or by whatever desktop virtual machine system you are using, if any. But if neither are the case you may wish to determine what has done this since it could be a sign of an advanced root kit compromise.

Thanks again,

 

Nick

 

Nick

 

You have one of those rare processors which are 32-bit only and VT-x enabled. Ensure that the guestos setting in the VMX file is darwin for Leopard or darwin10 for Snow Leopard.

 

Dave

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted
Nick

 

You have one of those rare processors which are 32-bit only and VT-x enabled. Ensure that the guestos setting in the VMX file is darwin for Leopard or darwin10 for Snow Leopard.

 

Dave

Dave, FYI, I asked Nick to check he was using guestOS = "darwin10" see post:

 

http://www.insanelymac.com/forum/index.php...t&p=1407264

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted
Dave, FYI, I asked Nick to check he was using guestOS = "darwin10" see post:

 

http://www.insanelymac.com/forum/index.php...t&p=1407264

 

Missed that, thanks. Not sure now what to suggest next. I will look at source code to the bootloader and see if it can force 32-bit for everything.

 

One thought, does the VMX file have:

 

paevm = "true"

 

P.S. Have reviewed the document and have some suggestions plus sorting out some additonal screenshots for you.

Link to comment
Share on other sites
nick8462
nick8462
Posted
Posted
Nick

 

You have one of those rare processors which are 32-bit only and VT-x enabled. Ensure that the guestos setting in the VMX file is darwin for Leopard or darwin10 for Snow Leopard.

 

Dave

 

Dave, a friend of mine originally created the vmx and I've just been porting it around (successfully until now). Let me post it, maybe you can spot why it still gives me the error.

 

Also, can it be due to the fact that I installed Vmware before I reflashed (to update) the bios and enable VT-x?

 

Here it is:

.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "7"
numvcpus = "2"
cpuid.coresPerSocket = "2"
maxvcpus = "4"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "1536"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "Mac OS X Server Snow Leopard-000002.vmdk"
ide1:0.present = "TRUE"
ide1:0.autodetect = "TRUE"
ide1:0.deviceType = "cdrom-image"
floppy0.startConnected = "FALSE"
floppy0.fileName = ""
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.addressType = "generated"
usb.present = "TRUE"
ehci.present = "TRUE"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
roamingVM.exitBehavior = "go"
displayName = "Mac OS X Server Snow Leopard"
guestOS = "darwin10"
nvram = "Mac OS X Server Snow Leopard.nvram"
virtualHW.productCompatibility = "hosted"
extendedConfigFile = "Mac OS X Server Snow Leopard.vmxf"
monitor.virtual_exec = "hardware"
monitor.virtual_mmu = "software"
ich7m.present = "TRUE"
ide1:0.fileName = "darwin.iso"
ethernet0.generatedAddress = "00:0c:29:6a:9e:80"
uuid.location = "56 4d 9c 25 c0 ac 81 fb-78 45 af 24 6c ba 31 71"
uuid.bios = "56 4d 08 08 12 06 af 43-24 4d be 72 32 6a 9e 80"
cleanShutdown = "TRUE"
replay.supported = "FALSE"
replay.filename = ""
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "33"
sound.pciSlotNumber = "34"
ehci.pciSlotNumber = "35"
vmci0.pciSlotNumber = "36"
vmotion.checkpointFBSize = "16777216"
usb:0.present = "TRUE"
usb:1.present = "TRUE"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "845848192"
usb:1.deviceType = "hub"
usb:0.deviceType = "mouse"
keyboard.vusb.enable = "TRUE" 
mouse.vusb.enable = "TRUE"
ide1:0.startConnected = "TRUE"
tools.syncTime = "FALSE"
isolation.tools.hgfs.disable = "TRUE"
sharedFolder.maxNum = "1"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.writeAccess = "TRUE"
sharedFolder0.hostPath = "C:\Users\Public"
sharedFolder0.guestName = "Public"
sharedFolder0.expiration = "never"
smc.present = "FALSE"

 

 

Cheers,

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted
Dave, a friend of mine originally created the vmx and I've just been porting it around (successfully until now). Let me post it, maybe you can spot why it still gives me the error.

 

Also, can it be due to the fact that I installed Vmware before I reflashed (to update) the bios and enable VT-x?

 

 

Cheers,

 

Firstly edit the VMX to have:

guestOS = "darwin10"

 

Next we can check out if it is the cores and CPUs? VMX edit 2:

cpuid.coresPerSocket = "1"

numvcpus = 1

 

Then if that does not work try adding VMX edit 3:

paevm = "TRUE"

 

(Make sure guest is powered down and VMware not running before editing or you will loose changes)

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted
Firstly edit the VMX to have:

guestOS = "darwin10"

 

Next we can check out if it is the cores and CPUs? VMX edit 2:

cpuid.coresPerSocket = "1"

numvcpus = 1

 

Then if that does not work try adding VMX edit 3:

paevm = "TRUE"

 

(Make sure guest is powered down and VMware not running before editing or you will loose changes)

Nick, Hopefully Donk's recommendations will resolve your issue, the CPU count and cores would seem a logical step bearing in mind you have come from a Q6600 to T2400. If not, then may need to run a full new install from scratch on the T2400 which will create a new .vmx, it would be interesting to compare the operational Q6600 with the new T2400 version. I have very nearly completed a new manual, which once I have got Donk's sign off, you may like to try, if Donk's suggestions do not solve your current issue.

Link to comment
Share on other sites
nick8462
nick8462
Posted
Posted
Firstly edit the VMX to have:

guestOS = "darwin10"

 

Next we can check out if it is the cores and CPUs? VMX edit 2:

cpuid.coresPerSocket = "1"

numvcpus = 1

 

Then if that does not work try adding VMX edit 3:

paevm = "TRUE"

 

(Make sure guest is powered down and VMware not running before editing or you will loose changes)

 

I had (guestOS = "darwin10") set already (halfway down the previous post) and the other two didn't solve it, unfortunately...

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted
I had (guestOS = "darwin10") set already (halfway down the previous post) and the other two didn't solve it, unfortunately...

 

Nick

 

I may have missed this but are you using the vanilla kernel or Voodoo one which helps with quad cores? If so do you have anything in com.apple.Boot.plist relating to the kernel and bus speeds?

Link to comment
Share on other sites
nick8462
nick8462
Posted
Posted
Nick

 

I may have missed this but are you using the vanilla kernel or Voodoo one which helps with quad cores? If so do you have anything in com.apple.Boot.plist relating to the kernel and bus speeds?

 

It's the vanilla kernel. I simply put in my retail snow install disc and installed it. Either way, it's something to do with VMware in my opinion because it's not even booting to the vmware bios. It fails immediately after I start the machine with a message that says my system doesn't support all of the virtualization features needed or whatever.

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string></string>
</dict>
</plist>

 

It's not really a big deal though. I have a non-vanilla kernel that I used from Zenith's guide to installing it on non-VT-x computers (I have a vaio without it), and it works fine. The only problem is it can't update without getting hacky, which isn't a problem because I'm just using it for iphone coding. The only thing that bothers me is the speed is a bit slow. I've read that VT-x only gives like a 5% improvement in speed, so it could just be that my comp isn't beefy enough handle it.

 

The Q6600 w/ 4gb of ram (vs the T2400 w/ 2gb) eats Snowkitty for breakfast. But then again, it also has VT-x...

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted
It's the vanilla kernel. I simply put in my retail snow install disc and installed it. Either way, it's something to do with VMware in my opinion because it's not even booting to the vmware bios. It fails immediately after I start the machine with a message that says my system doesn't support all of the virtualization features needed or whatever.

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
 <key>Kernel</key>
 <string>mach_kernel</string>
 <key>Kernel Flags</key>
 <string></string>
</dict>
</plist>

 

It's not really a big deal though. I have a non-vanilla kernel that I used from Zenith's guide to installing it on non-VT-x computers (I have a vaio without it), and it works fine. The only problem is it can't update without getting hacky, which isn't a problem because I'm just using it for iphone coding. The only thing that bothers me is the speed is a bit slow. I've read that VT-x only gives like a 5% improvement in speed, so it could just be that my comp isn't beefy enough handle it.

 

The Q6600 w/ 4gb of ram (vs the T2400 w/ 2gb) eats Snowkitty for breakfast. But then again, it also has VT-x...

 

What is the message? I guess that as the code to run Mac OS X inside VMware was really written for Fusion, it may be taking code paths that are not optimal on the plethora of PCs out there. As almost all Intel Macs are 64-bit (exception of some early Mac Minis) VMware may have assumed certain CPU facilities are always available.

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted
Hello,

 

I was wondering if there is an easy fix for being able to get a higher resolution than 1024x768 on the emulated OSX. Host PC has an Nvidia Gforce 6600LE if that's of any importance.

Yes, install the Darwin VMware Tools and you should be able to select a range of resolutions. An enhanced graphics driver is available at Zenith432's site link below, but in order to get scaling you will also need the guestd patch.

 

http://sourceforge.net/projects/vmsvga2/files/

 

In terms of your physical graphics card, this has no bearing on the guestOS, the graphics in a VM are purely virtual, and have no direct hooks in to your physical graphics card.

 

 

 

It's not really a big deal though. I have a non-vanilla kernel that I used from Zenith's guide to installing it on non-VT-x computers (I have a vaio without it), and it works fine. The only problem is it can't update without getting hacky, which isn't a problem because I'm just using it for iphone coding. The only thing that bothers me is the speed is a bit slow. I've read that VT-x only gives like a 5% improvement in speed, so it could just be that my comp isn't beefy enough handle it.

 

The Q6600 w/ 4gb of ram (vs the T2400 w/ 2gb) eats Snowkitty for breakfast. But then again, it also has VT-x...

Nick, The T2400 is hampered by the combination of 32-bit and VT-x not being supported by the vanilla OS X kernel. So you have a system which can only address the CPU in 32-bit mode and no hardware acceleration, compared to the Q6600 which can take advantage of both, as well as being serveral generations newer, more cache, smaller die size, faster, etc. You get the picture, comparing apples and pears!

Link to comment
Share on other sites
dogen
dogen
Posted
Posted

VMware Workstation now has an update from 7 to 7.01. If anyone has applied the update, can you report on how it affected your Snow Leopard and whether any special patches, procedures, or reinstallations were necessary? If it's not an important update or if it causes complications I'm inclined to skip it. I might even switch from Workstation to Player. Is there an advantage either way between those two?

 

Thanks as always for any help or insight.

Link to comment
Share on other sites
nick8462
nick8462
Posted
Posted
What is the message? I guess that as the code to run Mac OS X inside VMware was really written for Fusion, it may be taking code paths that are not optimal on the plethora of PCs out there. As almost all Intel Macs are 64-bit (exception of some early Mac Minis) VMware may have assumed certain CPU facilities are always available.

 

The exact message is: "Mac OS X is not supported with software virtualization. To run Mac OS X you need a host on which VMware Workstation supports hardware virtualization." Underneath is, there is a message that also pops up (message log) that says: "This host does not support all of the hardware virtualization features required by VMware Workstation. Using software virtualization with a software MMU."

 

Also, I forgot to mention, I have VMware 7.0.1-227600.

Link to comment
Share on other sites
jerryyyyy
jerryyyyy
Posted
Posted
VMware Workstation now has an update from 7 to 7.01. If anyone has applied the update, can you report on how it affected your Snow Leopard and whether any special patches, procedures, or reinstallations were necessary? If it's not an important update or if it causes complications I'm inclined to skip it. I might even switch from Workstation to Player. Is there an advantage either way between those two?

 

Thanks as always for any help or insight.

 

No big improvement and you have to rerun the setup etc....

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted
VMware Workstation now has an update from 7 to 7.01. If anyone has applied the update, can you report on how it affected your Snow Leopard and whether any special patches, procedures, or reinstallations were necessary? If it's not an important update or if it causes complications I'm inclined to skip it. I might even switch from Workstation to Player. Is there an advantage either way between those two?

 

Thanks as always for any help or insight.

Dogen, as Jerry says no dramatic improvements that I can see, it has a few bug fixes, and also offers additional guest OS support, but not OS X. So no real drive to upgrade, also it does a complete reinstall so you will have to re-install the darwin.iso.

 

The only thing is Player included with Workstation 7.0.1 is 3.0.1 whereas the standalone download for Player is still at 3.0.0 last time I looked.

 

So in the old technical speak, if it ain't broke don't fix it, so leave well alone. Although speaking as a Geek, I have to have the latest shiny version, i.e. Office 2010 (nothing to do with OS X, just an example), so I am running 7.0.1 and all appears fine.

 

Hope this helps, also thanks to Jerry for his input.

Link to comment
Share on other sites
BigCat400
BigCat400
Posted
Posted

Not sure this has been asked. I am running SL on WS7 just fine. No issues. About this mac reports a "4.30GHz Unknown Processor".. Is this normal? I am just curious about this. My host is running an i7-820QM processor. It'd be nice if OSX could see at least two processors.

Link to comment
Share on other sites
dogen
dogen
Posted
Posted
Hope this helps, also thanks to Jerry for his input.

 

Yep, it does, and thank you both. Right after I saw the alert for the update to 7.0.1 I ran into a glitch in Workstation wherein control-alt-enter isn't resizing the virtual machine window properly. I can live with that. If anything more serious goes wrong, I'll cross my fingers, apply the update, and reinstall Darwin.iso.

 

Mac Son of Knife, I saw your instructions for a reinstall at post 1173. Just to ensure we're on the same page (literally), are you saying we should follow the instructions in section 2.1 of the pdf attached to the first post in the thread? I rarely work in Windows, so can you be more explicit about how to open a command prompt? Also, once I've run the uninstall and then install commands for setup.cmd, would I then skip ahead to section 4 of the pdf?

 

Sorry for the lame questions. I'm asking now because I imagine the answer will apply (fingers again crossed) to future updates as well.

Link to comment
Share on other sites
Nihilator
Nihilator
Posted
Posted

Donk,

 

I am current running VMware Fusion 3.01.

 

What command do I use to "shrink" a Mac OS X 10.6 (Snow Leopard) virtual hard disk? Your "manual.pdf" says to use the "vmware-tools-guestd" executable to shrink a virtual hard disk.

 

The "vmware-tools-guestd" executable is not included with the "vmware-darwin-snowy.zip". The "vmware-tools-guestd" executable only appears in the vmware-darwin-200.zip.

 

BTW:

 

Where is the "vmware-darwin-snowy.zip" attachment? It has disappeared. It used to be posted at the top of this thread.

 

Thanks, Nihilator

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted
Not sure this has been asked. I am running SL on WS7 just fine. No issues. About this mac reports a "4.30GHz Unknown Processor".. Is this normal? I am just curious about this. My host is running an i7-820QM processor. It'd be nice if OSX could see at least two processors.

Yes, this is normal, currently the only way round this is to move away from the vanilla kernel, which I did try, but no real benefit. You can configure multiple cores in the settings, even multiple CPU's but no significant benefit.

 

Yep, it does, and thank you both. Right after I saw the alert for the update to 7.0.1 I ran into a glitch in Workstation wherein control-alt-enter isn't resizing the virtual machine window properly. I can live with that. If anything more serious goes wrong, I'll cross my fingers, apply the update, and reinstall Darwin.iso.

 

Mac Son of Knife, I saw your instructions for a reinstall at post 1173. Just to ensure we're on the same page (literally), are you saying we should follow the instructions in section 2.1 of the pdf attached to the first post in the thread? I rarely work in Windows, so can you be more explicit about how to open a command prompt? Also, once I've run the uninstall and then install commands for setup.cmd, would I then skip ahead to section 4 of the pdf?

 

Sorry for the lame questions. I'm asking now because I imagine the answer will apply (fingers again crossed) to future updates as well.

Dogen,

 

Hey, not a problem, if you are not familiar better to ask! In terms of updating from Workstation 7.0.0 to 7.0.1. It does a complete uninstall of 7.0.0, requests a re-boot, then installs 7.0.1, so you loose your darwin.iso, so you need to re-install it.

 

Click on start and select Run... and then type CMD and click on OK this will bring up the Command Prompt. Click in to the command prompt window and change directories to where you unzipped the darwin-200 zip with the updated darwin.iso from the wks7 zip, this superceeds the snowy zip. Once in the correct directory run the "setup.cmd install" command.

 

Your geustOS OS X should now be working as before.

 

Hope this helps!

 

 

 

Donk,

 

I am current running VMware Fusion 3.01.

 

What command do I use to "shrink" a Mac OS X 10.6 (Snow Leopard) virtual hard disk? Your "manual.pdf" says to use the "vmware-tools-guestd" executable to shrink a virtual hard disk.

 

The "vmware-tools-guestd" executable is not included with the "vmware-darwin-snowy.zip". The "vmware-tools-guestd" executable only appears in the vmware-darwin-200.zip.

 

BTW:

 

Where is the "vmware-darwin-snowy.zip" attachment? It has disappeared. It used to be posted at the top of this thread.

 

Thanks, Nihilator

The snowy zip has been replaced with wks7, but it does not incluse the full install suite, so install the darwin-200 zip to a directory, then overwrite the darwin.iso in the darwin-200 directory with the one from the darwin wks7 zip. Finally go to a Command Prompt and follow the instructions posted above for Dogen. Sorry cannot comment on the Fusion issue, not currently running a "real" Mac.

 

Cheers!

Link to comment
Share on other sites
Nihilator
Nihilator
Posted
Posted
Yes, this is normal, currently the only way round this is to move away from the vanilla kernel, which I did try, but no real benefit. You can configure multiple cores in the settings, even multiple CPU's but no significant benefit.

 

 

Dogen,

 

Hey, not a problem, if you are not familiar better to ask! In terms of updating from Workstation 7.0.0 to 7.0.1. It does a complete uninstall of 7.0.0, requests a re-boot, then installs 7.0.1, so you loose your darwin.iso, so you need to re-install it.

 

Click on start and select Run... and then type CMD and click on OK this will bring up the Command Prompt. Click in to the command prompt window and change directories to where you unzipped the darwin-200 zip with the updated darwin.iso from the wks7 zip, this superceeds the snowy zip. Once in the correct directory run the "setup.cmd install" command.

 

Your geustOS OS X should now be working as before.

 

Hope this helps!

 

 

 

 

The snowy zip has been replaced with wks7, but it does not incluse the full install suite, so install the darwin-200 zip to a directory, then overwrite the darwin.iso in the darwin-200 directory with the one from the darwin wks7 zip. Finally go to a Command Prompt and follow the instructions posted above for Dogen. Sorry cannot comment on the Fusion issue, not currently running a "real" Mac.

 

Cheers!

 

Mac Son of Knife,

 

I'm not running on a "real" mac. I am running a Hackintosh. I'm running VMware Fusion 3.01 on my Hackintosh. Why? Because then I can run MAC OS X as a guest. VMWare Fusion on a "real" Mac only supports Mac OS X Server as a guest.

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted
Mac Son of Knife,

 

I'm not running on a "real" mac. I am running a Hackintosh. I'm running VMware Fusion 3.01 on my Hackintosh. Why? Because then I can run MAC OS X as a guest. VMWare Fusion on a "real" Mac only supports Mac OS X Server as a guest.

 

Actually if you read my original post and the PDF, the changes I published also allow Mac OS X client version on Fusion as well, not just Server

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...