April 2021
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	29	30

Archive for April, 2021

VMware ESXi console: viewing all VMs, suspending and waking them up: part 5

Posted by jpluimers on 2021/04/30

Yesterday’s post got a bit longer than anticipated as there were most steps than I hoped for to create 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

This means that today there is a new try to cover the rest of these lists I started yesterday with:

Available commands

vim-cmd vmsvc/power.getstate vmid

vim-cmd vmsvc/power.hibernate vmid

vim-cmd vmsvc/power.off vmid

vim-cmd vmsvc/power.on vmid

vim-cmd vmsvc/power.reboot vmid

vim-cmd vmsvc/power.reset vmid

vim-cmd vmsvc/power.shutdown vmid

vim-cmd vmsvc/power.suspend vmid

vim-cmd vmsvc/power.suspendResume vmid

Unavailable commands

vim-cmd vmsvc/power.startup vmid

vim-cmd vmsvc/power.resume vmid

vim-cmd vmsvc/power.wakeup vmid

So here we go:

`vim-cmd-hibernate-running-VMs.sh` and `vim-cmd-suspend-running-VMs.sh`

These files are almost the same: the echo and command are different (Hibernating versus Suspending and power.hibernate versus suspend)

#!/bin/sh
# https://wiert.me/2021/04/30/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-5/
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})."
    if [ "${powerState}" == "Powered on" ] ; then
        echo "Powered on  VM with id ${vmid} and name: $name"
        echo "Hibernating VM with id ${vmid} and name: $name"
        vim-cmd vmsvc/power.hibernate ${vmid}
    fi
done

This hibernates all VMs with power state Powered on and waits for each VM to complete hibernation.

#!/bin/sh
# https://wiert.me/2021/04/30/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-5/
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})."
    if [ "${powerState}" == "Powered on" ] ; then
        echo "Powered on VM with id ${vmid} and name: $name"
        echo "Suspending VM with id ${vmid} and name: $name"
        vim-cmd vmsvc/power.suspend ${vmid}
    fi
done

This suspends all VMs with power state Powered on and waits for each VM to complete suspending.

`vim-cmd-resume-suspended-VMs.sh` and `vim-cmd-wakeup-suspended-VMs.sh`

#!/bin/sh
# https://wiert.me/2021/04/30/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-5/
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})."
    if [ "${powerState}" == "Suspended" ] ; then
        echo "Suspended VM with id ${vmid} and name: $name"
        echo "Resuming  VM with id ${vmid} and name: $name"
        vim-cmd vmsvc/power.on ${vmid}
    fi
done

This resumes (as there is no vim-cmd vmsvc/power.resume vmid) all VMs with power state Suspended and waits for each VM to complete resume.

`vim-cmd-power-off-powered-on-VMs.sh`

#!/bin/sh
# https://wiert.me/2021/04/30/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-5/
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})."
    if [ "${powerState}" == "Powered on" ] ; then
        echo "Powered on   VM with id ${vmid} and name: $name"
        echo "Powering off VM with id ${vmid} and name: $name"
        vim-cmd vmsvc/power.off ${vmid}
    fi
done

This powers off all VMs with power state Power on and waits for each VM to start powering off (but does not wait for them to complete powering off, so parts run in parallel).

`vim-cmd-power-on-powered-off-VMs.sh`, `vim-cmd-power-on-shutdown-VMs.sh` and `vim-cmd-startup-shutdown-VMs.sh`

#!/bin/sh
# https://wiert.me/2021/04/30/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-5/
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})."
    if [ "${powerState}" == "Powered off" ] ; then
        echo "Powered off VM with id ${vmid} and name: $name"
        echo "Powering on VM with id ${vmid} and name: $name"
        vim-cmd vmsvc/power.on ${vmid}
    fi
done

These powers on all VMs with power state Powered off and waits for each VM to complete power on (but does not wait for them to complete boot, so part runs in parallel!).

These are exactly the same, as you cannot distinguish a VM that has been shutdown by vim-cmd vmsvc/power.off vmid from vim-cmd vmsvc/shutdown vmid.

`vim-cmd-reboot-powered-on-VMs.sh`

#!/bin/sh
# https://wiert.me/2021/04/30/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-5/
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})."
    if [ "${powerState}" == "Powered on" ] ; then
        echo "Powered on VM with id ${vmid} and name: $name"
        echo "Rebooting  VM with id ${vmid} and name: $name"
        vim-cmd vmsvc/power.reboot ${vmid}
    fi
done

This reboots all VMs with power state Power on and waits for each VM to start rebooting (but does not wait for them to complete reboot, so parts run in parallel).

`vim-cmd-reset-powered-on-VMs.sh`

#!/bin/sh
# https://wiert.me/2021/04/30/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-5/
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})."
    if [ "${powerState}" == "Powered on" ] ; then
        echo "Powered on VM with id ${vmid} and name: $name"
        echo "Resetting  VM with id ${vmid} and name: $name"
        vim-cmd vmsvc/power.reset ${vmid}
    fi
done

This resets all VMs with power state Power on and waits for each VM to start rebooting (but does not wait for them to complete reboot, so parts run in parallel).

`vim-cmd-suspendResume-powered-on-VMs.sh`

#!/bin/sh
# https://wiert.me/2021/04/30/vmware-esxi-console-viewing-all-vms-suspending-and-waking-them-up-part-5/
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})."
    if [ "${powerState}" == "Powered on" ] ; then
        echo "Powered on      VM with id ${vmid} and name: $name"
        echo "SuspendResuming VM with id ${vmid} and name: $name"
        vim-cmd vmsvc/power.suspendResume ${vmid}
    fi
done

This suspends and resumes on all VMs with power state Power on and waits for each VM to start this shirt cycle (but does not wait for them to complete the suspend and resume cycle, so parts run in parallel).

Future episodes

