WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple

VMware Tools for Nested ESXi updated to v1.2

08.20.2015 by William Lam // 10 Comments

I just wanted to give everyone a heads up that we have a minor update to the VMware Tools for Nested ESXi Fling (esx-tools-for-esxi-9.7.2-0.0.5911061.i386.vib) and you can find the list of changes below.

What's new in version 1.2:

  • Larger resource pool for programs started using the VIX/Guest Operations API (resolves this issue)
  • Now supports Guest Time Synchronization
  • No longer require -f flag to install the VIB

If you have any feedback, feel free to leave a comment here or on the Flings page.

Categories // ESXi, Nested Virtualization, vSphere 6.0 Tags // ESXi, nested, nested virtualization, vSphere 5.5

ESXi 6.0 on Apple Xserve 2,1

08.20.2015 by William Lam // 9 Comments

I really enjoy hearing from my readers, especially when they share some of the unique challenges they have come across or boundaries they have pushed with our VMware software. Several weeks back I received an interesting email from a reader named John Clendenen who was able to get ESXi 6.0 running on both his Apple Xserve 3,1 as well as Xserve 2,1! To be honest, I was pretty surprised to hear that this worked and not only that, there was not a whole lot that John had to do to get it working. I thought this was a pretty cool setup and asked if John was interested in sharing more details with the VMware/Mac OS X community in case others were interested.

Disclaimer: This is not officially supported by VMware, please use at your own risk.

*** This is a guest blog post from John Clendenen ***

For the past 5 years, I have lived in New York where I work at various print and post-production studios. The IT situations in many of these locations is often home-grown and sub-adequate, if not barely functional, so I took it upon myself to learn OS X Server administration. I have a background in computer science and networking, so it wasn’t a huge leap to step into administration. I was able to gradually build one studio’s IT infrastructure form a single AFP share with incessant permissions problems, to an Open Directory driven, single sign-on infrastructure with mobile homes, messaging etc.. However, with each OS X Server update, things broke, and I was spending a lot of time putting out fires.

This led me to pursue virtualization in hopes of isolating services on separate machines, without telling the studio to go buy 8 Apple Mac Minis. However, I needed to learn how to do this, before pitching it to them, so I looked on Craigslist for some cheap hardware. I found an Xserve 2,1, which I was able to talk down to $100. I also found a brief post in a thread that said that the Xserve 2,1 ran ESXi 5.5 without issue. I figured I’d take the plunge and just resell it on eBay if it didn’t work out.

Since then, my home lab has grown considerably, and I have learned that the best way to provide Mac services, is simply to use Linux (I’ve had a great experience with Netatalk). That said, Open Directory, Software Update, Caching and a few other services still need to be run on a Mac, so it’s still necessary to have the hardware. For a while, I had 3 Xserves, all purchased very cheaply, running VMs. I just sold one, and will sell another in the next month or two in favor of some Supermicro hardware (I really am mostly running Linux VM’s at this point). I’ll keep the one to run a few Mac OS X VMs. I’m still working on getting Samba 4 to work as the PDC, but once that is running smoothly, I’ll have a functional environment that I can take to the studios where I work (with approved hardware of course). Then I’ll have an improved work experience, while also pulling some extra income on the installation/maintenance.

Anyway, you’ve come here to read about running ESXi 6.0 on an Xserve 2,1. Well, it works. It’s 7 years old, and not officially supported, but you already know that. So, if you were considering it, I doubt anything here will dissuade you. On top of that, there’s not much for me to say other than, it works. No tricks to it, just install and you’re off.

pic1
That said, I do have some recommendations and tips to help you if you want to get the most out of this hardware. 2 months ago, since I swapped out the RAID card for the standard backplane/interconnect and upgraded the RAM. It hasn’t skipped a beat since.

My System

This is my home custom 13u rack with sound insulation and active air flow. Networking is in the back (Ubiquiti). It sits in a lofted storage area with an A/C and vents into the bathroom.

pic8
Here you see an Xserve 3,1 on top of an Xserve 2,1. There’s a blank unit because I just sold an Xserve 2,1 on eBay, and the other 2,1 will be for sale soon as well to make room for a 4 node 2U Supermicro Server. The NAS is comprised of a 4u head unit and a 4U JBOD running Centos. Last of course, is a 2U CyberPower UPS which is really just to condition the power and keep brownouts from taking down the system.

