Working with templates has become much easier in vSphere 7 since VMware added new features to content libraries. It is now possible to deploy VMs directly from templates in content libraries and to update templates while the orignal version stays in place.
If there are still classic templates in vCenter, you can clone them to a content library.
Transfer the old template to the content library as a new template.
Failed to export OVF package
After klicking OK, an error message “Failed to export OVF package” might be issued. Usually followed by a second message that leads to the root cause of the problem.
File ds:///vmfs/volumes/vsan:527a6824b9bfa7ad-36f48a2cd78b9685/1f40b55e-f88d-e569-9d66-002590bb2ed0/b02cb65d-e81b-49cb-a654-ef26ea21b2f7/ubuntu-20.04-live-server-amd64_5696e54c-c62a-4fa8-b007-0192a28ff53d.iso was not found
The only interesting part of the message are the last four words: “iso was not found“. Obviously the VM had an iso image mounted before it was converted to a template. Luckily that problem is easy to resolve by converting the template into a VM and removing the iso image from CD-ROM settings. Change it to “Client Device” for example. Convert the VM back to a template and retry cloning to content library. Without a mounted iso image the conversion works without an error.
Updates to the vCenter Server Appliance (VCSA) are usually easily done from the VAMI interface. In rare cases, however, problems may occur during the update. Recently I tried to update the VCSA in the lab from version 7.0.0 (16386335) to 7.0.0 U1 (16858589). The update was started via a locally mounted ISO image. It was detected that an update is available, but the update failed right after start. The problem referenced in the link above did not apply in this case.
In such cases it is worthwhile to try the VCSA shell. To do this, it must first be allowed in VAMI, then the session can be established via SSH client.
It is important that you’re NOT on the bash shell. You can return from bash to the VAMI shell with the command below.
In the first step the update packages are staged. The ISO should be mounted at this time.
software-packages stage --iso --acceptEulas
The process checks some requirements, detects source- and destination version and tests for a mounted iso.
software-packages list --staged
The command listed above will show details to the staged package.
If everything looks correct we can trigger the update.
software-packages install --staged
The update to version 7.0 U1 finished without any issues.
VMware vSphere and other products from the VMware ecosphere highly rely on DNS resolution. Name resolution is crucial to the virtual world and there’s a rule amongst troubleshooters:
“If you’ve ruled out DNS as the origin of your problem – check DNS again.”
In the corporate sector there are usually DNS servers of various types. Either hardware appliances with DNS functionality, or entire Microsoft Active Directory servers. However, if you want to set up a homelab, your office usually has only a small DSL router with a (poor) DHCP server functionality. It is possible to run DNS servers or whole ADS domain controllers inside a VM, but then we have the chicken and egg problem. The VM will start after cluster and vCenter are online. Until then wild things can happen in a vSphere cluster without DNS. So we are looking for a small, energy-saving, inexpensive and configurable hardware solution as DNS server for our homelab. Sounds like the Swiss-Army knive, but it can be easily realized with a Raspberry Pi.
In this article I will explain what you need to build your DNS server and how to configure a subnet for the lab.
Raspi as DNS-server
For this project we don’t need the latest model of the Raspberry Pi. A Raspi 3b model is fine for this purpose and the accessories are also available at low prices.
Raspberry Pi 3b+ / 1GB / 4-Core / 1,4 GHz
Micro SD card 32 GB
Power supply 2,5A (optional)
Parts list with average prices as of June 2020
For much less than 100€ you’ll get a tiny server which can also fulfill other tasks like home automization or as ad-blocker pi-hole.
There are a few things to consider. In principle you can power the Raspi via USB. But you have to make sure that the source delivers at least and reliably 1.2A. Power sources with 2.5A are recommended. My first boot attempts failed because my USB power supply did not provide enough power.
The Raspi requires a micro-SD card as permanent boot and storage media. Here you shouldn’t take the cheapest product, but for less than 10 € you can get 32 GB from a trustworthy brand.
I had the special pleasure of working on a book project as co-author in the past months. It is entitled “VMware vSphere 7 – Das umfassende Handbuch” (“VMware vSphere 7 – The Compendium”, published in German language) and will be published in November by Rheinwerk-Verlag. It is the 6th updated and extended edition of this series.
This book covers a wide range of vSphere 7. From basic architecture to setup and day-2 operations. It helps novice and advanced IT administrators understand the principles of vSphere, network virtualization with NSX-T, vSAN, container workloads, VMware Cloud Foundation, Hybrid Cloud, and SDDC.
My contributions are the completely new written chapters Monitoring and vSAN. The chapter Monitoring is about giving the administrator an overview of the integrated monitoring tools and how to use and interpret them. It also introduces VMware and third-party tools. The vSAN chapter explains the fundamental structure of this storage virtualization and explains the special features of a vSAN cluster in comparison to conventional storage solutions.