For now, this is OK enough for me, but I might write a new installment trying to run more of these in parallel (as parts already are done on the ESXi side).

–jeroen

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

Mac SE/30 recap links

Posted by jpluimers on 2021/04/30

Some links for my archive:

Via:

–jeroen

Read the rest of this entry »

Posted in Apple, Classic Macintosh, Macintosh SE/30, Power User | Leave a Comment »

AstraZeneca: tweede prik gaat gewoon door (via Rijksoverheid.nl)

Posted by jpluimers on 2021/04/30

Via [Archive.is] NicolettevCronenburg on Twitter: “Ik schrok van je bericht. Je moet gewoon de 2e prik kunnen krijgen volgens het advies van de Gezondheidsraad: … “:
- [Wayback] Wat moet ik weten over vaccinatie met het AstraZeneca-vaccin? | Rijksoverheid.nl
  
  Ik heb al 1 prik met AstraZeneca gehad
  
  Hoe gaat het nu verder met mijn 2e prik?
  
  Alle mensen die al een 1e prik met AstraZeneca hebben gehad, krijgen ook hun 2e prik met AstraZeneca. Het geboortejaar maakt hierbij niet uit. Dat is ook het advies van de Gezondheidsraad.
- [Archive.is] NicolettevCronenburg on Twitter: “:-(, niet OK dit. Ik neem voor mijn 2e prik dan maar een kopie van deze regel mee voor de zekerheid. Wil je deze groep met 1 prik voldoende bescherming bieden, dan is die 2e gewoon nodig! @rivm @Gezondheidsraad…”
[Archive.is] Jeroen Wiert Pluimers on Twitter: “Ik hoor van de collega van Eega dat mensen bij de GGD worden weggestuurd die voor hun 2e prik AstraZeneca komen, tegen het advies van de Gezondheidsraad in: … “De Gezondheidsraad adviseert verder dat mensen geboren na 1960 die al een eerste vaccinatie 1/”
- [Wayback] Inzet AstraZeneca-vaccin | Advies | Gezondheidsraad
  
  Inzet AstraZeneca-vaccin
  
  …
  
  Mensen onder de 60 die al een eerste prik met het AstraZeneca-vaccin hebben gehad, kunnen wel hun tweede dosis vaccin toegediend krijgen. Er zijn tot op heden wereldwijd geen meldingen van de bijwerking na de tweede dosis, terwijl wereldwijd al enkele miljoenen mensen een tweede dosis vaccin hebben ontvangen.
[Archive.is] Jeroen Wiert Pluimers on Twitter: “met AstraZeneca hebben gekregen, de afspraak voor de tweede prik met AstraZeneca kunnen laten doorgaan.” en … “Mensen onder de 60 die al een eerste prik met het AstraZeneca-vaccin hebben gehad, kunnen wel hun tweede dosis vaccin toegediend krijgen.” 2/”
- [Wayback] Prikken met AstraZeneca voor mensen van 60 jaar en ouder gaat door | RIVM
  
  De Gezondheidsraad adviseert verder dat mensen geboren na 1960 die al een eerste vaccinatie met AstraZeneca hebben gekregen, de afspraak voor de tweede prik met AstraZeneca kunnen laten doorgaan.

Posted in About, LifeHacker, Personal, Power User | Leave a Comment »

Celebrate Email Debt Forgiveness Day!

Posted by jpluimers on 2021/04/30

If there’s an email response you’ve wanted to send but been too anxious to send, you can send it today

[Wayback] Celebrate Email Debt Forgiveness Day! | Email Debt Forgiveness Day

Via: [Archive.is] Ionica Smeets on Twitter: “Voor wie net als ik nog wat achterstallige mails heeft: komende vrijdag is het email debt forgiveness day”

–jeroen

Read the rest of this entry »

Posted in LifeHacker, Power User | Leave a Comment »

Thoughts on ix500; should I get an ix1500?

Posted by jpluimers on 2021/04/30

Some of my thoughts on [WayBack] AW: Netzwerkfähiger Dokumentenscanner?:

I use a Fujitsu ScanSnap ix500 scanner for this plus a Windows VM that automatically logs on.

Pictures: https://commons.wikimedia.org/wiki/C…ScanSnap_iX500

Blog posts: https://wiert.me/category/power-user…cansnap/ix500/

Heise https://www.google.com/search?q=ix500+site%3Aheise.de

It is out of production now, but I think most of the below holds as the successor ix1500 is very similar (ix500 announcement https://www.fujitsu.com/sg/about/res…-20181002.html)

Before the ix500, I used a Fujitsu ScanSnap S510 which had similar capabilities as the ix500 but was a lot slower.

Cool things:

included software can do OCR and scan to a path the Windows user has access to

the scanner is fast, and does a stack of A4 full duplex automatically at a few seconds per page scanning on the scanner and 5-10 seconds per page OCR on a 1.2 Ghz dual core VM

no fiddling from within the scanner to get network stuff working, or to keep it up-to-date on protocol changes

Drawbacks:

the software pops up a dialog after each scan, so I wrote this: https://bitbucket.org/jeroenp/wiert….onsoleProject/

you need a Windows PC that is logged on (so the software does work), which means I configured a VM to auto-logon

WiFi 2.4 Ghz only (no ethernet interface, no 5 Ghz WiFi)

you need USB on the same VM connected to the scanner once to configure WiFI

like any hardware/software combination, sometimes the scanner or Windows VM need a reboot, for instance when it looses network or USB connection

The ix1500 has a touch screen instead of 2 buttons, so it might be that it has more standalone functionalities than the ix500.

Since I need a second scanner in a second place, I might get an ix1500 after the summer.

–jeroen

–jeroen

Posted in Fujitsu ScanSnap, Hardware, ix500, LifeHacker, Power User, Scanners | Leave a Comment »

VMware ESXi console: viewing all VMs, suspending and waking them up: part 4

Posted by jpluimers on 2021/04/29

Yesterday we ended with an overview of available and unavailable vim-cmd vmsvc commands and the promise to try running the various power commands on all relevant VMs.

Let’s start with a summary of the commands, so it will be easier to make a list of scripts to run them on relevant VMs.

Available commands

vim-cmd vmsvc/power.getstate vmid
vim-cmd vmsvc/power.hibernate vmid
vim-cmd vmsvc/power.off vmid
vim-cmd vmsvc/power.on vmid
vim-cmd vmsvc/power.reboot vmid
vim-cmd vmsvc/power.reset vmid
vim-cmd vmsvc/power.shutdown vmid
vim-cmd vmsvc/power.suspend vmid
vim-cmd vmsvc/power.suspendResume vmid

Unavailable commands

vim-cmd vmsvc/power.startup vmid
vim-cmd vmsvc/power.resume vmid
vim-cmd vmsvc/power.wakeup vmid

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

Getting the `vmid`

Yesterday I showed a small statement that gives the list of vmid values on an ESXi system:

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"

What I ideally want is not just the vmid and name for each VM from vim-cmd vmsvc/getallvms, but also get the power state information from vim-cmd vmsvc/power.getstate vmid.

For that, we need to parse the output of vim-cmd vmsvc/power.getstate vmid, which can be three outputs:

Retrieved runtime info Powered off
Retrieved runtime info Powered on
Retrieved runtime info Suspended

So basically it involves deleting the first line which was covered in part 2 of this installment, for example on my system:

# vim-cmd vmsvc/power.getstate 10 | sed '1d'
Powered on

Getting VM `name`

Extracting both vmid and name from vim-cmd vmsvc/getallvms at the same time is not easy, heck even impossible, so I decided to go the vim-cmd vmsvc/get.config vmid way.

Getting multiple values out of some output is already very hard in bash, where usually the less difficult way is to use arrays. Since Busybox has an ash shell (see Busybox sh (actually ash derivative dash): checking exit codes), and ash does not do arrays, that route is gone.

To give you an idea how hard this is in bash and how to sort of workaround the lack of array support in ash:

[Wayback] shell – How to assign values to multiple variables in command line with bars – Unix & Linux Stack Exchange (explaining how to do this with multiple assignments)

[Wayback] bash – Extract two values from the output of a command – Unix & Linux Stack Exchange (explaining how to use tee to pass output to multiple distinct commands)

[Wayback] linux – Extract multiple values using sed – Stack Overflow (how to use sed to split output over multiple lines)

[Wayback] linux – how to get elements from list in bash? – Super User (on the bash array syntax)

[Wayback] linux – reading a tuple from a file with awk – Stack Overflow (on how to use multiple arrays in bash)

[Wayback] shell – How to port to bash-style arrays to ash? – Unix & Linux Stack Exchange (explaining that unlike bash, ash has no arrays)

This partial vim-cmd vmsvc/get.config vmid sample output on one of my VMs that shows how to use head -n 31 to get just the first 31 lines of output:

# vim-cmd vmsvc/get.config 10 | head -n 31
Configuration:

(vim.vm.ConfigInfo) {
   changeVersion = "2021-04-07T22:08:30.548274Z", 
   modified = "1970-01-01T00:00:00Z", 
   name = "X9SRI-3F-W10P-EN-MEDIA", 
   guestFullName = "Microsoft Windows 10 (64-bit)", 
   version = "vmx-14", 
   uuid = "564d51ac-f6cf-e40b-b686-2f53a28a4bea", 
   createDate = "2019-05-17T21:37:11.408173Z", 
   instanceUuid = "52403d0e-7ccd-48da-bb21-7e966defccf7", 
   npivNodeWorldWideName = , 
   npivPortWorldWideName = , 
   npivWorldWideNameType = , 
   npivDesiredNodeWwns = , 
   npivDesiredPortWwns = , 
   npivTemporaryDisabled = true, 
   npivOnNonRdmDisks = , 
   locationId = "564d6b18-ecd1-2261-0127-146b3f3bc636", 
   template = false, 
   guestId = "windows9_64Guest", 
   alternateGuestName = "", 
   annotation = "", 
   files = (vim.vm.FileInfo) {
      vmPathName = "[EVO860_500GB] VM/X9SRI-3F-W10P-EN-MEDIA/X9SRI-3F-W10P-EN-MEDIA.vmx", 
      snapshotDirectory = "[EVO860_500GB] VM/X9SRI-3F-W10P-EN-MEDIA", 
      suspendDirectory = "[EVO860_500GB] VM/X9SRI-3F-W10P-EN-MEDIA", 
      logDirectory = "[EVO860_500GB] VM/X9SRI-3F-W10P-EN-MEDIA", 
      ftMetadataDirectory = 
   }, 
   tools = (vim.vm.ToolsConfigInfo) {

The reason to go the vim-cmd vmsvc/get.config vmid way is that it contains all the configuration info in a kind of JSON format (except the first two lines) and should be relatively easy to parse. Or so at least I hoped.

Basically I am interested in the value of name = "X9SRI-3F-W10P-EN-MEDIA", however, there are multiple name fields in the total configuration:

# vim-cmd vmsvc/get.config 10 | sed -n -E '/name =/p'
   name = "X9SRI-3F-W10P-EN-MEDIA", 
         name = "EVO860_500GB",

So what I really want is the value of name = "X9SRI-3F-W10P-EN-MEDIA", in between the (vim.vm.ConfigInfo) { and files = (vim.vm.FileInfo) { parts.

This can be done using sed as it allows to specify a range using a start and end value using addresses:

[Wayback] sed: Addresses in sed
An address is either a decimal number that counts input lines cumulatively across files, a '$' character that addresses the last line of input, or a context address (which consists of a BRE, as described in Regular Expressions in sed , preceded and followed by a delimiter, usually a slash).

An editing command with no addresses shall select every pattern space.

An editing command with one address shall select each pattern space that matches the address.

An editing command with two addresses shall select the inclusive range from the first pattern space that matches the first address through the next pattern space that matches the second. (If the second address is a number less than or equal to the line number first selected, only one line shall be selected.) Starting at the first line following the selected range, sed shall look again for the first address. Thereafter, the process shall be repeated. Omitting either or both of the address components in the following form produces undefined results:
```
[address[,address]]
```
Range Addresses (sed, a stream editor)[Wayback] Range Addresses (sed, a stream editor)
An address range can be specified by specifying two addresses separated by a comma (,). An address range matches lines starting from where the first address matches, and continues until the second address matches (inclusively):
```
$ seq 10 | sed -n '4,6p'
4
5
6
```
If the second address is a regexp, then checking for the ending match will start with the line following the line which matched the first address: a range will always span at least two lines (except of course if the input stream ends).

…
[Wayback] Regexp Addresses (sed, a stream editor)

For example (with some characters escaped because of [Wayback] ERE syntax (sed, a stream editor)):

# vim-cmd vmsvc/get.config 10 | sed -n -E -e '/\(vim.vm.ConfigInfo\) \{/,/files = \(vim.vm.FileInfo\) \{/p'
(vim.vm.ConfigInfo) {
   changeVersion = "2021-04-07T22:08:30.548274Z", 
   modified = "1970-01-01T00:00:00Z", 
   name = "X9SRI-3F-W10P-EN-MEDIA", 
   guestFullName = "Microsoft Windows 10 (64-bit)", 
   version = "vmx-14", 
   uuid = "564d51ac-f6cf-e40b-b686-2f53a28a4bea", 
   createDate = "2019-05-17T21:37:11.408173Z", 
   instanceUuid = "52403d0e-7ccd-48da-bb21-7e966defccf7", 
   npivNodeWorldWideName = , 
   npivPortWorldWideName = , 
   npivWorldWideNameType = , 
   npivDesiredNodeWwns = , 
   npivDesiredPortWwns = , 
   npivTemporaryDisabled = true, 
   npivOnNonRdmDisks = , 
   locationId = "564d6b18-ecd1-2261-0127-146b3f3bc636", 
   template = false, 
   guestId = "windows9_64Guest", 
   alternateGuestName = "", 
   annotation = "", 
   files = (vim.vm.FileInfo) {

With [Wayback] BRE syntax (sed, a stream editor) the filter part would be easier: vim-cmd vmsvc/get.config 10 | sed -n -e '/(vim.vm.ConfigInfo) {/,/files = (vim.vm.FileInfo) {/p', but the print part would be more difficult:

# vim-cmd vmsvc/get.config 10 | sed -n -E -e '/\(vim.vm.ConfigInfo\) \{/,/files = \(vim.vm.FileInfo\) \{/ s/^ +name = "(.*)",.*?/1/p'
X9SRI-3F-W10P-EN-MEDIA

# vim-cmd vmsvc/get.config 10 | sed -n -e '/(vim.vm.ConfigInfo) {/,/files = (vim.vm.FileInfo) {/ s/^ +name = "(.*)",.*?/1/p'
X9SRI-3F-W10P-EN-MEDIA

Since I am used to extended regular expressions (ERE) over basica regular expressions (BRE), I prefer the first solution.

So getting the name in a variable now becomes this:

# name=`vim-cmd vmsvc/get.config 10 | sed -n -e '/(vim.vm.ConfigInfo) {/,/files = (vim.vm.FileInfo) {/ s/^ +name = "(.*)",.*?/1/p'`
# echo ${name}
X9SRI-3F-W10P-EN-MEDIA

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

As a bonus, next to powerState, the script also figures out vmPathName in a similar way to name.

–jeroen

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

Huurprijswijzigingen die voor 1 juli 2021 ingaan berekenen

Posted by jpluimers on 2021/04/29

Voor mijn link-archief:

[Wayback/Archive.is] Huurverhoging in 2021 | Passende huur | Woningmarktbeleid

Verhuurders sturen meestal in april de jaarlijkse brief aan hun huurder(s) over de huurverhoging die per 1 juli ingaat. Maar de huurverhoging kan ook op een andere datum ingaan.
[Wayback/Archive.is] Wat is de maximale huurverhoging in 2021? | Rijksoverheid.nl

Vanaf 1 juli 2021 gaat de huur voor een sociale huurwoning niet omhoog. Ook de huur voor mensen met een hoger inkomen gaat niet omhoog. Dit geldt tot 30 juni 2022. Huurt u in een vrijesectorwoning? Dan geldt er géén maximum huurverhoging.
[Wayback/Archive.is] Welke regels gelden er voor een huurverhoging? | Rijksoverheid.nl

U woont in een sociale huurwoning. Dan kan uw verhuurder elk jaar uw huur verhogen. De Rijksoverheid bepaalt met hoeveel procent. Let op: vanaf 1 juli 2021 mag uw verhuurder de huur niet verhogen. Dit geldt tot 30 juni 2022. Huurt u een vrijesectorwoning? Dan geldt er geen maximale huurverhoging. Dit verandert misschien in 2021.
[Wayback/Archive.is] Wat is het verschil tussen een sociale huurwoning en een huurwoning in de vrije sector? | Rijksoverheid.nl

Een sociale huurwoning kent een begrensde huur. De huur mag nooit hoger zijn dan een bepaald bedrag. Dit heet de maximale huurgrens van de woning. Ook mag de huurverhoging nooit te hoog zijn. In de vrije sector gelden deze regels niet.
[Wayback/Archive.is] Hoe hoog is de inflatie van de consumentenprijzen (CPI is consumentenprijsindex)?
[Wayback/Archive.is] Bereken huurverhoging vrije sector huurwoning of bedrijfspand

Bereken de jaarlijkse huurverhoging van uw vrije sector huurwoning volgens de consumentenprijsindex (CPI) van het Centraal Bureau voor de Statistiek. Dit wordt ook wel de indexering van de huur genoemd.
[Archive.is] StatLine – Consumentenprijzen; prijsindex 2015=100
[Archive.is] StatLine – Consumentenprijzen; prijsindex 2015=100
[Archive.is] StatLine – Consumentenprijzen; prijsindex 2015=100

–jeroen

Posted in About, Personal | Leave a Comment »

Some links on Delphi and CHM help files

Posted by jpluimers on 2021/04/29

I hardly use help files, but some older systems do, and when porting really old Delphi code, often odd implementations of accessing them through HHCTRL.OCX are used.

Since I tend to forget the correct way using the HtmlHelpViewer unit, here are some links:

Very old code involving the OCX file:

Quote from the first link [WayBack] How to Connect HTML Help with your Delphi Application:

Linking HTML Help (CHM) Files

You should add the “HTMLHelpViewer” unit to the “Uses” clause in the main form of your application. Then set the full path to your CHM file to Application.HelpFile property. To do so, you can add the following line to the main form’s “On Create” event handler:
Application.HelpFile := ExtractFilePath(Application.ExeName) + 'HelpFile.chm';
where “HelpFile.chm” is the actual name of your HTML Help file, located in the same directory as your application’s executable file.

Using HTML Help from Code

When you need to display your help file or a specific help topic, or perform others actions, you can use the following calls:

Displaying a help topic
Application.HelpContext(IDH_TOPIC);
where IDH_TOPIC is the ContextId value of the topic to display.

Displaying the Table of Contents tab
HtmlHelp(0, Application.HelpFile, HH_DISPLAY_TOC, 0);
Displaying the Index tab
HtmlHelp(0, Application.HelpFile, HH_DISPLAY_INDEX, DWORD(PWideChar('Test')));
Displaying the Search tab
var
  Query: THH_Fts_QueryW;
begin
  with Query do
  begin
    cbStruct := SizeOf(THH_Fts_QueryW);
    fUniCodeStrings := True;
    pszSearchQuery := '';
    iProximity := 0;
    fStemmedSearch := True;
    fTitleOnly := False;
    fExecute := True;
    pszWindow := nil;
  end;
  HtmlHelp(0, Application.HelpFile, HH_DISPLAY_SEARCH, DWORD(@Query));
end;
Performing Keyword Lookup
Application.HelpKeyword('Test');
Providing Help for Controls

You can link specific help topics with any controls located on the form. In this case a control will automatically display the corresponding help topic when the user focuses it and presses F1. Also, you can add the standard [?] button to the caption area of the form: using the Object Inspector, set the form’s BorderStyle property as bsDialog and biHelp member of the BorderIcons property to True. Then set the controls’ HelpContext properties that should correspond to the topic ContextId values as defined in your help project.

–jeroen

Read the rest of this entry »

Posted in Delphi, Development, Software Development | Leave a Comment »

VMware ESXi console: viewing all VMs, suspending and waking them up: part 3

Posted by jpluimers on 2021/04/28

Yesterday’s installment ended with a list of power related vim-cmd vmsvc commands:

Usage: power.getstate vmid
Usage: power.hibernate vmid
Usage: power.off vmid
Usage: power.on vmid
Usage: power.reboot vmid
Usage: power.reset vmid
Usage: power.shutdown vmid
Usage: power.suspend vmid
Usage: power.suspendResume vmid

Getting `vmid` values

These all have a vmid parameter, so let’s create a small statement that gives the list of vmid on an ESXi system:

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"

On my system the relevant VMs it returns are these:

10
5

The various power commands

The outcome of the various power commands are not as simple as one might think as they often do not just depend on the current power state of the VM, but also on either VMware Tools or open-vm-tools to be running.

Basically these tools do the same, but their origin is different: open-vm-tools is often included as part of Linux distributions; VMware Tools is often installed separately, see:

I have made a table for this hoping it makes reading easier, the explanations are by empirical usage, as the documentation in the help dump (see [Wayback] delimited vim-cmd help for each vmsvc command.txt) does not seem to match behaviour.

Command Explanation
vim-cmd vmsvc/power.getstate vmid Gets the power state of the VM, returning a line Retrieved runtime info followed by lines indicating the power state:

Powered off

Powered on

Suspended
vim-cmd vmsvc/power.hibernate vmid
When neither VMware Tools or open-vm-tools to be running, you get an error:
(vim.fault.ToolsUnavailable) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = 
   msg = "Received SOAP response fault from []: standbyGuest
Cannot complete operation because VMware Tools is not running in this virtual machine."
}
When a hibernate/suspend task is already running, you get an error:
(vim.fault.TaskInProgress) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   task = 'vim.Task:haTask-12-vim.VirtualMachine.suspend-1006072588'
   msg = "Received SOAP response fault from []: standbyGuest
Another task is already in progress."
}
Otherwise, depends on the power state of the VM if vmware tools:
Powered off: keeps the power state of the VM as Powered off and shows an error
(vim.fault.InvalidPowerState) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   requestedState = "poweredOn", 
   existingState = "poweredOff"
   msg = "Received SOAP response fault from []: standbyGuest
The attempted operation cannot be performed in the current state (Powered off)."
}
Powered on: sets the power state of the VM to Suspended and shows no output, unless neither VMware Tools, nor open-vm-tools can be communicated with, then you get this error:
(vmodl.fault.SystemError) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   reason = "Invalid fault"
   msg = "Received SOAP response fault from []: standbyGuest
vim.fault.GenericVmConfigFault"
}
Suspended: keeps the power state of the VM as Suspended and shows an error
(vim.fault.InvalidPowerState) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   requestedState = "poweredOn", 
   existingState = "suspended"
   msg = "Received SOAP response fault from []: standbyGuest
The attempted operation cannot be performed in the current state (Suspended)."
}
vim-cmd vmsvc/power.off vmid
Depends on the power state of the VM and either VMware Tools or open-vm-tools to be running:
Powered off: keeps the power state of the VM as Powered off and shows two lines
Powering off VM:
Power off failed
Powered on: powers off the VM (bypasses any VMware Tools or open-vm-tools) and sets power state of the VM to Powered off showing one line
Powering off VM:
Suspended: Hardware powers off the VM (bypasses any VMware Tools or open-vm-tools) and sets power state of the VM to Powered off showing one line
Powering off VM:
vim-cmd vmsvc/power.on vmid
Depends on the power state of the VM:
Powered on: keeps power state of the VM as Powered off showing two lines
Powering on VM:
Power on failed
Powered off: keeps the power state of the VM as Powered off and shows one line
Powering ofn VM:
Suspended: keeps the power state of the VM as Suspended showing two lines
Powering on VM:
Power on failed
This also undoes a vim-cmd vmsvc/power.hibernate vmid, vim-cmd vmsvc/power.shutdown vmid or vim-cmd vmsvc/power.suspend vmid.
vim-cmd vmsvc/power.reboot vmid
Depends on the power state of the VM and either VMware Tools or open-vm-tools to be running:
Powered off: keeps the power state of the VM as Powered off and shows the error
(vim.fault.InvalidPowerState) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   requestedState = "poweredOn", 
   existingState = "poweredOff"
   msg = "Received SOAP response fault from []: rebootGuest
The attempted operation cannot be performed in the current state (Powered off)."
}
Powered on and either VMware Tools or open-vm-tools are running: uses VMware Tools or open-vm-tools to reboot the VM: keeps the power state of the VM as Powered on.
Powered on, but neither VMware Tools nor open-vm-tools are running: keeps the power state of the VM as Powered on and shows the error
(vim.fault.ToolsUnavailable) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = 
   msg = "Received SOAP response fault from []: rebootGuest
Cannot complete operation because VMware Tools is not running in this virtual machine."
}
Suspended: keeps the power state of the VM as Suspended and shows the error
(vim.fault.InvalidPowerState) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   requestedState = "poweredOn", 
   existingState = "suspended"
   msg = "Received SOAP response fault from []: rebootGuest
The attempted operation cannot be performed in the current state (Suspended)."
}
vim-cmd vmsvc/power.reset vmid
Depends on the power state of the VM:
Powered off: keeps the power state of the VM as Powered off and shows two lines
Reset VM:
Reset failed
Powered on: keeps the power state of the VM as Powered on, bypasses running VMware Tools or open-vm-tools (basically like a hardware reset button) and shows one line
Reset VM:
Suspended: keeps the power state of the VM as Suspended and shows two lines
Reset VM:
Reset failed
vim-cmd vmsvc/power.shutdown vmid
Depends on the power state of the VM and either VMware Tools or open-vm-tools to be running:
Powered off: keeps the power state of the VM as Powered off and shows the error
(vim.fault.InvalidPowerState) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   requestedState = "poweredOn", 
   existingState = "poweredOff"
   msg = "Received SOAP response fault from []: shutdownGuest