I have about a dozen VM’s running between the 2 Xserves. I have each Mac OS X service separated on it’s own installation. This way I can run updates per service. It’s especially nice to have Open Directory separate from less important services. I also have Debian, Centos and OpenBSD VMs running various services. Getting the Xserve 3,1 running ESXi 6 is possible, but more problematic. Now that I have it working, I’m dropping the 2,1’s simply because the processors aren’t multithreaded. I am currently working on a companion article to this one, detailing my experience with the Xserve 3,1, so that information will be available soon.

Storage

1. Don’t use the RAID backplane/interconnect or count on using it. ESXi 6 does not recognize it, and RDM appears to work at first and then will crash your VM and never show up again. You can have it installed in the Xserve without any issue, but you’ll get a lot more mileage out of the hardware if you have the standard backplane/interconnect.

The backplane you want appears periodically on eBay. The part number is: 661-4648

2. If/once you have the non-RAID backplane/interconnect, keep in mind that it is SATAII and will only support 3Gb/s. I am using 3 old 500Gb WD RE3’s, but I’d recommend using some older SSDs that will max out the SATAII interface without paying for speed you can’t use. Be sure you consult the Apple Drive Module compatibility page to make sure you have the right drive caddies. They all fit, but they don’t all work.

Apple Drive Module Compatibility Chart: https://support.apple.com/en-us/HT1219

pic2
3. PCIE Flash is a good idea, whether you use it for cache, VM’s or as the ESXi boot disk, it is by far the fastest storage option. I have not invested in it, but the good people at Mushkin have told me their Scorpion PCIE flash will work in ESXi 6. Please contact them yourself though before investing in one of their cards. I have not tested them. While this will give you the best performance out of your Xserve 2,1, it seems like overkill to me, but hey, if you want to push this thing, you might find some meaningful performance gains here.

Mushkin Scorpion PCIE Flash: http://www.poweredbymushkin.com/index.php/products/solid-state-drives.html

4. It might occur to you that replacing the optical drive with an ssd might be a good idea. While MCE Technologies makes “Optibay” for Xserve 2,1, the connection is IDE, so this is not recommended. I also don’t know if ESXi would recognize it. My gut says probably, but again, it’s too slow to be useful. It isn’t that cheap either.

MCE Technologies Optibay: http://store.mcetech.com/mm/merchant.mvc?Store_code=MTOS&Screen=PROD&Product_Code=OBSXGB-XS

Network

There are a lot of options here. You can plug any network card that you want really as long as you can at least find an anecdotal account of it working on ESXi 6.

I have one such anecdote for you, and it is also a strong suggestion. The company Silicom makes/made several models of gigabit NICs which are all incredibly inexpensive, are all over eBay and work in ESXi 6. Buy the 6 port model. It’s cheap and you’ll get great scaling with ESXi load balancing across 8 gigabit ports.

The Xserve 2,1 has the added advantage here of an optional PCIX riser. If your model has one, or you find one for cheap, you can save even more on the Silicom NIC. The PCIE models go for $60-$80 on eBay, while the PCIX models go for $40.

pic3

Memory

ECC DDR2 is pretty cheap and easy to find used. I recommend memory4less though. I had to return some RAM that was mislabeled from a random eBay distributor. Memory4less will get it right. http://www.memory4less.com/

pic4

Processors

One great perk of the Xserve 2,1, is that you can upgrade the single processor hardware to dual processor. You can pick up an additional processor on eBay for $40 or so, but you’ll need to get a heat sink as well. The single processor units come with a fake aluminum heat sink, but do not use it. You want a copper one. I believe the heat sinks in the Xserve 1,1 are the same. Don’t forget the thermal paste.

pic5

Minor Issues

1. The Performance tab throws an error.

pic6
2. Not sure about the hardware sensors, but it looks like not everything is working even if it’s showing up. I did not do any testing here.

pic7
Stay tune for Part II of John's guest blog post on running ESXi 6.0 on Xserve 3,1.

Categories // Apple, ESXi, Not Supported, vSphere 6.0 Tags // apple, ESXi 6.0, notsupported, osx, xserve

New HTML5 Embedded Host Client for ESXi

08.11.2015 by William Lam // 61 Comments

How many of you remember the old WebAccess interface that came with classic ESX 2.0? I know I sure do! It was a very useful interface that allowed administrators to easily manage their ESX hosts through a web browser that provided basic VM creation, troubleshooting and most importantly initial bootstrap configurations for greenfield deployments where a vCenter Server may not be available yet.

