Skip to main content

ESX home lab upgrade

My original home lab, three years old now, included two PC's running virtualization software, with Intel core 2 quad CPU's and 8 GB RAM each. While browsing for a replacement, I found Didier's Shuttle SX58J3 review. I researched some alternatives, but decided to go for the SX58J3 as well, fitted with 12 GB RAM and i7-970 CPUs, hexacores with hyperthreading.
  • shallow: depth is critical in my telco rack.
  • reduced height: I might get 4 shuttles in the same space as 2 minitowers earlier. They're actually slightly wider, but not by much.
  • 12 GB per server is 50% more than the old lab (16 GB is supported but slower)
  • the Intel core i7-970 CPU gives 100% more MHz than the old Q6600. They are much more expensive, truth be told. But being Westmere generation, they support vSphere4.1 features like DirectPath I/O and Fault Tolerance.
  • I can re-use the PCIe dual gigabit adapters I had in the old lab.
One real problem so far: in BIOS v100, I couldn't change any setting without rendering the machine unbootable (hanging on "checking NVRAM"). With default settings, I could install Vista and update to BIOS v102. Booting problems were then solved, and the machines now boot ESXi 4.1 from a USB stick.
A minor issue I still have to resolve: putting ESXi in standby mode works, reviving them via Wake-On-LAN doesn't (yet).

Comments

deinoscloud said…
> reviving them via Wake-On-LAN doesn't (yet).

I've tested it with a simple WoL tool (Fusion WOL) it works fine. Make sure you send the magic packets to the LOM, eventually the first NIC's MAC address.

I haven't tested with DPM so far...

Cheers,
Didier

Popular posts from this blog

How to solve "user locked out due to failed logins" in vSphere vMA

In vSphere 6, if the vi-admin account get locked because of too many failed logins, and you don't have the root password of the appliance, you can reset the account(s) using these steps:

reboot the vMAfrom GRUB, "e"dit the entry"a"ppend init=/bin/bash"b"oot# pam_tally2 --user=vi-admin --reset# passwd vi-admin # Optional. Only if you want to change the password for vi-admin.# exitreset the vMAlog in with vi-admin These steps can be repeated for root or any other account that gets locked out.

If you do have root or vi-admin access, "sudo pam_tally2 --user=mylockeduser --reset" would do it, no reboot required.

Volkswagen UHV bluetooth touch adapter & its problems

My Volkswagen car has the "universal cellphone preparation" UHV built-in. This is the main part of a car kit, but requires an additional adapter for connecting to a cellphone. At first, I was using an adapter for my good old Nokia 6310, even after I changed to the Nokia E71. Connecting was easy: pair the phone with the "VW UHV" bluetooth entity, and done. This has the phone connected to the car kit at all times, so even non-call-related functions use the car audio system (e.g. voice recognition).
But progress will have its way, no matter what happens. So in comes the "bluetooth touch adapter". Instead of a phone-specific adapter, this is a small touchscreen device that slots into the UHV dashboard mount. Connecting a phone is very different now:
the Bluetooth Touch Adapter connects to the "VW UHV" device via bluetooth
the phone connects to "Touch Adapter" device, also via bluetoothThe device doesn't allow step 2 if step 1 didn't s…

Multiple VLANs on a Synology NAS

Synology, like other SOHO/SMB NAS vendors, touts VLAN functionality with their current DSM 4.1 software. However, the web interface just lets you specify one VLAN tag to use over each eth interface (or bond interface).
Manual approachIn the busybox environment that you can ssh into as root (after enabling ssh through the webinterface), there's all the tools you need to use multiple VLANs over one link (eth or bond), however:
First you insert the 802.1q module into the Linux kernel:
 /sbin/lsmod | /bin/grep -q 8021q || /sbin/insmod /lib/modules/8021q.koThen you add each VLAN you need to every interface (bond0 in this example)
 /sbin/vconfig add bond0 4And finally you can configure IP addresses on every interface.vlan combination (bond0.4 in this example)
 /sbin/ifconfig bond0.4 192.168.4.1 broadcast 192.168.4.255 netmask 255.255.255.0The same type of script would work on a QNAP NAS too, by the way. They offer 8021q.ko and vconfig in their commandline environment as well.
Packets from…