The attempted operation cannot be performed in the current state (Powered off)."
}
Powered on and either VMware Tools or open-vm-tools are running: uses VMware Tools or open-vm-tools to shutdown the VM and sets the power state of the VM to Powered off without showing any output.
Powered on, but neither VMware Tools nor open-vm-tools are running: keeps the power state of the VM as Powered on and shows the error
(vim.fault.ToolsUnavailable) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = 
   msg = "Received SOAP response fault from []: shutdownGuest
Cannot complete operation because VMware Tools is not running in this virtual machine."
}
Suspended: keeps the power state of the VM as Suspended and shows the error
(vim.fault.InvalidPowerState) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   requestedState = "poweredOn", 
   existingState = "suspended"
   msg = "Received SOAP response fault from []: shutdownGuest
The attempted operation cannot be performed in the current state (Suspended)."
}
vim-cmd vmsvc/power.suspend vmid
When neither VMware Tools or open-vm-tools to be running, you get an error:
(vim.fault.ToolsUnavailable) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = 
   msg = "Received SOAP response fault from []: standbyGuest
Cannot complete operation because VMware Tools is not running in this virtual machine."
}
When a hibernate/suspend task is already running, you get an error:
(vim.fault.TaskInProgress) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   task = 'vim.Task:haTask-12-vim.VirtualMachine.suspend-1006072588'
   msg = "Received SOAP response fault from []: standbyGuest
