February 2026
M	T	W	T	F	S	S
	1
2	3	4	5	6	7	8
9	10	11	12	13	14	15
16	17	18	19	20	21	22
23	24	25	26	27	28

Archive for the ‘ESXi6.7’ Category

Some ESXi 7.x notes

Posted by jpluimers on 2021/12/16

Yes, I know this is late in the game, but I’m still catching up with some of the things after from autumn 2019 to spring 2021 spending most of my time on rectum cancer treatment and other core things.

So here are some links on ESXi 7.x so I know what to expect to upgrade existing ESXi 6.x installations and get some new ones up. This will hopefully make some software development easier too, as I plan to have a build-rig some day.

But first of all a surprise for me:

ESXi 7 on ARM

I had not expected ESXi 7 to be available on ARM in 2020 yet, but it’s there and certified to run on Raspberry Pi 4. So here are some links:

ESXi 7 on x64

The bulk of the links:

[Wayback] VMware ESXi Release and Build Number History | virten.net
[Wayback] Free ESXi 7.0 – How to Download and get License Keys | virten.net
[Wayback] ESXi 7.0 Free: New features, limitations, upgrade | 4sysops
[Wayback] Homelab considerations for vSphere 7
[Wayback] Nested ESXi Virtual Appliance
[Wayback] Quick Tip – HTTPs now supported with wget on ESXi 7.0
[Wayback] Important – NVMe SSD not found after upgrading to ESXi 7.0
- [Wayback] NVMe SSDs are not recognized anymore after upgrading to VMware ESXi 7 – ivobeerens.nl
  
  William Lam and the VMware support team discovered quickly that we used the wrong esxcli update command (esxcli software vib update). The correct command to upgrade an ESXI host is: esxcli software profile update.
- [Wayback] VMware NVME PCIE Driver Missing on ESXi 7.0 after upgrade from 6.7 U3 on SuperMicro 5028D-TN4T (Updated) – jeffreykusters.nl
[Wayback] A trip down memory lane with the vSphere C# Client and ESXi 6.7 & 7.0
- [Archive.is] William Lam on Twitter: “Just deployed the latest F@H @VMware Appliance using the new #vSphere7 Client 😊… “
[Wayback] TOP differences between ESXi 6.7 and ESXi 7.0 | ESX Virtualization

–jeroen

Read the rest of this entry »

Posted in ESXi6, ESXi6.5, ESXi6.7, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »

VFrontDe/ESXi-Customizer-PS: PowerCLI script that greatly simplifies and automates the process of creating fully patched and customized VMware ESXi installation images

Posted by jpluimers on 2021/11/30

On my list of things to try, as it allows me to have an ISO at hand in case I ever need to quickly re-install a machine to the current patch level (for instance when the USB boot stick breaks down: these things happen in reality): [Wayback] VFrontDe/ESXi-Customizer-PS: PowerCLI script that greatly simplifies and automates the process of creating fully patched and customized VMware ESXi installation images

ESXi-Customizer-PS is a Powershell script that greatly simplifies and automates the process of creating fully patched and customized ESXi 5.x and 6.x installation ISOs using the VMware PowerCLI ImageBuilder module/snapin.

…

Requirements

A Windows computer (XP or newer) with Powershell 2.0 or newer

VMware PowerCLI version 5.1 or newer

…

You can get the code from [Wayback] ESXi-Customizer-PS/ESXi-Customizer-PS.ps1 at master · VFrontDe/ESXi-Customizer-PS.

The old site (which still has most of the documentation) can be reached at two places:

[Wayback] esxi-customizer-ps.v-front.de which redirects to
[Wayback] www.v-front.de/p/esxi-customizer-ps.html

A video showing how to use it is below the signature.

The above links via [Wayback] Custom ESXi ISO with ne1000 driver for install on Intel NUC Frost Canyon – seanwalsh.dev.

Oh: you can check if you have a PXE, USB or HDD installation of ESXi via the steps here: Determining the ESXi installation type (2014558) | VMware KB.

Some bash parameter propagation links that hopefully will work with ash/dash too

Posted by jpluimers on 2021/10/27

For my link archive; I started with [Wayback] dash get all parameters quoted – Google Search:

[Wayback] Handling positional parameters [Bash Hackers Wiki] has this handy table:

Parameter(s) Description

$0 the first positional parameter, equivalent to argv[0] in C, see the first argument

$FUNCNAME the function name (attention: inside a function, $0 is still the $0 of the shell, not the function name)

$1 … $9 the argument list elements from 1 to 9

${10} … ${N} the argument list elements beyond 9 (note the parameter expansion syntax!)

$* all positional parameters except $0, see mass usage

$@ all positional parameters except $0, see mass usage

$# the number of arguments, not counting $0

These positional parameters reflect exactly what was given to the script when it was called.

Option-switch parsing (e.g. -h for displaying help) is not performed at this point.

See also the dictionary entry for “parameter”.

[Wayback] Handling positional parameters: mass usage [Bash Hackers Wiki] has this summary table:

Syntax Effective result

$* $1 $2 $3 … ${N}

$@ $1 $2 $3 … ${N}

"$*" "$1c$2c$3c…c${N}"

"$@" "$1" "$2" "$3" … "${N}"
[Wayback] Parameter expansion [Bash Hackers Wiki]
The elaborate answer to [Wayback] How to pass all arguments passed to my bash script to a function of mine? – Stack Overflow by [Wayback] User Gordon Davisson – Stack Overflow of which the first part is:
The $@ variable expands to all command-line parameters separated by spaces. Here is an example.
```
abc "$@"
```
When using $@, you should (almost) always put it in double-quotes to avoid misparsing of arguments containing spaces or wildcards (see below). This works for multiple arguments. It is also portable to all POSIX-compliant shells.

It is also worth nothing that $0 (generally the script’s name or path) is not in $@.

The Bash Reference Manual Special Parameters Section says that $@ expands to the positional parameters starting from one. When the expansion occurs within double quotes, each parameter expands to a separate word. That is "$@" is equivalent to "$1" "$2" "$3"....
Last part of the [Wayback] Accessing bash command line args $@ vs $* – Stack Overflow answer by [Wayback] Serge Stroobrandt:

If the arguments are to be stored in a script variable and the arguments are expected to contain spaces, I wholeheartedly recommend employing a "$*" trick with the input field separator set to tab IFS=$'\t' [Wayback].

and comment by Serge as well:

Here is [Wayback] an example, which includes quoted input. The input also matters!

Parameter(s)	Description
`$0`	the first positional parameter, equivalent to `argv[0]` in C, see the first argument
`$FUNCNAME`	the function name (attention: inside a function, `$0` is still the `$0` of the shell, not the function name)
`$1 … $9`	the argument list elements from 1 to 9
`${10} … ${N}`	the argument list elements beyond 9 (note the parameter expansion syntax!)
`$*`	all positional parameters except `$0`, see mass usage
`$@`	all positional parameters except `$0`, see mass usage
`$#`	the number of arguments, not counting `$0`

Syntax	Effective result
`$*`	`$1 $2 $3 … ${N}`
`$@`	`$1 $2 $3 … ${N}`
`"$*"`	`"$1c$2c$3c…c${N}"`
`"$@"`	`"$1" "$2" "$3" … "${N}"`

[Wayback] Propagate all arguments in a bash shell script – Stack Overflow (thanks [Wayback] Sdaz MacSkibbons for the answer and [Wayback] Ilan Schemoul to make it understandable by applying proper naming of the script files):

Use "$@" instead of plain $@ if you actually wish your parameters to be passed the same.

Observe:

$ cat no_quotes.sh
#!/bin/bash
echo_args.sh $@

$ cat quotes.sh
#!/bin/bash
echo_args.sh "$@"

$ cat echo_args.sh
#!/bin/bash
echo Received: $1
echo Received: $2
echo Received: $3
echo Received: $4

$ ./no_quotes.sh first second
Received: first
Received: second
Received:
Received:

$ ./no_quotes.sh "one quoted arg"
Received: one
Received: quoted
Received: arg
Received:

$ ./quotes.sh first second
Received: first
Received: second
Received:
Received:

$ ./quotes.sh "one quoted arg"
Received: one quoted arg
Received:
Received:
Received:

–jeroen