Screen Shot 2015-07-17 at 8.07.56 AM
I have always felt that having a simple web interface that customers can just point their browser to an ESX(i) host after an installation would be the most intuitive from a user experience standpoint. About a year ago, I was involved in a project with two VMware Engineers, Kevin Christopher and Jehad Affoneh, when we worked on an early prototype of an optimized Embedded Host Client for ESXi. We socialized the prototype across many different teams at VMware and the overwhelming feedback was super positive. Earlier this year, with the help of the ESXi PM and the Engineering team, they decided to take the concept of the prototype to the next level and really turn it into something that could really be used by customers.

UPDATE: (08/25/15) - v2 has just been released, be sure to take a look at this blog post for more details.

Today, I am very happy to announce the release of a new VMware Fling: HTML5 Embedded Host Client for ESXi which is currently distributed as a simple installable VIB. The Fling currently only supports ESXi 6.0 (however, there is a workaround ESXi 5.x which you can find below). In this first release, the Free ESXi Hypervisor is not supported, but the plan is to add support for this in a future update. Here is a list of some of the supported operations in this first release:

  • VM operations (power on, off, reset, suspend, etc.)
  • Creating a new VM, from scratch or from OVF/OVA (limited OVA support)
  • Configuring NTP on a host
  • Displaying summaries, events, tasks and notifications/alerts
  • Providing a console to VMs
  • Configuring host networking
  • Configuring host advanced settings
  • Configuring host services
  • License management

Once the VIB is installed, which does not require a system reboot, you simply just point your web browser to the following URL: https://[ESXI-HOST]/ui and login with an administrator account.

embedded-host-client-0
One of my favorite features of the Embedded Host Client is the integrated VM Console which is accessible directly within the browser and does not require any additional plugins or installers. I do want to mention that the VM Console feature is currently only available when installed onto an ESXi 6.0 host. One other caveat that I would like to point out is that for customers who wish to try the Embedded Host Client on ESXi 5.5 or on ESXi 6.0 host which have been upgraded from an ESXi 5.x environment, the following workaround is required:

ESXi 5.x or ESXi 6.0 (upgraded from ESXi 5.x) workaround:

Step 1 - SSH to your ESXi host and open the following configuration file:

/etc/vmware/rhttpproxy/endpoints.conf

Step 2 - Remove the following line and save the changes

/ui                      local            8308                             redirect       allow

Step 3 - Restart the reverse proxy by running the following command:

/etc/init.d/rhttpproxy restart

Step 4 - Open a browser to the following URL: https://[ESXI-HOST]/ui/ and note the additional trailing "slash" at the end of the URL. This is mandatory else the Embedded Host Client page will not properly load.

Note: This only applies to ESXi 6.0 hosts which have been upgraded from ESXi 5.x or pre-ESXi 5.5 Update 3 systems. You may also noticed translation errors when running the Fling on pre-ESXi 6.0, this is expected. For the best experience, we recommend using ESXi 6.0 or waiting until ESXi 5.5 Update 3 is released which will resolve this problem.

Having spent the last couple of months working with both of the Engineers: Etienne Le Sueur and George Estebe, I was able to help provide feedback and usability enhancements and I think you will really like what is there in this first release. I do want to stress that this is in no way, shape or form a comprehensive replacement for the existing vSphere C# Client functionality, but I think it could be a good start if the feedback from customers is positive. I really hope you do give this a try in your lab environment and please let us know what features and capabilities we should add next. There is a variety of way you can provide feedback by leaving a comment on this blog post, leaving a comment on the Flings page.

Big thanks goes out to both George and Etienne who took on the challenge and did a fantastic job on the Fling!

Categories // ESXi Tags // embedded host client, ESXi, Fling, HTML5, web access

  • « Previous Page
  • 1
  • …
  • 102
  • 103
  • 104
  • 105
  • 106
  • …
  • 146
  • Next Page »

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Automating the vSAN Data Migration Pre-check using vSAN API 06/04/2025
  • VCF 9.0 Hardware Considerations 05/30/2025
  • VMware Flings is now available in Free Downloads of Broadcom Support Portal (BSP) 05/19/2025
  • VMUG Connect 2025 - Minimal VMware Cloud Foundation (VCF) 5.x in a Box  05/15/2025
  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...