Another task is already in progress."
}
Otherwise, depends on the power state of the VM:
Powered off: keeps the power state of the VM as Powered off and shows two lines
Suspending VM:
Suspend failed
Powered on: keeps the power state of the VM as Powered on, and shows one line
Suspending VM:
unless neither VMware Tools, nor open-vm-tools can be communicated with, then you get this error:
(vmodl.fault.SystemError) {
   faultCause = (vmodl.MethodFault) null, 
   faultMessage = , 
   reason = "Invalid fault"
   msg = "Received SOAP response fault from []: standbyGuest
vim.fault.GenericVmConfigFault"
}
Suspended: keeps the power state of the VM as Suspended and shows two lines
Suspending VM:
Suspend failed
vim-cmd vmsvc/power.suspendResume vmid
Depends on the power state of the VM:
Powered off: keeps the power state of the VM as Powered off and shows two lines
Suspend/Resuming the VM:
Suspend/Resume failed
Powered on: keeps the power state of the VM as Powered on, and shows one line
Suspend/Resuming the VM:
Suspended: keeps the power state of the VM as Suspended and shows two lines
Suspend/Resuming the VM:
Suspend/Resume failed
Note that in the VMware web console, this is shown as “Invoke FSR” which is a Fast Suspend Resume, which I think has to do with vMotion.