Posted in *nix, *nix-tools, ash/dash, ash/dash development, bash, bash, Development, ESXi6, ESXi6.5, ESXi6.7, ESXi7, Power User, Scripting, Software Development, Virtualization, VMware, VMware ESXi | Leave a Comment »

ESXi: listing virtual machines with their IP addresses

Posted by jpluimers on 2021/10/26

This is sort of a follow-up on VMware ESXi console: viewing all VMs, suspending and waking them up: part 4 which already gave part of the configuration details of all the configured VMs.

Back then, we ended with this:

List the `vmid` values, power status and name of all VMs

Back to the listing script vim-cmd-list-all-VMs.sh:

#!/bin/sh
# https://wiert.me/2021/04/29/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-4/
vmids=`vim-cmd vmsvc/getallvms | sed -n -E -e "s/^([[:digit:]]+)\s+((\S.+\S)?)\s+(\[\S+\])\s+(.+\.vmx)\s+(\S+)\s+(vmx-[[:digit:]]+)\s*?((\S.+)?)$/\1/p"`
for vmid in ${vmids} ; do
    powerState=`vim-cmd vmsvc/power.getstate ${vmid} | sed '1d'`
    name=`vim-cmd vmsvc/get.config ${vmid} | sed -n -E -e '/\(vim.vm.ConfigInfo\) \{/,/files = \(vim.vm.FileInfo\) \{/ s/^ +name = "(.*)",.*?/\1/p'`
    vmPathName=`vim-cmd vmsvc/get.config ${vmid} | sed -n -E -e '/files = \(vim.vm.FileInfo\) \{/,/tools = \(vim.vm.ToolsConfigInfo\) \{/ s/^ +vmPathName = "(.*)",.*?/\1/p'`
    echo "VM with id ${vmid} has power state ${powerState} (name = ${name}; vmPathName = ${vmPathName})."
done

It uses vim-cmd vmsvc/getallvms, vim-cmd vmsvc/power.getstate and vim-cmd vmsvc/get.config with some sed and a for loop from dash to generate a nice list of information.

A long time ago, I already figured out that vim-cmd vmsvc/get.guest # gives all guest information including network information for a running VM that has either VMware Tools or open-vm-tools running (see VMware ESXi console: viewing all VMs, suspending and waking them up: part 3 for the difference between these two tools).

A full output of a sample VM is below the signature.

