 | 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… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
Posted by jpluimers on 2017/10/02
Fixed in 6.5u1: [WayBack] VM Memory Usage heuristic over-reporting on ESXi 6.5
Via: [WayBack] Incorrect memory utlization for 1 VM Web Client… |VMware Communities
Hi – After upgrading my host to ESXi 6.5 and VCSA to 6.5 I have found that one of my VM’s shows all memory being utilized in the summary screen and when
–jeroen
Posted in ESXi6.5, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »
Posted by jpluimers on 2017/10/02
Remove the “VMware Pointing Device” using “devmgmt.msc”
Somehow I have it happen every now and then on Windows (usually 8.1 x64) VMs running inside a VMware (usually Fusion) that the mouse cursor is stuck.
VMware Tools were already at the latest version and a plain reboot didn’t help.
It doesn’t matter if I was running full screen or Windows and altering these mouse settings did not change the behaviour:
Enable pointer shadowDisplay pointer trails (long or short: does not matter)I did enable Show location of pointer when I press the CTRL key which then indicated the mouse pointer was static at the screen center.
The only thing to get the mouse respond to mouse movement were these steps:
Device Manager using devmgmt.mscDevices by Connection view from the View menuW81ENTX64VS2015ACPI x64-based PCMicrosoft ACPI-Compliant SystemPCI BusIntel 82371AB/EB PCI to ISA bridge (ISA mode)VMware Pointing DeviceDevice Manager ask you to do soAfter that my mouse cursor works fine.
Just in case you bump into a similar thing, but the above steps don’t help, here are some links with different steps that might work in your situation:
Posted in Fusion, Power User, Virtualization, VMware, Windows, Windows 8.1 | Leave a Comment »
Posted by jpluimers on 2017/08/31
Anyone that knows how to edit the port groups of ESXi 6.5 Update 1 live VMs?
This worked fine in the C# based Windows vSphere Client, but not in the web-client.
When pressing Save, you get this error: Failed to reconfigure virtual machine [[vmname]]. The attempted operation cannot be performed in the current state (Powered on). - dismiss.
You have to edit because of This VM is attached to a network portgroup VM Network Fiber xs4all that doesn't exist. Edit this VM and attach it to a different network. Actions.
If seems a known issue at [Archive.is] ESXi Embedded Host Client – Bugs: #88 Error while editing a VM more than once, but it is unclear how these bugs are tracked and in which of the labs versions any of the bus are fixed ([Archive.is] @jpluimers: Hi @elesueur ! …How can we track progress at VMware Labs Flings?).
The big problem is that the vSphere Web Client is nearly covering the vSphere Windows Client, but as of VMware ESXi 6.5 update 1, the vSphere Windows Client cannot be used any more:
Screenshots:
Press
Actions, thenEdit Settings:
Press
Save:
–jeroen
Posted in ESXi6.5, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »
Posted by jpluimers on 2017/08/18
What directories to backup on ESXi apart from the VMs? – Server Fault [WayBack]:
You may want to look at purpose-built VMware backup tools. You will be very disappointed if you treat an ESXi host like a Linux/Unix server.
Use the VMware backup commands [WayBack] from a separate station, and you’ll be left with a nice configuration tarball. I would find another approach for the actual VM backups.
Edit: Host-based example
vim-cmd hostsvc/firmware/sync_config vim-cmd hostsvc/firmware/backup_configThis stores the config in
/scratch/downloads:# vim-cmd hostsvc/firmware/backup_config Bundle can be downloaded at : http://ip.of.esxi.host/downloads/52fd67ba-2fdf-9876-6651-46c3da638f1a/configBundle-centaur.ewwhite.net.tgzAlso see: http://www.virtuallyghetto.com/2013/02/how-to-backup-restore-free-esxi-host.html [WayBack]
–jeroen
Posted in ESXi5, ESXi5.1, ESXi5.5, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »
Posted by jpluimers on 2017/05/19
Boy, I totally forgot to post this. It runs also ESXi 5.x; I’ve not tried more recent ESXi versions as they just run fine.
As a follow-up on [WayBack] VMware Communities: ESX 3.5 Whitebox on HP xw6600 …, I have installed ESXi 4.0.0.Update01-208167 on a HP XW6600 workstation.
Good news: the generic ESXi 4 installation works, whereas the HP specific ESXi 4 fails (you get a nice purple screen of death).
[WayBack] http://www.vm-help.com//esx40i/esx40_whitebox_HCL.php
–jeroen
Posted in ESXi4, ESXi5, ESXi5.1, ESXi5.5, Hardware, HP XW6600, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »
Posted by jpluimers on 2017/04/20
Note this works only when the VMs have VMware Tools installed (more on that below):
VMWare provides, not surprisingly, a built in tool for this, vmrun. It’s under
/Applications/VMware Fusion.app/Contents/Library/vmrunalthough it has moved around in other Fusion releases a bit.
🍺 vmrun list Total running VMs: 1 .docker/machine/machines/myvm.vmx
🍺 vmrun getGuestIPAddress ~/.docker/machine/machines/myvm.vmx 172.16.213.128
via: How do I find the IP address of a virtual machine using VMware Fusion? – Super User [WayBack]
vmrun [WayBack] is barely documented and most of is in PDF of which this is the most recent I could find: www.vmware.com/pdf/vix180_vmrun_command.pdf [WayBack]
Based on the above path, I added this to my ~/.bash_profile file:
alias vmrun='/Applications/VMware\ Fusion.app/Contents/Library/vmrun'
alias vmrun-list-running-VMs='vmrun list | grep vmx'
vmrun-list-ipv4-of-running-VMs()
{
vmrun-list-running-VMs | while read line ; do echo $line && vmrun getGuestIPAddress $line; done
}
Now I can do this:
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
/Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
Error: The VMware Tools are not running in the virtual machine: /Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
172.16.172.134
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
172.16.172.134
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.142
These are the messages I observed:
Error: The VMware Tools are not running in the virtual machine: /Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address
172.16.172.135
The first one means a machine is running but has no VMware Tools installed. For an OpenSuSE machine you can install it with zypper install open-vm-tools, for other Linux systems read VMware Tools auf Ubuntu, Mint, CentOS oder openSUSE installieren | ITrig [WayBack]
Some more examples of vmrun for VMware Fusion are at Control VMware Fusion from the Command Line | James Reuben Knowles [WayBack]
–jeroen
Posted in *nix, bash, Development, Fusion, openSuSE, Power User, Scripting, Software Development, SuSE Linux, Tumbleweed, Virtualization, VMware | Leave a Comment »
Posted by jpluimers on 2016/11/11
To grow you must first change the size of the container: the partition, the LV, or arraydevice. Then you can resize the file system. It’s the same with XFS, and NTFS. I’m only aware of Apple’sdiskutil resizevolume command that resizes the flavors of HFS+ and at the same time sets the new end valuefor the partition entry.
Source: Development of the BTRFS linux file system (not yet archived at the WayBack machine)
I will need the above for a single disk device having a BTRFS partition sandwiched between a swap and xfs partition:
# parted -l Model: VMware Virtual disk (scsi) Disk /dev/sda: 21.5GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 1562MB 1561MB primary linux-swap(v1) type=82 2 1562MB 17.7GB 16.1GB primary btrfs boot, type=83 3 17.7GB 21.5GB 3799MB primary xfs type=83
I’ll likekly be:
I might be able to do all this from the gparted live CD as moving xfs and growing btrfs is on the GParted — Features list.
Fingers crossed. Luckily I’ve backups (:
–jeroen
Posted in *nix, ESXi4, ESXi5, ESXi5.1, ESXi5.5, ESXi6, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed, VMware, VMware ESXi | Leave a Comment »
Posted by jpluimers on 2016/10/31
On my research list: Determine TBW from SSDs with S.M.A.R.T Values in ESXi (smartctl) | Virten.net
Via Matthijs ter Woord.
–jeroen
Posted in ESXi6, Power User, Virtualization, VMware, VMware ESXi | 1 Comment »
Posted by jpluimers on 2016/10/21
Not sure why yet, but on a gigabit network between a Windows 2008 R2 Server and a Proxmox KVM machine, WinSCP gets around 10 megabit/second and FileZilla > 30 megabit/second.
Others seem to agree that filezilla faster than winscp.
–jeroen
Posted in Communications Development, Development, Internet protocol suite, Power User, Proxmox, SSH, TCP, Virtualization, VMware, Windows, Windows Server 2008, Windows Server 2008 R2 | 1 Comment »
Posted by jpluimers on 2016/10/17
There are various places that tell you you cannot resize a thick disk to a thin disk using vmkfstools.
When you do it wrong, you get this error:
DiskLib_Check() failed for source disk. The file specified is not a virtual disk (15).
This happens when you directly try to resize the physical disk image:
# vmkfstools --clonevirtualdisk msmxp-flat.vmdk --diskformat thin msmxp-flat.thin.vmdk DiskLib_Check() failed for source disk The file specified is not a virtual disk (15).
Whereas you should point vmkfstools to the disk descriptor file which has the shortest name:
# vmkfstools --clonevirtualdisk msmxp.vmdk --diskformat thin msmxp.thin.vmdk Destination disk format: VMFS thin-provisioned Cloning disk 'msmxp.vmdk'... Clone: 100% done.
(Note that many people shorten the --clonevirtualdisk to -i and --diskformat to -d).
For performance, it doesn’t matter much if your disk is thick or thin as explained by Death to false myths: The type of virtual disk used determines your performance.
But various people issues expanding a thick disk. With thin disks, that usually works fine.
This post explains the correct steps of resizing: VMWare ESXi 5.1–convert virtual disk (vmdk) from thick to thin provision.
For instance with rsync is great for making a local backup:
# time ./850EVO1TBR1B/bin/rsync -aiv --info=progress2 --progress ./850EVO1TBR1B/Raid6SSD-VM/msmxp/ ./850EVO1TBR1A/Raid6SSD-VM/msmxp/
/vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # du -h *.vmdk 12.0G msmxp-flat.vmdk 0 msmxp.vmdk
There are two: msmxp.vmdk describes the disk and msmxp-flat.vmdk has the data.
# ls -al /vmfs/volumes | grep "552f5788-33e30274-8dba-001f29022aed" drwxr-xr-t 1 root root 2660 Aug 5 04:35 552f5788-33e30274-8dba-001f29022aed lrwxr-xr-x 1 root root 35 Aug 5 06:11 850EVO1TBR1B -> 552f5788-33e30274-8dba-001f29022aed # df -h | grep "850EVO1TBR1B\|Use%" Filesystem Size Used Available Use% Mounted on VMFS-5 930.8G 736.8G 194.0G 79% /vmfs/volumes/850EVO1TBR1B
# vmkfstools --clonevirtualdisk msmxp.vmdk --diskformat thin msmxp.thin.vmdk Destination disk format: VMFS thin-provisioned Cloning disk 'msmxp.vmdk'... Clone: 100% done.
In my case the flat disk was almost full and fragmented, so the thin disk is not smaller:
/vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # du -h *.vmdk 12.0G msmxp-flat.vmdk 12.0G msmxp.thin-flat.vmdk 0 msmxp.thin.vmdk 0 msmxp.vmdk
Use vmkfstools (do not use mv as that will not keep the descriptor/data vmdk files bound together) and check the rename.
You can replace --renamevirtualdisk with -E:
/vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --renamevirtualdisk msmxp.thin.vmdk msmxp.vmdk ## /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools -E msmxp.vmdk msmxp.thick.vmdk /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # du -h *.vmdk 12.0G msmxp-flat.vmdk 12.0G msmxp.thick-flat.vmdk 0 msmxp.thick.vmdk 0 msmxp.vmdk
If it does, then delete it (you can replace --deletevirtualdisk with -U) which will remove both both the descriptor and data vmdk file:
/vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --deletevirtualdisk msmxp.vmdk ## /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools -U msmxp.vmdk /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # du -h *.vmdk 12.0G msmxp-flat.vmdk 0 msmxp.vmdk
After shutting down the VM again and making a new backup, you can now expand the disk as described in VMware KB: Adding space to an ESXi/ESX host virtual disk.
You can replace --extendvirtualdisk with -X.
/vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --extendvirtualdisk 14G msmxp.vmdk ## /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools -X 14G msmxp.vmdk Grow: 100% done. /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # du -h *.vmdk 12.0G msmxp-flat.vmdk 0 msmxp.vmdk /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --renamevirtualdisk msmxp.vmdk msmxp.thick.vmdk /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --clonevirtualdisk msmxp.thick.vmdk msmxp.vmdk --diskformat thin Destination disk format: VMFS thin-provisioned Cloning disk 'msmxp.thick.vmdk'... Clone: 100% done. /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # diff msmxp.thick.vmdk msmxp.vmdk --- msmxp.thick.vmdk +++ msmxp.vmdk @@ -7,18 +7,18 @@ createType="vmfs" # Extent description -RW 29360128 VMFS "msmxp.thick-flat.vmdk" +RW 29360128 VMFS "msmxp-flat.vmdk" # The Disk Data Base #DDB -ddb.adapterType = "ide" -ddb.thinProvisioned = "1" -ddb.geometry.sectors = "63" -ddb.geometry.heads = "16" -ddb.geometry.cylinders = "29127" -ddb.uuid = "60 00 C2 9f 5e f8 33 76-6e c5 48 3c f2 84 d8 1e" -ddb.longContentID = "5659579edebed2ebdd8e0c8fda15abd4" ddb.toolsVersion = "9221" ddb.virtualHWVersion = "8" ddb.deletable = "true" +ddb.longContentID = "5659579edebed2ebdd8e0c8fda15abd4" +ddb.uuid = "60 00 C2 95 66 1b cf 7a-e3 db 3f 30 17 7e 00 2d" +ddb.geometry.cylinders = "29127" +ddb.geometry.heads = "16" +ddb.geometry.sectors = "63" +ddb.thinProvisioned = "1" +ddb.adapterType = "ide" /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # du -h *.vmdk 12.0G msmxp-flat.vmdk 12.0G msmxp.thick-flat.vmdk 0 msmxp.thick.vmdk 0 msmxp.vmdk /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --extendvirtualdisk 14G msmxp.vmdk Failed to extend disk : One of the parameters supplied is invalid (1). /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --extendvirtualdisk 14G msmxp.vmdk Failed to extend disk : One of the parameters supplied is invalid (1). /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --extendvirtualdisk 14G msmxp.vmdk Failed to extend disk : One of the parameters supplied is invalid (1). /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --extendvirtualdisk 15G msmxp.vmdk Grow: 100% done. /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # du -h *.vmdk 12.0G msmxp-flat.vmdk 12.0G msmxp.thick-flat.vmdk 0 msmxp.thick.vmdk 0 msmxp.vmdk /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # vmkfstools --deletevirtualdisk msmxp.thick.vmdk /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp # du -h *.vmdk 12.0G msmxp-flat.vmdk 0 msmxp.vmdk /vmfs/volumes/552f5788-33e30274-8dba-001f29022aed/Raid6SSD-VM/msmxp #
–jeroen
via: vmware esxi – vmkfstools returns error when trying to copy thin vmdk – Server Fault.
Posted in ESXi4, ESXi5, ESXi5.1, ESXi5.5, ESXi6, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »
The Wiert Corner - irregular stream of stuff 