Command	Explanation
`vim-cmd vmsvc/power.getstate vmid`	Gets the power state of the VM, returning a line `Retrieved runtime info` followed by lines indicating the power state: `Powered off` `Powered on` `Suspended`
`vim-cmd vmsvc/power.hibernate vmid`	When neither VMware Tools or open-vm-tools to be running, you get an error: `(vim.fault.ToolsUnavailable) { faultCause = (vmodl.MethodFault) null, faultMessage = msg = "Received SOAP response fault from []: standbyGuest Cannot complete operation because VMware Tools is not running in this virtual machine." }` When a hibernate/suspend task is already running, you get an error: `(vim.fault.TaskInProgress) { faultCause = (vmodl.MethodFault) null, faultMessage = , task = 'vim.Task:haTask-12-vim.VirtualMachine.suspend-1006072588' msg = "Received SOAP response fault from []: standbyGuest Another task is already in progress." }` Otherwise, depends on the power state of the VM if vmware tools: `Powered off`: keeps the power state of the VM as `Powered off` and shows an error `(vim.fault.InvalidPowerState) { faultCause = (vmodl.MethodFault) null, faultMessage = , requestedState = "poweredOn", existingState = "poweredOff" msg = "Received SOAP response fault from []: standbyGuest The attempted operation cannot be performed in the current state (Powered off)." }` `Powered on`: sets the power state of the VM to `Suspended` and shows no output, unless neither VMware Tools, nor open-vm-tools can be communicated with, then you get this error: `(vmodl.fault.SystemError) { faultCause = (vmodl.MethodFault) null, faultMessage = , reason = "Invalid fault" msg = "Received SOAP response fault from []: standbyGuest vim.fault.GenericVmConfigFault" }` `Suspended`: keeps the power state of the VM as `Suspended` and shows an error `(vim.fault.InvalidPowerState) { faultCause = (vmodl.MethodFault) null, faultMessage = , requestedState = "poweredOn", existingState = "suspended" msg = "Received SOAP response fault from []: standbyGuest The attempted operation cannot be performed in the current state (Suspended)." }`
`vim-cmd vmsvc/power.off vmid`	Depends on the power state of the VM and either VMware Tools or open-vm-tools to be running: `Powered off`: keeps the power state of the VM as `Powered off` and shows two lines `Powering off VM: Power off failed` `Powered on`: powers off the VM (bypasses any VMware Tools or open-vm-tools) and sets power state of the VM to `Powered off` showing one line `Powering off VM:` `Suspended`: Hardware powers off the VM (bypasses any VMware Tools or open-vm-tools) and sets power state of the VM to `Powered off` showing one line `Powering off VM:`
`vim-cmd vmsvc/power.on vmid`	Depends on the power state of the VM: `Powered on`: keeps power state of the VM as `Powered off` showing two lines `Powering on VM: Power on failed` `Powered off`: keeps the power state of the VM as `Powered off` and shows one line `Powering ofn VM:` `Suspended`: keeps the power state of the VM as `Suspended` showing two lines `Powering on VM: Power on failed` This also undoes a `vim-cmd vmsvc/power.hibernate vmid`, `vim-cmd vmsvc/power.shutdown vmid` or `vim-cmd vmsvc/power.suspend vmid`.
`vim-cmd vmsvc/power.reboot vmid`	Depends on the power state of the VM and either VMware Tools or open-vm-tools to be running: `Powered off`: keeps the power state of the VM as `Powered off` and shows the error `(vim.fault.InvalidPowerState) { faultCause = (vmodl.MethodFault) null, faultMessage = , requestedState = "poweredOn", existingState = "poweredOff" msg = "Received SOAP response fault from []: rebootGuest The attempted operation cannot be performed in the current state (Powered off)." }` `Powered on` and either VMware Tools or open-vm-tools are running: uses VMware Tools or open-vm-tools to reboot the VM: keeps the power state of the VM as `Powered on`. `Powered on`, but neither VMware Tools nor open-vm-tools are running: keeps the power state of the VM as `Powered on` and shows the error `(vim.fault.ToolsUnavailable) { faultCause = (vmodl.MethodFault) null, faultMessage = msg = "Received SOAP response fault from []: rebootGuest Cannot complete operation because VMware Tools is not running in this virtual machine." }` `Suspended`: keeps the power state of the VM as `Suspended` and shows the error `(vim.fault.InvalidPowerState) { faultCause = (vmodl.MethodFault) null, faultMessage = , requestedState = "poweredOn", existingState = "suspended" msg = "Received SOAP response fault from []: rebootGuest The attempted operation cannot be performed in the current state (Suspended)." }`
`vim-cmd vmsvc/power.reset vmid`	Depends on the power state of the VM: `Powered off`: keeps the power state of the VM as `Powered off` and shows two lines `Reset VM: Reset failed` `Powered on`: keeps the power state of the VM as `Powered on`, bypasses running VMware Tools or open-vm-tools (basically like a hardware reset button) and shows one line `Reset VM:` `Suspended`: keeps the power state of the VM as `Suspended` and shows two lines `Reset VM: Reset failed`
`vim-cmd vmsvc/power.shutdown vmid`	Depends on the power state of the VM and either VMware Tools or open-vm-tools to be running: `Powered off`: keeps the power state of the VM as `Powered off` and shows the error `(vim.fault.InvalidPowerState) { faultCause = (vmodl.MethodFault) null, faultMessage = , requestedState = "poweredOn", existingState = "poweredOff" msg = "Received SOAP response fault from []: shutdownGuest The attempted operation cannot be performed in the current state (Powered off)." }` `Powered on` and either VMware Tools or open-vm-tools are running: uses VMware Tools or open-vm-tools to shutdown the VM and sets the power state of the VM to `Powered off` without showing any output. `Powered on`, but neither VMware Tools nor open-vm-tools are running: keeps the power state of the VM as `Powered on` and shows the error `(vim.fault.ToolsUnavailable) { faultCause = (vmodl.MethodFault) null, faultMessage = msg = "Received SOAP response fault from []: shutdownGuest Cannot complete operation because VMware Tools is not running in this virtual machine." }` `Suspended`: keeps the power state of the VM as `Suspended` and shows the error `(vim.fault.InvalidPowerState) { faultCause = (vmodl.MethodFault) null, faultMessage = , requestedState = "poweredOn", existingState = "suspended" msg = "Received SOAP response fault from []: shutdownGuest The attempted operation cannot be performed in the current state (Suspended)." }`
`vim-cmd vmsvc/power.suspend vmid`	When neither VMware Tools or open-vm-tools to be running, you get an error: `(vim.fault.ToolsUnavailable) { faultCause = (vmodl.MethodFault) null, faultMessage = msg = "Received SOAP response fault from []: standbyGuest Cannot complete operation because VMware Tools is not running in this virtual machine." }` When a hibernate/suspend task is already running, you get an error: `(vim.fault.TaskInProgress) { faultCause = (vmodl.MethodFault) null, faultMessage = , task = 'vim.Task:haTask-12-vim.VirtualMachine.suspend-1006072588' msg = "Received SOAP response fault from []: standbyGuest Another task is already in progress." }` Otherwise, depends on the power state of the VM: `Powered off`: keeps the power state of the VM as `Powered off` and shows two lines `Suspending VM: Suspend failed` `Powered on`: keeps the power state of the VM as `Powered on`, and shows one line `Suspending VM:` unless neither VMware Tools, nor open-vm-tools can be communicated with, then you get this error: `(vmodl.fault.SystemError) { faultCause = (vmodl.MethodFault) null, faultMessage = , reason = "Invalid fault" msg = "Received SOAP response fault from []: standbyGuest vim.fault.GenericVmConfigFault" }` `Suspended`: keeps the power state of the VM as `Suspended` and shows two lines `Suspending VM: Suspend failed`
`vim-cmd vmsvc/power.suspendResume vmid`	Depends on the power state of the VM: `Powered off`: keeps the power state of the VM as `Powered off` and shows two lines `Suspend/Resuming the VM: Suspend/Resume failed` `Powered on`: keeps the power state of the VM as `Powered on`, and shows one line `Suspend/Resuming the VM:` `Suspended`: keeps the power state of the VM as `Suspended` and shows two lines `Suspend/Resuming the VM: Suspend/Resume failed` Note that in the VMware web console, this is shown as “Invoke FSR” which is a Fast Suspend Resume, which I think has to do with vMotion.