There are a few places that have the LAN ipAddress. For now, I choose to use only the IPv4 main address from ipAddress, which is in between (vim.vm.GuestInfo) { and net = (vim.vm.GuestInfo.NicInfo) [.

I modified the above script to become this:

Read the rest of this entry »

Posted in *nix, *nix-tools, ash/dash, ash/dash development, Development, ESXi6, ESXi6.5, ESXi6.7, ESXi7, find, Power User, Scripting, sed, sed script, Software Development, Virtualization, VMware, VMware ESXi | Leave a Comment »

ESXi shell: appending the parent directory of a script to the path and starting a new shell, even if the script is symlinked

Posted by jpluimers on 2021/10/26

I needed a way to append the directory of a script to the path as all my tool scripts are in there, and I did not want to modify any profile scripts as these might be modified during ESXi upgrade.

First you need the full script filename through readlink then toe parent directory name through dirname:

- [Wayback] string – bash : Bad Substitution – Stack Overflow
```
me@pc:~$ readlink -f $(which sh)
/bin/dash
```
  By [Wayback] Vanni Totaro.
- [Wayback] shell – Getting parent’s directory name by piping the results of dirname to basename in a Bash script – Stack Overflow
```
# echo 'test/90_2a5/Windows' | xargs dirname | xargs
basename90_2a5
```
  By [Wayback] Rafael.

Note there might be dragons with more symlinks or different shells:

I created the script below. It is not perfect, but for my situation it gets the job done.

If you do not start a new shell, then the export is lost as a new dash shell process is started for each script that runs from the terminal or console.

# cat /opt/bin/append-script-directory-to-path-and-start-new-shell.sh
#!/bin/sh
# Absolute path to this script, e.g. /home/user/bin/foo.sh
# echo "'$0'"
SCRIPT=$(readlink -f "$0")
# Absolute path this script is in, thus /home/user/bin
SCRIPTPATH=$(dirname "$SCRIPT")
# echo Appending to $PATH: $SCRIPTPATH
export PATH=$PATH:$SCRIPTPATH
sh

–jeroen

Posted in *nix, *nix-tools, ash/dash, ash/dash development, Development, ESXi6, ESXi6.5, ESXi6.7, ESXi7, Power User, Scripting, Software Development, Virtualization, VMware, VMware ESXi | Leave a Comment »

VMware ESXi has 2 bootbanks; with some luck the second contains your old ESXi version

Posted by jpluimers on 2021/10/19

Just in case I ever need this again:

[Wayback] VMware Knowledge Base: Reverting to a previous version of ESXi (1033604)
1. In the console screen of the ESXi host, press Ctrl+Alt+F2 to see the Direct Console User Interface (DCUI) screen.
2. Press F12 to view the shutdown options for the ESXi host.
3. Press F11 to reboot.
4. When the Hypervisor progress bar starts loading, press Shift+R. You will see the warning:
```
Current hypervisor will permanently be replaced
with build: X.X.X-XXXXXX. Are you sure? [y/n]
```
5. Press Y to roll back the build.
6. Press Enter to boot.
[Wayback] Downgrade ESXi 6.5 from update 3 to update 2 – VMware Technology Network VMTN; when out of luck:
- This is not my case.As I mentioned, I don’t have altbootbank with update 2. This is because after update 3, I also installed the latest patch.So both bootbanks now have update 3.Is there any other option for me. Can I just install update 2 again so it will overwrite everything? Or it is impossible?
- Backup ESXi configurations and reinstall it without overwriting VMFS.

Via: [Wayback/Archive.is] downgrade esxi 6.5 u3 to u2 – Google Search

–jeroen

Posted in ESXi6, ESXi6.5, ESXi6.7, ESXi7, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »

Some links to post about ESXi 6 and ESXi 7 storage and storage speed issues

Posted by jpluimers on 2021/09/09

For my link archive (most via [Wayback] sata very slow after ESXi 6.7 update – Google Search):

Thick versus thick provisioned VMDKs: [Wayback/Archive.is] Solved: ESXi 6.7 – Windows 10 Pro VM – poor disk performan… – VMware Technology Network VMTN
PERC firmware and driver versions were too old: [Wayback] Solved: ESXi 6.0U3 disk performance extremely slow – VMware Technology Network VMTN
Use VMotion to move things around: [Wayback] [SOLVED] ESXi 6.7 slow ssd read rate when moving VM – Spiceworks
GUI operations might be capped, try dd: [Wayback] datastore – How can I speed up file tranfers on local storage in vSphere 5? – Server Fault
An older Dell OpenManage Server Administrator version slowing things down: [Wayback] Performance issue with vSphere 6.7U3 on Dell servers – vInfrastructure Blog
Disable the native driver so the Lynx driver gets selected [Wayback] ESXi 6.5 Storage Performance Issues and Fix – VIRTUALIZATION IS LIFE!
- Passing through the Lynx PCIe to FreeNAS on a SuperMicro X10 based board (and showing how to list PCI devices; I use lspci | grep -E -i "SAS|SATA|SCSI|RAID|SSD" for this): [Wayback] Freenas on ESXI – AHCI Passthrough – Intel C220 Lynx Point Controller | TrueNAS Community
- Another FreeNAS passthrough of a Lynx PCIe device showing esxcli storage core adapter list to ist controllers together with drivers, then lspci -n (I tend to use lspci -v | less for this) to find which one to set to passthrough: [Wayback] Kaperschip: AHCI controller passthrough with a Supermicro Xeon-D motherboard
The stock vmw_ahci being slow,whereas the Patsburg driver isn’t (this is supposed to be fixed in ESXi 6.7): [Wayback/Archive.is] Incredibly slow disk performance – ESXi 6.5 : vmware
- [Wayback] Solved: Very slow speed on SSD – VMware Technology Network VMTN
  ESXi 6.5 includes a new native driver (vmw_ahci) for SATA AHCI controllers, but that introduces performance problems with a lot of controllers and/or disks.
  
  Try to disable the native driver and revert to the older sata-ahci driver by running
```
esxcli system module set --enabled=false --module=vmw_ahci
```
  in an ESXi shell. Reboot the host to make the change effective.
In specific situations, snapshots can make things very slow [Wayback] windows 10 1809 slow – VMware Technology Network VMTN.
Not all drivers are installed when upgrade is done through the wrong command: [Wayback] NVMe SSDs are not recognized anymore after upgrading to VMware ESXi 7 – ivobeerens.nl
- Detailed steps to fix this: [Wayback] Important – NVMe SSD not found after upgrading to ESXi 7.0
- These devices do work:
  - Samsung SSD 970 EVO 1TB NVMe
  - Samsung SSD 950 PRO 512GB NVMe
Some consumer NVMe devices no longer supported, workaround is to use the old driver (which might not work for future upgrades): [Wayback] Quick Tip – Crucial NVMe SSD not recognized by ESXi 6.7 & 7.0
Some NVMe devices (even of the same brand/type) suddenly not being visible any more: [Wayback] ESXi 6.7U2 not seeing all the NVMe, only 2 of 12 -… – VMware Technology Network VMTN
- [Wayback] Gain Optimal Performance by Changes to SSD Physical Sector Size

Two takeaways already:

“get a VMUG licence, they are not that expensive and you get to lab up all the latest software.”
when testing features (in stead of hardware support), nesting is good, though unsupported:
- [Wayback] Deploying nested ESXi is now easier than ever
- [Wayback] How I configured VLANs, VXLANs and OSPF in my nested VMware homelab – jeffreykusters.nl

–jeroen

Posted in ESXi6, ESXi6.5, ESXi6.7, ESXi7, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »

“fixing” ESXi “rsync error: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]”

Posted by jpluimers on 2021/08/30

Reminder to self: create a static ESXi binary for a recent rsync release.

Quite a few people have bumped into rsync erroring out with “large” sets of files (where large can be as low as ~1000), like for instance Tj commenting on my post “ESXi 5.1 and rsync – damiendebin.net.”:

ERROR: out of memory in receive_sums [sender] │······
rsync error: error allocating core memory buffers (code 22) at util2.c(102) [sender=3.1.1] │······
rsync: [generator] write error: Broken pipe (32) │······

I bumped into this myself as well, even when updating from rsync 3.1.0 to 3.1.2.

There are various static rsync for ESXi around. Just a few of them for completeness:

3.1.0: ESXi 5.1 and rsync – damiendebin.net. (how to download the build by Damien Debin from http://damiendebin.net and how to create the right XML firewall settings from his [Wayback] gist)

3.1.2: [Wayback] DOWNLOADS – bachmann-lan.de via [Wayback] VMware ESXi 5.1 rsync 3.0.9 statically linked binary erstellen – bachmann-lan.de

3.1.3: [Wayback/Archive.is] noelmartinon/vmtools: Tools for VMware ESXi to use in ESXi which pointed at the wrong binary link, so I archived the right one in the Wayback machine.

There is also 3.0.9 (via [Wayback] VMware ESXi 5.1 rsync 3.0.9 statically linked binary erstellen – bachmann-lan.de), but it has a VMFS bug ([Wayback] 8177 – Problems with big sparsed files) as per [Wayback] ESXi 5.1 and rsync – damiendebin.net.)

The good news is that it is fixed in 3.2.2 as a user-configurable setting, but since there is no ESXi build yet (see reminder above)…

Anyway: [Wayback] 12769 – error allocating core memory buffers (code 22) depending on source file system

Wayne Davison 2020-06-26 03:56:35 UTC

I fixed the allocation args to be size_t values (and improved a bunch of allocation error checking while I was at it).

I then added an option that lets you override this allocation sanity-check value. The default is still 1G per allocation, but you can now specify a much larger value (up to "--max-alloc=8192P-1").

If you want to make a larger value the default for your copies, export RSYNC_MAX_ALLOC in the environment with the size value of your choice.

Committed for release in 3.2.2.

This is what happens with 3.1.2 and 3.1.3:

time rsync -aiv --info=progress2 --progress --partial --existing --inplace /vmfs/volumes/Samsung850-2TB-S3D4NX0HA01043L/ Samsung850-2TB-S3D4NX0HA01043L/
sending incremental file list
              0   0%    0.00kB/s    0:00:00 (xfr#0, ir-chk=1000/1259)
ERROR: out of memory in flist_expand [sender]
rsync error: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]
Command exited with non-zero status 22
real    0m 0.87s
user    0m 0.10s
sys 0m 0.00s
time rsync -aiv --info=progress2 --progress --partial --ignore-existing --sparse /vmfs/volumes/Samsung850-2TB-S3D4NX0HA01043L/ Samsung850-2TB-S3D4NX0HA01043L/
sending incremental file list
              0   0%    0.00kB/s    0:00:00 (xfr#0, ir-chk=1000/1259)
ERROR: out of memory in flist_expand [sender]
rsync error: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]
Command exited with non-zero status 22
real    0m 0.28s
user    0m 0.12s
sys 0m 0.00s
Finished

I was lucky that [Wayback] “rsync error: error allocating core memory buffers” protocol version “3.1.2” – Google Search got me a result so quickly: add a --protocol-29 and you are set.

The first result (Wayback has the results reversed from what got) didn’t fix it. The second did.

[Wayback] 225761 – net/rsync long path causes buffer overflow (update to 3.1.3)
[Wayback/Archive.is] AIX Open Source – IBM Power Systems Community: rsync out of memory

As a work around, I added “--protocol=29” to one of our servers that was consistently failing with “ERROR: out of memory in flist_expand [receiver]” “rsync error: error allocating core memory buffers (code 22) at util2.c(105) [receiver=3.1.3]” in rsync-3.1.3-2.ppc

I read the man page and started experimenting with the protocol version until I lowered it enough to get it to work consistently.

The problem might be that running on the ESXi gives you limited memory, but then some 10k files should not use more than like half a megabyte of memory.

Sometime I will dig deeper into the protocol version differences, for now a list of files I think will be relevant for that (mainly look for protocol_version):

Some web pages mentioning the --protocol option and might give me more insight in the protocol differences:

With --protocol=29, time estimation is way off, but there are no errors:

time rsync -aiv --info=progress2 --progress --partial --existing --inplace --protocol=29 /vmfs/volumes/Samsung850-2TB-S3D4NX0HA01043L/ Samsung850-2TB-S3D4NX0HA01043L/
building file list ... 
9059 files to consider
.d..t...... isos/
         27,593   0%    0.00kB/s    0:00:06 (xfr#1, to-chk=0/9059)   

sent 212,594 bytes  received 268 bytes  20,272.57 bytes/sec
total size is 3,055,677,645,398  speedup is 14,355,204.99
real    0m 13.31s
user    0m 1.35s
sys 0m 0.00s

time /vmfs/volumes/5791a3e1-0b9368de-4965-0cc47aaa9742/local-bin/rsync -aiv --info=progress2 --progress --partial --ignore-existing --sparse --protocol=29 /vmfs/volumes/Samsung850-2TB-S3D4NX0HA01043L/ Samsung850-2TB-S3D4NX0HA01043L/
building file list ... 
9059 files to consider
>f+++++++++ isos/EN-Windows-XP-SP3-VL.iso
...
cd+++++++++ ESXi65.filesystem-root/usr/share/
216,868,164,639   7%   40.64MB/s    1:24:48 (xfr#2571, to-chk=0/9059)   

sent 216,894,938,870 bytes  received 57,858 bytes  42,582,702.80 bytes/sec
total size is 3,055,677,645,398  speedup is 14.09
real    1h 24m 58s
user    34m 5.59s
sys 0m 0.00s
Finished

Even not on ESXi, there were just a few people bumping into this, so I wonder why there are so few matches on [Wayback] “ERROR: out of memory in flist_expand [sender]” “sender=3.1” – Google Search:

RHEL rsync.x86_64 3.1.2-6.el7_6.1 [Wayback] 1751822 – rsync failing with out of memory in flist_expand (Redhat denied fix effort because “Red Hat Enterprise Linux version 7 entered the Maintenance Support 1 Phase in August 2019”)
Cygwin rsync 3.0.9:
- [Wayback] Richard Ivarson – Re: rsync ERROR: out of memory in flist_expand [sender]
- [Wayback] Bruno Galindro da Co – rsync ERROR: out of memory in flist_expand [sender]

–jeroen

Posted in *nix, *nix-tools, ash/dash development, Development, ESXi5, ESXi5.1, ESXi5.5, ESXi6, ESXi6.5, ESXi6.7, ESXi7, Power User, rsync, Scripting, Software Development, Virtualization, VMware, VMware ESXi | Leave a Comment »

ESXi: finding unmounted VMFS volumes

Posted by jpluimers on 2021/08/26

Sometimes, especially when ESXi thinks a volume is bad, but the ESXi S.M.A.R.T. logging does not indicate so, it boots without mounting some of the VMFS volumes as datastores.

It took me a while to find the right command to list those, but I’m glad I found it:

Read the rest of this entry »

Posted in ESXi6, ESXi6.5, ESXi6.7, Power User, PowerCLI, Virtualization, VMware, VMware ESXi | Leave a Comment »

The curious Kabri | How to force VMware to generate a new MAC address for a virtual machine

Posted by jpluimers on 2021/08/06

[WayBack] The curious Kabri | How to force VMware to generate a new MAC address for a virtual machine

Shut down the Guest OS.

Open up the .vmx file.
Delete the following lines (that begin with…):
ethernet0.addressType
uuid.location =
uuid.bios =
ethernet0.generatedAddress =
ethernet0.generatedAddressOffset =
Boot up the Guest OS again, and it should generate new details in the vmx file (I’d check afterwards to be doubly sure).

In my experience, start with the bold values.

If the address is the same, fiddle with ethernet0.generatedAddressOffset

Be careful with the other values, as it might force your OS to think so much hardware has changed, that license keys have become invalid.

Via: [WayBack] Re-generate MAC addresses for VMs |VMware Communities

[WayBack] Virtual machine MAC address conflicts or have a duplicate MAC Address when creating a virtual machine (1024025)

…

2>/dev/null esxcfg-info | grep -i "system uuid"

…
[WayBack] vmware esxi – Distribute VM and force new mac address – Server Fault

–jeroen

Posted in ESXi6, ESXi6.5, ESXi6.7, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »

« Previous Entries

Next Entries »

	Attila Kovacs on Crowbarring Windows 95 into Wi…
	Jeroen Wiert Pluimer… on Does Odido (the old T-Mobile N…
	Lars Fosdal on Security alarm provider Woonve…
	Thomas Mueller on Question got closed in May 202…
	Thaddy de Koning on Formulier voor bewindvoerders…

The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

Subscribe

Archives

Recent Comments

Recent Posts

Blog Stats

Meta title

Tag Cloud Title

Top Clicks

Top Posts

My badges

Twitter Updates

My Flickr Stream

Pages

All categories

Email Subscription

Archive for the ‘ESXi6.7’ Category

Some ESXi 7.x notes

ESXi 7 on ARM

ESXi 7 on x64

VFrontDe/ESXi-Customizer-PS: PowerCLI script that greatly simplifies and automates the process of creating fully patched and customized VMware ESXi installation images

Some bash parameter propagation links that hopefully will work with ash/dash too

ESXi: listing virtual machines with their IP addresses

List the `vmid` values, power status and name of all VMs

ESXi shell: appending the parent directory of a script to the path and starting a new shell, even if the script is symlinked

VMware ESXi has 2 bootbanks; with some luck the second contains your old ESXi version

Some links to post about ESXi 6 and ESXi 7 storage and storage speed issues

“fixing” ESXi “rsync error: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]”

ESXi: finding unmounted VMFS volumes

The curious Kabri | How to force VMware to generate a new MAC address for a virtual machine

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

Subscribe

Archives

Recent Comments

Recent Posts

Blog Stats

Meta title

Tag Cloud Title

Top Clicks

Top Posts

My badges

My Flickr Stream

Pages

All categories

Email Subscription

Archive for the ‘ESXi6.7’ Category

ESXi 7 on ARM

ESXi 7 on x64

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

List the vmid values, power status and name of all VMs

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

List the `vmid` values, power status and name of all VMs