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.

relume

Members
  • Content count

    7
  • Joined

  • Last visited

About relume

  • Rank
    InsanelyMac Protégé
  1. Differences of Unlocker 1.3.0 and Unlocker 1.3.1? Hello I am wondering what are the differences between Unlocker 1.3.0 and 1.3.1 in order to understand why I had no success with 1.3.0 to enable working MacOS-guest but had success with 1.3.1. On several SuperMicro server boards with Xeon 56XX cpu I have running the latest ESXi 5.5.0 updates (u2) and patches (201412001) together with Unlocker 1.3.0 and had never problems to run MacOSX 10.6, 10.8, 10.9 and 10.10 VM-guests. On an other server from IBM x3550 M4 with Xeon E-2620 cpu I had running ESXi 5.1 with the latest patches and Unlocker 1.2 and MacOSX-guest (10.6) for a year without any problems. Now I "upgraded" on this server ESXi 5.1 to 5.5.0 by installing a total new instance of ESXi 5.5.0 (starting with 5.5.0 u1) to a new USB-medium and applied all following updates and patches. Thereafter I switched in the ESXi host configuration the scratch partition to a installed SSD as I did before under ESXi 5.1 and as I have it on the others servers with the SuperMicro boards and finally installed Unlocker 1.3.0. Unfortunately I was not able to startup now the MacOSX-guests, nor a MacOSX (10.6) installer CD-ROM iso. MacOSX-guests startups were always stopped on the grey Apple logo, and for the MacOSX installer CD-ROM by a spin ball on a void dark grey screen. So far all guest vmx configurations files looked ok, quasi the same as on the well running MacOSX-guests on the SuperMicro servers. After hours I decided to try Unlocker 1.3.1 on the IBM server and thereafter all MacOSX-guests booted and worked correctly and instantly. So I am wondering why Unlocker 1.3.0 "works" on identical ESXi 5.5.0 installations (same upgrades, updates and patches" but not on different hardware and what could be the reasons why Unlocker 1.3.1 works on the "problematic" server hardware? I would appreciate any hint in order to understand, many thanks in advance. P.S. 1 : Many thanks to all that have contributed to develop Unlocker and adapt it further!! P.S. 2 : Is there any way to pass boot parameters on the ESXi 5.5.0 guest boot-efi shell in order MacOSX-guests would boot up in verbose mode? I could not figure out how to pass the -v parameter.
  2. Hello, unfortunately link aggregation on OSX guest does not work very well - the link aggregation is much slower than a single nic. Also passthrough an 10Gb adapter does not work at all. So the only solution would be an VMXNET3 native driver for OSX. Is the VMXNET3 driver for Linux guest OpenSource? By the way for OSX guest the E1000E nic should be used - by setting it manually in the vmx-setting, as the E1000 creates often PSOD.
  3. VMware Unlocker for OS X

    ESXi 5.5.0 u2 (build 2068190) VMware Unlocker 1.3.0 Guest OSs : MacOSX server 10.9.5, MacOSX Server 10.6.8 Hello VMware Unlocker 1.3.0 works perfectly for our configurations - many thanks!. Although I have some question about virtual NIC drivers and MacOS guests: e1000 on the guest OS crashes the ESXi host (purple screen) on heavy NIC-load on the guest OS (no difference if VMware Tools for darwin are installed or not). The problem should have been addressed with the actual ESXi 5.5 update 2 but it seems to persist. Is there any possibility to enable vmxnet3 on the guest MacOSX OS? Is there some "third party" driver to be installed on the guest MacOSX OS? Unfortunately VMware Tools for Darwin does not contain such drivers. In the mean time we have manually enabled on the guest.vmx file the e1000e NIC instead of e1000. e1000e seems to be stable and has not provoked any ESXi crash in the last 3 days. Some other question about network performance. Are the e1000 or e1000e NIC drivers on the guest MacOSX limiting the transfer rate to 1Gb/s or can this limit be outreached? Teaming configuration (two or more virtual nics) on the guest MacOSX is possible, but does not work properly. Is there an other possibility to outreach the 1Gb/s limitation of the virtual NIC on the guest MacOSX? Many thanks for any considerations.
  4. Hello I upgraded our VMware ESXi 5.1.0 host to 5.5.0 by a fresh install of ESXi to an USB memory stick (as before for 5.1.0) . After sucessful test of our Linux VMs I applied unlocker version 1.2.0 and found problems in disconnecting VWware Sphere vi and cli client (both version 5.5.0) and Linux VMs that did not start temporarlly and by random, complaining "msg.vmk.status.VMK_ACCESS_DENIED". Preexistings VMs with MacOSX Server 10.6.8 (under ESXi 5.1.0 and unlocker 1.1.0 worked stable) crashed soon after 30-60 seconds, crashing also VMware Sphere vi client. Some times we could reconnect the VMware Sphere vi client immediately or some time later or not at all. So we installed unlocker version 1.2.1 (replacing esxi/install.sh - first by unstalling it and rebooting the ESXi host). We had to boot the host twice in order we could connect with the VMware Sphere vi Client. Now the preexistings MacOSX Server 10.6.8 VMs booted correct and are for serveral minutes <=30 stable and then randomly crashed again by stressing them with benchmark tests. However VMware Sphere vi Client is disconnecting after some minutes (ca. 5-10 minutes), even if no MacOSX VM is running, or VMware Sphere vi Client is crashing at all. In the Host log we can see, that most often the Host process "/bin/hostd" is crashing. The problem seems not only to be related to missing space on the bootbank partition, but to other issues caused by applying unlocker. We unstalled for this moment unlocker, as the MacOSX Server VMs were at this moment only for test purposes, althought we planed to convert actuall hacintosh MacOSX 10.6.8 servers to ESXi VMs.
  5. Hello Many thanks for your response. I found the way, how under MacOSX a "correct" ISO-image can be created from the retail MacOSX installer DVD. Open the Apple disk utility and select/mark with the retail installer DVD inserted/mounted on the drive area the DVD-Drive itself and not the assigned MacOSX installer DVD volume. It is very important to not select the volume but the DVD-drive itself. Then create from the selected DVD-drive an image in the CD/DVD-Master format (".cdr"). After the image is successfully created, change on the image file the suffix from ".cdr" to ".iso". Thereafter upload this image file to a VMWare store and connect on the VM configuration the iso-image to the virtual VM CD/DVD-Drive. On starting up the VM selecet at the boot loader prompt by activating the F5-key the MacOSX installer disk. Also enter at the boot loader prompt the command "rd(0,1)/legacy_kernel -v -f -x rd=disk1s3" and then hit the enter-key. Without this boot-load command the installation will not start correctly and shows the message "still waiting for root device". best regards, relume
  6. Hello First I would like to thank to all peoples that made it possible that MacOSX (Server) can be installed on VMWare ESXi 4.x! This is really some "ray of hope" after Apple has decided to discontinue the rack mountable Xserve models last November. I have now running a test installation of MacOSX Server 10.6.7 (installation first with 10.6.3 retail DVD) with ESXi 4.1.0u1 with darwin.iso 310_1064 on a SuperMicro SuperServer with max. 4 System nodes (actually only one single node with one Xeon L5620 CPU). As newbie to the installation of MacOSX under VMWare ESXi i would like to ask, if the "simulated" virtual guest system, actually shows up as a minimac 2.1 could be altered to be recognized as mac pro 5.1 or xserve 3.1? Also I am wondering, if the recognized mac type or mac model has some influence to the performance of the installed guest OS (MacOSX Server 10.6.7)? Thank you very much in advance, reluem
  7. Hello I tried to install on VMWare ESXi 4.1.0u1 MacOSX Server 10.6.3 from an ISO created on MacOSX from the retail DVD with the Apple disk utility by saving the image in the CD/DVD master format and replacing the ".cdr" suffix to ".iso". Unfortunately I was not able to boot with darwin.iso 310_1064 from this MacOSX Server installation ISO image. In the end I attached a physical DVD-ROM usb-drive to the server and configured it as a passthrough device in ESXi. In this way I was able to boot the DVD iso image and could install MacOSX Server successfully. Although the installation worked with the physical DVD, I would like to place the somewhat "stupid" question: how can be created a working ISO from the retail DVD on a MacOSX Computer, as this would be more comfortable and flexbile for installation on VMWare ESXi? Thank you for any suggestions, Relume
×