Notes:

there is no command vim-cmd vmsvc/power.startup vmid (to undo vim-cmd vmsvc/power.shutdown vmid), use vim-cmd vmsvc/power.on vmid in stead.
there is no command vim-cmd vmsvc/power.resume vmid (to undo vim-cmd vmsvc/power.suspend vmid), use vim-cmd vmsvc/power.on vmid in stead.
there is no command vim-cmd vmsvc/power.wakeup vmid (to undo vim-cmd vmsvc/power.hibernate vmid), use vim-cmd vmsvc/power.on vmid in stead.

Running the various power commands on all relevant VMs

This will be the topic for the next installment.

–jeroen

Updating chocolatey itself

Posted by jpluimers on 2021/04/28

I wondered how to update (ore actually choco upgrade as choco update will command will eventually be deprecated) Chocolatey itself.

It appeared my stock upgrade batch file choco upgrade all --exit-when-reboot-detected --yes was already doing it as the magic all will upgrade all packages.

To upgrade just [Wayback] chocolatey itself, remember it is a package, so choco upgrade chocolatey --exit-when-reboot-detected --yes will work fine.

–jeroen

Posted in Chocolatey, Power User, Windows | Leave a Comment »

« Previous Entries

	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…
	Thaddy de Koning on Formulier voor bewindvoerders…

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 April, 2021

