Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About alexiskai

  • Rank
    InsanelyMac Protégé
  1. ESXi 5 Mac OS X Unlocker

    We are having an issue with the unlocker. After the unlocker patch has been installed on an ESXi host, no non-Mac VMs can start on that host; in addition, non-Mac VMs created on that host will not easily start on other hosts - they have to be tinkered with first. Has anyone else seen this behavior and is there any fix?
  2. ESXi 5 Mac OS X Unlocker

    My install experience for 10.8: (this is on ESXi 5.1 on Dell R710 with unlocker 1.10 applied) - First hurdle was how to create the VM as hardware version 9, since the vSphere desktop client doesn't support it. Had to go through vCenter Server's web client to create the empty VM. - Once that was done, switched back to connecting directly to the host with the vSphere desktop client. - Tried to boot from: remotely attached 10.8 USB - nope 10.8 ISO mounted through virtual optical drive - nope 10.8 DMG mounted through virtual optical drive - nope 10.7.1 installer VMDK left over from previous adventures in ESX - yep - Left the 10.8 ISO attached via the optical drive; installed 10.7.1 to empty VMDK; rebooted - Installed 10.8.0 over 10.7.1; rebooted - Installed VMware Tools (darwin.iso) that I pulled from Fusion 5; rebooted - Installed 10.8.2 via Software Update; rebooted Seems to be working fine now. Next hurdle, install Server and then migrate a bunch of stuff from the 10.7 VM that has a corrupted GUI.
  3. I originally had smc.present set to TRUE, but changed it during troubleshooting. And I think I've re-run the unlocker after we patched. However, I'll go back in and run it again just in case.
  4. I think he means he finally figured out how to attach files to forum posts. FWIW, I haven't figured out my problem either.
  5. We are having an issue that just cropped up after some updates were done on our ESXi 5 hosts. Not sure what updates caused the issue. At first, a previously-functional 10.7.4 VM wouldn't boot at all. It just sat there at "PCI Configuration Begin." I Googled around and tried inserting npci=0x2000 into the boot flags, and that got it to boot somewhat, but now it won't boot to the GUI. It gives a warning that only root can launch the Window Server and then just sits there. Some services are running, e.g. Apache and SSH, but no GUI. I'm wondering whether the npci instruction got it confused about where its monitor was. Adding the -x flag to boot causes it to hang at "Load com.apple.iokit.IOUserEthernet failed; removing personalities from kernel." I also have a "known good" 10.7.2 VM that's having precisely the same problems. Something seems to have changed on the hosts, but we don't know what. I tried this on two different hosts with the same results. VMX file as follows: #!/usr/bin/vmware .encoding = "UTF-8" config.version = "8" virtualHW.version = "8" virtualHW.productCompatibility = "hosted" pciBridge0.present = "true" pciBridge0.pciSlotNumber = "17" pciBridge4.present = "true" pciBridge4.virtualDev = "pcieRootPort" pciBridge4.functions = "8" pciBridge4.pciSlotNumber = "21" pciBridge5.present = "true" pciBridge5.virtualDev = "pcieRootPort" pciBridge5.functions = "8" pciBridge5.pciSlotNumber = "22" pciBridge6.present = "true" pciBridge6.virtualDev = "pcieRootPort" pciBridge6.functions = "8" pciBridge6.pciSlotNumber = "23" pciBridge7.present = "true" pciBridge7.virtualDev = "pcieRootPort" pciBridge7.functions = "8" pciBridge7.pciSlotNumber = "24" vmci0.present = "true" vmci0.pciSlotNumber = "35" vmci0.id = "1635665540" hpet0.present = "true" powerType.powerOff = "soft" powerType.powerOn = "hard" powerType.suspend = "hard" powerType.reset = "soft" displayName = "neurobiology" numvcpus = "2" cpuid.coresPerSocket = "2" scsi0.present = "true" scsi0.sharedBus = "none" scsi0.virtualDev = "lsilogic" scsi0.pciSlotNumber = "16" memsize = "2048" sched.scsi0:0.shares = "normal" sched.scsi0:0.throughputCap = "none" sched.scsi0:1.throughputCap = "none" sched.cpu.min = "0" sched.cpu.units = "mhz" sched.cpu.shares = "normal" sched.mem.min = "0" sched.mem.shares = "normal" ethernet0.present = "true" ethernet0.virtualDev = "e1000" ethernet0.networkName = "DMZ" ethernet0.addressType = "vpx" ethernet0.generatedAddress = "00:50:56:8a:1f:c1" ethernet0.pciSlotNumber = "33" ethernet0.generatedAddressOffset = "0" usb.present = "true" usb.pciSlotNumber = "32" usb:1.present = "TRUE" usb:1.speed = "2" usb:1.deviceType = "hub" usb:1.port = "1" usb:1.parent = "-1" ehci.present = "true" ehci.pciSlotNumber = "34" svga.autodetect = "true" chipset.onlineStandby = "false" ich7m.present = "true" firmware = "efi" guestOS = "darwin11-64" uuid.bios = "56 4d 20 3a 2a 73 c0 60-17 1f 5a 07 61 7e 46 84" uuid.location = "56 4d 36 34 26 28 b6 16-05 6d 40 ab 83 82 1f 70" vc.uuid = "50 0a a2 09 ae 7e d7 fd-5c 2b e9 aa c3 46 96 be" ctkEnabled = "false" snapshot.action = "keep" tools.upgrade.policy = "manual" tools.remindInstall = "FALSE" tools.syncTime = "false" replay.supported = "FALSE" evcCompatibilityMode = "TRUE" vmotion.checkpointFBSize = "33554432" cleanShutdown = "FALSE" uuid.action = "keep" scsi0:0.present = "true" scsi0:0.fileName = "neurobiology.vmdk" scsi0:0.deviceType = "scsi-hardDisk" sched.swap.derivedName = "/vmfs/volumes/4ec2ebc8-cb031ec3-ddda-a4badb1160b0/neurobiology/neurobiology-1e4056b6.vswp" replay.filename = "" scsi0:0.redo = "" hostCPUID.0 = "0000000b756e65476c65746e49656e69" hostCPUID.1 = "000106a510100800009ce3bdbfebfbff" hostCPUID.80000001 = "00000000000000000000000128100800" guestCPUID.0 = "0000000b756e65476c65746e49656e69" guestCPUID.1 = "000106a400020800809822091febfbff" guestCPUID.80000001 = "00000000000000000000000128100800" userCPUID.0 = "0000000b756e65476c65746e49656e69" userCPUID.1 = "000106a510100800009822091febfbff" userCPUID.80000001 = "00000000000000000000000128100800" bios.forceSetupOnce = "FALSE" scsi0:1.present = "FALSE" smc.present = "FALSE" floppy0.present = "FALSE" usb:0.present = "TRUE" usb:0.deviceType = "hid" usb:0.port = "0" usb:0.parent = "-1" Another thing that I think is related is that the WindowServer process is not running. Launching it does nothing, whether I start the plist through launchd or launch it directly from the command line (except it turns the screen white and then quits).
  6. Also I'll repost the solution to the 10.7.2 crash problem in case anyone has trouble finding it. Problem: Running the 10.7.2 update causes your Mac VM to fail to boot Cause: The extension AppleLSIFusionMPT.kext does not work properly with Workstation or ESXi Workaround as follows: Open Terminal before you start the OS update. Download the 10.7.1 version of the faulty extension and unzip it. Do not run the 10.7.2 update from Software Update directly. Either download it from Apple's download page or locate it in /Library/Updates/041-1590 and run it from there. This will allow you to continue to interact with the UI after the update completes. When you run the 10.7.2 update, do not click Restart when the update completes. Let it sit there for the moment. When the update is done moving files around, run the following commands in Terminal: cd /System/Library/Extensions sudo rm -R AppleLSIFusionMPT.kext sudo mv [your download path]/AppleLSIFusionMPT.kext AppleLSIFusionMPT.kext sudo chown -R 0:0 AppleLSIFusionMPT.kext cd .. sudo touch -c Extensions sudo kextcache -system-prelinked-kernel sudo kextcache -system-caches Now complete the OS update via the installer's Restart prompt. Your VM should reboot successfully.
  7. This is actually what I did, except that I used a 10.5 VM. Here's the steps: You'll need the Lion Installer application. It's preferable to use one that's already on the LAN on which you intend to create the 10.7 VM. Now you'll need a Mac that's already a VM. Ideally this will be an ESX VM, but you can do this under Workstation and Fusion as well. Shut down your Mac VM before proceeding. On your existing Mac VM host, open the settings for this VM and add a new 5GB hard drive. You may have to make it an IDE node in order for Disk Utility to see it. However, if you're able to use a SCSI node, this will save a step later. Also, do NOT save the new disk inside the VM. Put it somewhere else, i.e. another folder or on another drive or datastore. You only want to attach it to this VM temporarily. Start up the Mac VM. You should be prompted about the new unformatted drive. Partition the new blank drive as GUID. Get access to the Lion Installer app in the Finder, either by copying it to your working VM, connecting an external drive, connecting over AFP to the server where it lives, etc. On the Mac VM, download the "mkboot" script referenced in this forum post. Open Terminal and cd to the directory where you put the mkboot script. Now run: sudo ./mkboot.sh [path to the Lion installer app] [path to the blank drive] e.g. sudo ./mkboot.sh /Volumes/MacSoftware/Install\ Lion.app /Volumes/Untitled This will image the blank drive as a Lion install disk. When it finishes, it will auto-unmount the drive. Shut down the VM. On your VM host, remove the new drive from this VM, but do not delete it. If this is an ESX VM, skip to the next step. Otherwise, you'll need to use VMware Converter to convert this VMDK to an ESX type disk. I don't know how this works, but there are probably instructions on this forum somewhere. If you have not already enabled SSH on your ESXi host, do so now. Using vSphere or SFTP or whatever your preference is, copy the folder containing the VMDK to your ESXi 5 datastore. The VMDK consists of two files, one tiny one called [name].vmdk and one very large one called [name]-flat.vmdk. These files need to stay together. Now, if you are happy with the name that VMware gave your new VMDK and if in step 3 you created it as a SCSI node, you're done. If either of those is not true, read on. Open the ESXi console or an SSH connection to the host, so that you're looking at a CLI prompt on the ESXi host. Navigate to the datastore directory where you deposited the Lion installer VMDK. To rename the container folder, if you have one, simply run mv oldname newname. For example, you could rename it "MacOS10_7_Installer". To rename the VMDK itself, cd into the container folder and run: vmkfstools -E OldName.vmdk NewName.vmdk (This will automatically rename both associated files.) If you created your VMDK as an IDE node, you need to change it to a SCSI node: Open the smaller of the two .vmdk files in vi. Find the line: ddb.adapterType = "ide" Change it to: ddb.adapterType = "lsilogic" Save and exit vi. [*]Now your VMDK is ready to serve as an installer for your new 10.7 VM. --------------------------- Edit: I should add that the reason to use the mkboot script rather than doing it all in Disk Utility is that the script creates an install partition rather than simply creating an installer boot disk. The difference between the two is that if you use an installer boot disk created via Disk Utility, when you boot off the 10.7 installer it will first copy the installation files to your blank 10.7 VMDK, then restart, then run the actual installer. Now you have 4GB of useless install files on your drive. Whereas if you use mkboot, it partitions and configures the installer disk so that the files are already present on your 5GB VMDK and the installer simply runs. This saves time and disk space.
  8. Am I correct that there are still only three approved methods for installing Lion on ESXi? 1. Install on Workstation and use Converter 2. Install 10.6 and then update via software within the VM 3. Connect InstallESD USB stick to ESXi host and pass through to VM More particularly, am I right that there is no way to install from the ISO onto a blank VM due to ESXi's inability to mount an ISO through a SCSI device? No workaround?
  9. Hi guys, I've got an interesting situation. I need to set up OS 10.5 Server on a box running ESX 4.1 (we're doing a P2V on an ailing webserver). I've done this whole shindig about 18 months ago, just as a test, and it worked fine. When I went to do it for real, of course many things had been updated in the meantime. So I downloaded the latest darwin.iso (310-macosx1064) and went about my business. Everything was fine right up to the point where I had to do the install. I discovered that I could not write anything to the virtual drive I'd created. IDE or SCSI, thin provisioning or full, didn't matter. I could format the drive, but once I tried to read or write from the formatted drive, it would hang or kernel panic. Eventually I reverted to the vmware-darwin-200 kernel, which is the way I'd tested it last year, and everything worked like a charm. Now here's my question - what's causing the panics? I'd like to resolve it because if, down the road, I need to host 10.6 Server and 10.5 Server on the same box, I'll have serious problems.
  10. Just wanted to add my experience applying these instructions on ESX4: * I was initially confused because my server offered both LSI Logic Parallel and LSI Logic SAS adapters. Turns out only Parallel works. * My final .vmx file included the following settings: ich7m.present = "TRUE" smc.present = "FALSE" keyboard.vusb.enable = "FALSE" mouse.vusb.enable = "TRUE" usb:0.present = "TRUE" usb:1.present = "TRUE" usb:1.deviceType = "hub" usb:0.deviceType = "mouse" monitor.virtual_exec = "hardware" monitor.virtual_mmu = "software" svga.vramSize="16708800" * I discovered that you can't have any special characters in the datastore name if you're going to access it from the command line. * I got EBIOS read errors when I tried to boot from a 10.5 Server Installer DVD ISO I had created by generating a .cdr file in Disk Utility and simply changing the suffix. The only way I got the ISO to work was by opening my copy of Windows XP in VMware Fusion, capturing the DVD drive, and then creating an image using ImgBurn. In ImgBurn, I had to set Disc Capacity to Disc instead of File System and I also set "Ignore reported file system." I think this worked because the DVD has both a Mac file system and a PC file system for Boot Camp. * I was able to run software updates fine without going into safe boot mode. * I am unable to resize the partition. I get the error: "MediaKit reports partition (map) too small." Otherwise everything seemed OK. I set up this VM on a server that hadn't gone live yet for another application, so I had to download the VM and shut it down eventually. I plan to upload it to another server next month and see how it works in that environment. Of course I'll need to run the scripts again.