Available commands

Unavailable commands

vim-cmd-hibernate-running-VMs.sh and vim-cmd-suspend-running-VMs.sh

vim-cmd-resume-suspended-VMs.sh and vim-cmd-wakeup-suspended-VMs.sh

vim-cmd-power-off-powered-on-VMs.sh

vim-cmd-power-on-powered-off-VMs.sh, vim-cmd-power-on-shutdown-VMs.sh and vim-cmd-startup-shutdown-VMs.sh

vim-cmd-reboot-powered-on-VMs.sh

vim-cmd-reset-powered-on-VMs.sh

vim-cmd-suspendResume-powered-on-VMs.sh

Future episodes

Rate this:

Share this:

Rate this:

Share this:

Ik heb al 1 prik met AstraZeneca gehad

Hoe gaat het nu verder met mijn 2e prik?

Inzet AstraZeneca-vaccin

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Available commands

Unavailable commands

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

Getting the vmid

Getting VM name

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

Rate this:

Share this:

Rate this:

Share this:

Linking HTML Help (CHM) Files

Using HTML Help from Code

Providing Help for Controls

Rate this:

Share this:

Getting vmid values

The various power commands

Running the various power commands on all relevant VMs

Rate this:

Share this:

Rate this:

Share this:

`vim-cmd-hibernate-running-VMs.sh` and `vim-cmd-suspend-running-VMs.sh`

`vim-cmd-resume-suspended-VMs.sh` and `vim-cmd-wakeup-suspended-VMs.sh`

`vim-cmd-power-off-powered-on-VMs.sh`

`vim-cmd-power-on-powered-off-VMs.sh`, `vim-cmd-power-on-shutdown-VMs.sh` and `vim-cmd-startup-shutdown-VMs.sh`

`vim-cmd-reboot-powered-on-VMs.sh`

`vim-cmd-reset-powered-on-VMs.sh`

`vim-cmd-suspendResume-powered-on-VMs.sh`

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

Getting the `vmid`

Getting VM `name`

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

Getting `vmid` values