The Wiert Corner – irregular stream of stuff

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

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,573 other followers

Having cancer is not a fight or a battle, it is about having luck or misfortune

Posted by jpluimers on 2021/12/10

No, I am not giving up. But I am having the regular fear of the upcoming checks: did the metastases return, or do I have the luck to outlive some 30% of my peer group.

The last metastases surgery has been slightly more than a year ago. A year from now, that percentage hopefully will be 50% and slowly increase over time until about 90% in some 9 years from now.

At year’s end, I will know for sure.

Below are some links on, mostly Dutch, articles about the mental side of having cancer, or having survived it for now.

Food for thought, somehow fitting for this time of the year.

Especially helpful are the articles by Ivan Wolffers, doctor, emeritus professor, writer (medical literature, fiction – the latter aimed at children and adults – and columns), some of them I found fitting:

There is also his personal blog, of which the full list of 2021 articles is at [Wayback/Archive] 2021 – Ivan Wolffers.

This is about my post title: [Wayback/Archive] “Waarom doen we alsof kanker een strijd is met winnaars en verliezers?” – NPO3.nl, which in depth explains both that cancer isn’t a battle with winners and losers, and that if people keep communicating it as a fight, that it has an adverse effect on the psychology of those patients, for instance some of them even opting out for treatment at all or undergoing treatment for too long making the final stage unbearable making it impossible to bring final closure in a reasonable manner. More examples in the article, of which the Google translated version is actually pretty good:

[Wayback/Archive] “Why do we pretend that cancer is a battle of winners and losers?” – NPO3.nl.

I got it via [Archive] Jacquel💉en on Twitter: “…” / Twitter, which I retweeted as

[Archive] Jeroen Wiert Pluimers on Twitter: “Dit. Zo belangrijk. Je hebt mazzel, of pech. En bij elke controls is er stress en de vraag: hoeveel mazzel heb ik deze keer?” / Twitter

This. So important. You either are lucky, or have misfortune. And with every check there is the stress and question: how lucky am I this time?

I quote-tweeted it, resulting in this nice thread (Twitter Translate works quite well on it):

The luck I had was in part due to the Covid-19 pandemic. Because of it age based cancer screening (mainly breast and colon cancer) had been scaled down, which – for hospitals that only do cancer – made it very easy to plan all the procedures.

The misfortunes I had were manyfold. Later I will blog about it in more detail, but in short it had to do with getting on the wait-and-see list, developing metastases that were found at the first check, chemotherapy causing way too much neuropathy and other effects, combined surgery on metastases removal and ileostomy repair causing a colon leak, emergency surgery, abscess and inflammation development after the surgeries and prolapses of both the ileostomies I had. Plus a very long recuperation of all procedures: it is still going on.

Memory

For me the combination of chemotherapy with radiation therapy, four major surgeries and lots of family issues going on within a year severely affected my memory. It steadily is coming back, especially tech stuff is doing very much OK now. Day to day things will likely never be at the height they were before, but that’s OK: there are good tools for that (in the past I could largely do without an agenda, now I finally got adjusted to using one).

LAR syndrome

My LAR syndrome effects are tough and take a lot of time. Going to the toilet I often do not know what will come and for how long. This is due to both surgery in the pelvis minor area will always do nerve damage, and almost all of my rectum being gone.

It means that on average I spend about 2 hours per day on the toilet, of which one hour during the night causing me to have a gap of about 90 minutes between the blocks of sleep. On bad days, it means spending 4-5 hours on the toilet.

Oh, and I wear diapers as about once every two weeks even rushing to the toilet does not help and without them it would make a bigger mess.

Fear

There is always the (sometimes latent) fear of the metastases returning.  Every pain and every odd feeling still make me think “is this cancer again?”. It reminds me of the first 5+ years after my wife had cancer. Hopefully it will fade and I will make those 5+ years.

When writing this, I’ll be having checkups in 2 weeks time. Slightly more than a year after the surgery that removed the metastases, I have about a 50% chance of them returning within a year from now and 90% of them returning in 9 years from now.

Then hopefully treatment procedures have improved, but for now it would mean the same chemotherapy, but heavier and longer. Which would also mean learning to cope with permanent neuropathy.

Positive

I do have enough quality of life, and my wife has survived her cancer for 21 years now. I hope to be at the good side of statistics and still be here at least a few more years in OK health. Health won’t return to the levels it was, but my mind gets better over time, so I hope to be able to work again at least part-time and be able to setup enough support so my mentally retarded brother can cope without relying on me.

That is enough to keep me going for the foreseeable future.

It’s a bit like Steve talks about in the video below.

References

I would have liked to follow up on Current state: still fighting the metastases of the rectum cancer; chemos are done, major liver surgery in about 3 weeks, but then events caught up with me, so I made the choice to have the blog run just auto-posting stuff from the (then almost) 2 year queue.

This is part of my series on cancer related posts, of which the rectum cancer posts are a subset..

–jeroen

Read the rest of this entry »

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

Current state: still fighting the metastases of the rectum cancer; chemos are done, major liver surgery in about 3 weeks

Posted by jpluimers on 2020/08/23

A long follow-up of Current state: still fighting with rectum cancer, but chances for better quality of life which does not even include everything, because so much happened.

So this is the current state; browse back via Twitter for more of the history which you can find at [Archive.is] Jeroen Pluimers on Twitter: “Too much to let sink in …” and [Archive.is] Jeroen Pluimers (@jpluimers) | Twitter.

Too much to let sink in, not just about the hospital results and upcoming surgery, but also about Cindy and Danny Thorpe who just lost their house in the California forest fires, despite it being on the humid side of the Santa Cruz mountains.
If you can help anybody affected by the #CZULightningComplex, please do. Many families there are going through a rough time for the foreseeable future especially because of the combination of fires and COVID.
If you are in that area: be careful, be safe.
For me it is mixed emotions time.
The chemo did make the cancer operable. Some tumors have shrunken, a few small ones are invisible, probably because of the chemo-induced hepatic steatosis, and no new tumor were found.
The prolapse has grown big: extended it is at least 10cm of bowel pushing itself outside of the abdomen causing many stoma leaks (5 full ones in 2 weeks time and 2 almost ones yesterday).
The good news is that it means there is hardly any intestinal adhesion.
The bad news: it takes 4-8 hours a day (of which 1-2 hours during the night) pushing the bowel back into the stoma so the output opening becomes unblocked and the poo can get out.
Though a temporary situation, this eats a lot of energy.
It means I need to find a way to keep my body in shape to prepare for surgery which is in 3-4 weeks (likely mid September).
The surgery will be tough as it will focus on 2 things:
  1. Removing areas of of the liver where the tumors are and were (which is about 30-50% of the liver).
  2. Likely remove the gallbladder, to minimise the chance of bile leakage (which is devastating when it gets into the abdomen)

    (Good news: no chance to get gallstones)

  3. repair the small intestine and remove the stoma.
It is going to be bloody surgery (because of the liver part) taking some 4 hours or more, likely ending up in the IC because the post-surgery risks.
This scares the hell out of me.
In addition recovery will take a long time, and even longer for liver tissue growing back (it will never reach 100%, but should be much more than 50% in a few years time).
I also need to re-learn how to poop, which likely means back to diaper age for quite a while.
So all of this means I feel very confused. Glad on the one side because I will loose the cancer and the stoma, but mixed about the risks and recovery.
More later.

–jeroen

Via [Wayback] Thread by @jpluimers on Thread Reader App: Too much to let sink in, not just about the hospital results and upcoming surgery, but also about Cindy and @danny_thorpe who just lost their house in the California forest fires…

Posted in About, Cancer, Personal, Rectum cancer | 1 Comment »

The biggest lie I tell myself is not about new years resolutions.

Posted by jpluimers on 2019/01/01

The biggest lie I tell myself is “I don’t need to write that down, I’ll remember it”

It’s likely older, but the oldest reference I could find was 2012 [WayBack].

So before I forget:

Happy New Year everyone!

With the above quote, it is no coincidence I started my blog even earlier (in 2009): it’s my off-line memory, way better readable than my hand-writing and indexed by various search engines.

Read the rest of this entry »

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

Over stemmen in je hoofd: de criticus en de lieverd

Posted by jpluimers on 2022/01/28

De meesten hebben een veel sterkere invloed van de criticus in hun hoofd dan de lieverd. Geef de laatste ook eens aandacht, bijvoorbeeld door vaker te lachen.

 

–jeroen

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

Fritz!Box and mobile USB sticks (Huawei E3372; 4G Systems W1208): some links; hopefully later also some personal experience

Posted by jpluimers on 2022/01/27

There seem to be at least three Huawei E3372 models:

  • Huawei E3372s
  • Huawei E3372h-153
  • Huawei E3372-h-320

4G Systems W1208 seems to have only one model (it is an OEM Huawei E3372, not sure which submodel), but it looks like it is only available in Germany, and might even be region locked.

There are various reports on which ones work/fail with Fritz!Box devices as backup-internet link.

Here are some links:

  • [Archive.is] HUAWEI E3372h-320 LTE-Stick: Amazon.de: Elektronik
  • [Wayback] Huawei E3372 (Wit) – Kenmerken – Tweakers: E3372h-153
  • [Wayback] Huawei Mobile USB-stick E3372 voor Windows

    Zoekt u een snelle 4G LTE dongle met een geïntegreerd micro SD kaart slot en 2 externe antenne aansluitingen? Dan is de Huawei E3372h-153 iets voor u.

  • [Wayback/Archive.is] E3372h-320 (Hi-Link) Dongle now works with fritz OS 7.25 : fritzbox

    After updating to Fritz OS 7.25(2021-03-11) , The Huawei E3372h-320 Mobile Dongle now works with the Fritzbox 7530 without any need to disable the HiLink software (aka flash into stick mode) on the Dongle

  • [Archive.is] Firmware-update: AVM Fritz!Box 5490 151.07.27 – Computer – Downloads – Tweakers

    • Improved New “Compatibility mode for mobile broadband dongles” option for generic integration of variants of known mobile broadband dongles
    • Improved Country-specific list of mobile network providers when FRITZ!Box used with a USB mobile network dongle
    • Improved Optimized details for “Advanced failover protection” setting
    • Improved Mobile network provider “Magenta Mobil” added for Austria
    • Improved Support for Huawei E3372h-320 USB mobile network dongle

  • [Wayback] Firmware-update: FRITZ!Box 7490 7.26 – Computer – Downloads – Tweakers

    • Improved New “Compatibility mode for mobile broadband dongles” option for generic integration of variants of known mobile broadband dongles
    • Improved Country-specific list of mobile network providers when FRITZ!Box used with a USB mobile network dongle
    • Improved Optimized details for “Advanced failover protection” setting
    • Improved Mobile network provider “Magenta Mobil” added for Austria
    • Improved Support for Huawei E3372h-320 USB mobile network dongle

  • [Wayback] Firmware-update: FRITZ!Box 7590 7.25 – Computer – Downloads – Tweakers

    • Improved Support for Huawei E3372h-320 USB mobile network dongle

  • [Wayback] Firmware-update: AVM FritzBox 7590 – FritzOS 7.10 – Computer – Downloads – Tweakers
    • NEW Higher data rates possible through support for the Mobile Broadband Interface Model (MBIM) (for instance, W1208 from 4G Systems)
    • NEW Push Service for sending received text messages
  • [Wayback] Setting up 4G backup on FritzBox 7530 :: Mobile Broadband (3G, 4G, 5G etc) :: think broadband

    AVM Fritz OS 7.25 (March 2021) now works with the Hi-Link software in the Huawei Dongle.

  • [Wayback] fritz 7530 USB LTE compatable dongle – AVM

    I just tested using VoIP when using the USB Mobile data on the E3372 dongle on the 7590 (Optus pre-paid mobile data plan). I was able to call out on VoIP to my mobile. I suppose incoming VoIP call would also work…

    The secret to getting VOIP to work over a mobile connection is to set the Transport Protocol in the FritzBox to TCP. You thus need a telephony provider that supports TCP.
    I’ve tested my 7590 (running FritzOS 7.20 or later) and an E3372 (using Optus) with SipTalk, and it worked correctly.
    You’ll find the setting under Telephone number, Edit, Additional Settings for the Connection, Transport protocol. Other needed settings are: Username, Password and Registrar. You can leave Proxy and Stun servers blank.

  • [Wayback] Fritz!Box 7490 und Huawei E3372 für Internet | IP Phone Forum

    Hallo, ich habe F!B 7490 international, habe Huawei E3372.USB LTE Stick mit o2.de SIM angeschlossen. LTE Internetverbindung funktioniert perfekt mit APN “internet”.
    Zuerst habe ich E3372 im Tethering mode an der F!B 7490i betrieben und konnte ich auf Hilink zugreifen.
    Da ich aber die native IP adresse benutzen wollte, habe
    habe ich die E3372 als Modem angeschlossen. Internet mit APN “internet” funktioniert weiterhin perfekt. Bekomme eine private native IP adresse an der F!B 7490i.
    Bei O2.de habe ich mir für SIM-Karte eine öffentliche IP adresse geben lassen. Dazu muste ich den APN auf “netpublic” umstellen.
    Jetzt kommt die Internetverbindung nicht zu stande. F!B zeigt unter ‘Mobilfunk’ dass das Netz gefunden wurde ‘bereit’ aber SIM ist nicht registriert wurde.
    Im Modem Mode kann ich über Hilink auf die Konfiguratioin der E3372 nicht zugreifen.
    Die SIM Karte in einem anderen Router (TP-Link M7350) funktioniert die SIM Karte mit APN “netpublic” mit öffentliche IP adresse eiwandfrei.
    Zurück zu F!B 7490i mit E3372 als Modem und APN “netpublic”.
    Bis jetzt keine Hilfestellung von AVM.
    Bin dabei das Problem mit F!B 7490i zu lösen.

    Mit aktueller 7.12-DE-FW scheinen die Sticks den Tethering-Mode nicht mehr (ohne weiteres?) zu beherrschen und werden trotz-HiLink-FW (22….) trotzdem ausschließlich als Modem angesprochen bzw. umgeschaltet.
    Vormals -bei älterer FW <7.xx … iirc- hing die Einbindung/Erkennung entweder als Modem oder Tethering-Device allein von der FW des 3372-Sticks ab (22er versus 21er-Version). Umso erstaunter bin ich über die eingangs zitierte Aussage, dass Du dies anscheinend wohl nach Belieben steuern könntest? Über das “how” wäre sicherlich mancher Leser hoch erfreut.
    Zu Deinem Problem: Es könnte sein, dass im Modem-Mode auf vorgefertigte APN-Listen zurückgegriffen wird, die eben “netpublic” (noch) nicht kennen und eine diesbzgl. Änderung im FB-GUI gleichfalls nicht greift? Die FW des 3372 ist eh schon recht betagt, sodass dieser intern die Verschmelzung von E-Plus und O² wohl auch noch nicht vollständig mitbekommen hat.

    Habe ich vom AVM den gleichen Typ erhalten wie Du beschreibst, es lag genau an dem dass ich ein neues Profil mit APN “netpublic” einrichten mußte. Jetzt funktioniert die F!B 7490i mit E3372 und APN “netpublic” tadenlos.
    Hier noch die Angaben zu E3372h und F!B 7490i.
    E3372h gekauft bei Conrad im Mai 2017
    Bestell-Nr.: 1234133 – 62
    EAN Code 6901443021437
    HW: Hardware-Version: CL2E3372HM
    FW: Software-Version: 22.328.62.00.1217
    HiLink: Weboberflächen-Version: 17.100.18.05.1217
    7490i Model: 20002647
    ASIN:B00H3IC3FC
    HWRevision 185
    HWSubRevision 6
    ProductID Fritz_Box_HW185
    annex A
    firmware_info 113.07.12
    firmware_version avme

    Habe mit dem AVM Support geschrieben. Anscheinend arbeitet AVM tatsächlich daran das Feature rauszuwerfen. Haben ja auch meine Screenshots zur 7490 113.07.19-75207 Labor gezeigt in gezeigt und zeigt auch die neue Labor FW (FRITZ.Box 7490 (UI) 113.07.19-75736 siehe Screenshot in diesem Post), die alles nochmal “klarer formuliert” aber halt nichts daran ändert, dass ein Feature entfernt wird, ohne es in die Release Notes zu schreiben. Außerdem könnte es Nutzer dazu bringen, kein Update mehr zu machen, wenn ein Feature weg gekürzt wird, dass sie früher einwandfrei genutzt haben… :/

  • [Wayback] [Frage] – LTE Stick für 7590 | IP Phone Forum

    An meiner 7490 hängt ein Huawei E3372 und macht was er soll. Einen Anschluss für eine externe Antenne hat er auch.

    In einer FB7490 FW 7.19-81587 (inhaus) erkenne ich im Bereich “Netzverfügbarkeit” 2von5 Balken … im Telekom-Mobilfunknetz hier indoor.
    Auch wenn ich nicht stündlich/täglich Ooaklo-Speedtests versuche, komme ich eher regelmäßig/ohne Probleme “eingebremst auf tarifliche 50/10MBit/s” auf die Werte.

    Generell habe ich unmaßgeblich erkannt, dass die E3372s oder h erheblich “wärmer” werden im Betrieb als der W1208. Ein Blick auf das Konstruktionsdatum E3372 ca. 2005/2006 lt. FW der W1208 laut “Bepper” 18/8/2019 könnte doch einen markanten Hinweis liefern, womit man besser fährt?

    Habe mir nun einen gebrauchten W1208 von 4GSystems (1und1) geholt und der läuft.

    Ok jetzt hab ich es nochmal versucht und plötzlich wie von selbst wird der Stick korrekt erkannt auch an der 7590.

    XSStick W1208 (1&1)

  • [Wayback] FritBox 7490 und Huawei E3372h-153 – kein No-HiLink? | IP Phone Forum

    In Bezug auf den E3372s/h ist es als Backup-Lösung unerheblich, ob dieser als als usb-net Device (HiLink-FW) oder usb-modem (NoHilink-FW) arbeitet. Dies ist ausschließlich von der verwandten SIM (Tarif/Netz/Lokaler Empfang) abhängig. Gerade bei O² (Netzkonsolodierung mit Base/E-Plus) kann es lokal sinnvoller sein, sich im 3G-Modus zu bewegen statt 4G.

    Damit ein usb-modem -hier ein E3372 mit NonHilink- vollständig und korrekt eingebunden wird, muss als Inet-verbindung eben der Client-Modus (hier hinter Kabelmodem) erst verlassen werden und “voll” über Mobilfunkverbindung kurz eingerichtet werden.

    -Dies gilt auch für andere voicefähige UMTS-Sticks z.B. für die GSM-Gateway-Geschichte-

    Danach kann man wieder auf Client-Modus umschalten. -hier I-Net via LAN1 und Kabelmodem-

    In Verbindung bzw. dem Einsatz an einer FB7490 ist dies -aus meiner persönlichen Sichtweise heraus- nicht einfach zu beantworten, da es oftmals auch an der verwandten SIM-Karte liegt und eben der gebuchten Geschwindigkeit nebst den Empfangsverhältnissen. Oftmals kommt die Kombination eher stationär auf Campingplatz/Gartenlaube/Ferienwohnung o.ä. zum Einsatz, wo jeder dies halt persönlich Testen muss, was im Dauereinsatz stabiler läuft.
    Erschwerend kommt hinzu, dass laut aktueller 7490 Intern-/Labor-FWs sich einiges tut in der Anbindung, da wohl Anpassungen im Rahmen der FB6890, die eben ein UMTS/LTE-Device schon onboard hat, ins Haus stehen. Da es keine Voicefähige FW für den E3372 gibt, kann man durchaus bei einer HiLink-FW bleiben. In Verbindung mit anderen Routern auf Linux-Basis, ist die Anbindung -lt. Tenor im lteforum.at- mit der NonHiLink-FW stabiler.

    Und wo wir schon dabei sind: was ist der Unterschied zwischen dem E3372s und E3372h?

    Es handelt sich nach meinen Wissen um unterschiedliche Hardware-Revisionen. Bekannt ist allerdings, dass die h-Version inpunkto Umflashen recht zickig sein kann, und es wohl öfters schon zu gebrickten Sticks dabei kam/kommt und man mit der “Nadel-Methode” und Spezialtools diese eher mühsam wiederbeleben muss/kann.

  • [Wayback] Internettoegang via mobiel netwerk via Fritz!box 7369

    Access-point (APN) is voor een XS4ALL SIM iets van umts.xs4all.nl of
    umts2.xs4all.nl, die informatie kreeg je bij de SIM.
    Access number is *99#, en username/password zijn onbelangrijk, maar
    moeten wel ingevuld zijn.

    APN: umts.xs4all.nl
    Gebruikersnaam: xs4all
    Wachtwoord: 1234
    Pincode: 0000

    • Huawei E180
    • Huawei E3372 , de E3135 dongles en met de Samsung
      J5 in tethering mode

  • [Wayback/Archive.is] AVM veröffentlicht FRITZ!OS 7 für weitere Geräte – teltarif.de News

    hat AVM auch ein neues FRITZ!Labor zum Download bereitgestellt. Dieses trägt die Versionsnummer 6.98-63245 und richtet sich an Besitzer der FRITZ!Box 4020

    Zudem sollen sich Internet-Verbindungen mit dem Huawei-LTE-Stick mit der Seriennummer E3372h-153 wieder herstellen lassen.

  • [Wayback] [Problem] – FritzBox 7580 mit Huawei E3372 geht so halb (aber unbrauchbar) | IP Phone Forum This is with older Fritz!Box and Huawei firmwares.
  • [Wayback] Firmware Versionen Hi/Non Hilink E3372h inkl Mod | LTE-Forum Österreich
  • [Wayback] Probleem met 4G USB modem HuaweiE3272 icm Fritzbox 4790 – Netwerken – GoT

    als ik mijn Huawei E3272s-153 4G/LTE USB modem aansluit op 1 van de USB poorten van mijn Fritzbox 4790, loop ik tegen het rare fenomeen aan dat afhankelijk van de SIM welke in de dongel aanwezig is, ik wél of géen IP adres krijg toegewezen via het betreffende 3G/4G netwerk.

    Mijn firmware van de Huawei E3272s-153 en Fritzbox 4790 zijn up to date.

    Wat ik al gevonden of geprobeerd heb, met 4 verschillende SIM kaarten:

    KPN SIM met data abonnement only:
    Werkt met USB dongle in PC met KPN mobile connect software (LTE en HSPA+ netwerken getest).
    Werkt niet icm Fritzbox 4790 (wordt wel herkend, pin is valide, KPN UMTS netwerk wordt herkend in GUI Fritzbox, maar er wordt geen IPv4 IP adres toegewezen).

    KPN SIM met voice en data abonnement:
    Werkt met USB dongle in PC met KPN mobile connect software (HSPA+ netwerk getest)
    Werkt niet icm Fritzbox 4790 (wordt wel herkend, pin is valide, KPN UMTS netwerk wordt herkend in GUI Fritzbox, maar er wordt geen IPv4 IP adres toegewezen).

    XS4ALL SIM met alleen data abonnement:
    Werkt met USB dongle in PC met KPN mobile connect software (HSPA+ netwerk getest)
    Werkt wel! in icm Fritzbox 4790, KPN UMTS/WCMDA wordt herkend en connecteert op UMTS, krijgt een IP adres toegewezen en LAN devices hebben daarna internet toegang.

    BEN SIM met data/voice abonnement:
    Werkt met USB dongle in PC met KPN mobile connect software (HSPA+ netwerk getest)
    Werkt wel! in icm Fritzbox 4790, BEN UMTS wordt herkend en connecteert op UMTS, krijgt een IP adres toegewezen en LAN devices hebben daarna internet toegang.

  • [Wayback/Archive.is] LTE-Surfstick bei 1&1 – Ihr mobiler Internet-Stick mit LTE

    Allgemein

    Hersteller: HUAWEI

    Modell: E3372

–jeroen

Posted in Power User, Hardware, Internet, Fritz!, Fritz!Box | Leave a Comment »

ESXi: on the console/ssh, when a moved VM pauses during power-on: show which VMs have messages waiting, then answer them

Posted by jpluimers on 2022/01/27

First the script that display messages for all virtual machines, vim-cmd-display-messages-for-all-VMs.sh:

#!/bin/sh
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 "Messages for VM with id ${vmid} which has power state ${powerState} (name = ${name}; vmPathName = ${vmPathName})."
    vim-cmd vmsvc/message ${vmid}
done
exit 0

It is very similar to vim-cmd-reload-all-VM-vmx-configurations.sh from Source: ESXi: reloading all virtual machines from their (potentially) vmx files.

Messages I know either equal “No message” or are about “This virtual machine may have been moved or copied.

If there is no available message, then you always get the stock message No message., so this is something you can use as a check in scripts.

The only messages I know of (and the only one I could find when searching for [Wayback] “vim-cmd vmsvc/message” – Google Search) are like these (where # is a number, like 18 , 235910112 or 6233874: they are unique messageId values so you can refer to them when answering the message):

  • ESXi 4.x era (from [Wayback] Answering a virtual machine related question from the command line (1026835)):
    Virtual machine message #:
    msg.uuid.altered:This virtual machine may have been moved or copied.
    
    To configure certain management and networking features VMware ESX needs to know which.
    
    Did you move this virtual machine, or did you copy it?
    If you don't know, answer "I copied it".
    
    0. Cancel (Cancel)
    1. I _moved it (I _moved it)
    2. I _copied it (I _copied it) [default]
  • ESXi 5.x era (from [Wayback] Starting a virtual machine from the ESXi CLI pauses forever | viktorious.nl – Virtualization & Cloud Management):
    Virtual machine message #:
    msg.uuid.altered:This virtual machine may have been moved or copied.
    
    To configure certain management and networking features VMware ESX needs to know which.
    
    Did you move this virtual machine, or did you copy it?
    If you don't know, answer "I copied it".
    
    0. Cancel (Cancel)
    1. I moved it (I moved it)
    2. I copied it (I copied it) [default]
  • ESXi 5.5 era (from [Wayback] Moving a powered off VM from CLI · RR Labs):
    Virtual machine message #:
    This virtual machine might have been moved or copied. In order to configure certain management and networking features, VMware ESX needs to know if this virtual machine was moved or copied. If you don't know, answer "I Copied It".
       0. Cancel (Cancel)
       1. button.uuid.movedTheVM (I Moved It)
       2. button.uuid.copiedTheVM (I Copied It) [default]
  • ESXi 6.5 (one of my own machines):
    Virtual machine message #:
    This virtual machine might have been moved or copied. In order to configure certain management and networking features, VMware ESX needs to know if this virtual machine was moved or copied. If you don't know, answer "I Copied It". 
       0. button.uuid.cancel (Cancel)
       1. button.uuid.movedTheVM (I Moved It)
       2. button.uuid.copiedTheVM (I Copied It) [default]

You get the pending message for a specific machine 25 using the vim-cmd vmsvc/message 25 like here:

# vim-cmd vmsvc/message 25
Virtual machine message 5970112:
This virtual machine might have been moved or copied. In order to configure certain management and networking features, VMware ESX needs to know if this virtual machine was moved or copied. If you don't know, answer "I Copied It". 
   0. button.uuid.cancel (Cancel)
   1. button.uuid.movedTheVM (I Moved It)
   2. button.uuid.copiedTheVM (I Copied It) [default]

The “[default]” will automatically be answered on ESXi 6.5 after four (4) minutes. For this, I got two (2) identical lines of log in /var/log/hostd.log for this:

2021-05-15T13:10:27.062Z info hostd[AE81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013/archiveteam-warrior-v3-20171013.vmx] Answered question 5970112
2021-05-15T13:10:27.062Z info hostd[AE81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013/archiveteam-warrior-v3-20171013.vmx] Answered question 5970112

Intermezzo: /var/log/hostd.log extract when not answering the “moved” question

A few observations of the log file is at the bottom of this post in a gist [Archive.is].

  • each vim-cmd vmsvc invocation leads to
    • a logon event with log-entries like these where I really wonder where password comes from. as this is not a new interactive logon:
      Accepted password for user root from 127.0.0.1
      2021-05-15T13:05:58.568Z info hostd[AEC2B70] [Originator@6876 sub=Vimsvc opID=vim-cmd-56-584b] [Auth]: User root
      2021-05-15T13:05:58.568Z verbose hostd[AEC2B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-56-584b] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
      2021-05-15T13:05:58.568Z info hostd[AEC2B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=vim-cmd-56-584b] Event 762 : User root@127.0.0.1 logged in as VMware-client/6.5.0
      2021-05-15T13:05:58.568Z verbose hostd[AEC2B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-56-584b] RecordOp ADD: sessionList["5263dcbb-1baf-7a5a-ab7b-ea07e6499e50"], ha-sessionmgr. Applied change to temp map.
      
    • a logoff event with log-entries like these (note a slightly different opID, but the same sessionList ID):
      2021-05-15T13:05:58.623Z verbose hostd[AEC2B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-56-5859 user=root] RecordOp ASSIGN: info, haTask--vim.ServiceInstance.retrieveContent-130896484. Applied change to temp map.
      2021-05-15T13:05:58.623Z verbose hostd[AEC2B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-56-5859 user=root] RecordOp ASSIGN: info, haTask--vim.ServiceInstance.retrieveContent-130896484. Applied change to temp map.
      2021-05-15T13:05:58.625Z verbose hostd[AE40B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-56-585a user=root] RecordOp ASSIGN: info, haTask--vim.SessionManager.logout-130896485. Applied change to temp map.
      2021-05-15T13:05:58.625Z verbose hostd[AE40B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-56-585a user=root] RecordOp REMOVE: sessionList["5263dcbb-1baf-7a5a-ab7b-ea07e6499e50"], ha-sessionmgr. Applied change to temp map.
      2021-05-15T13:05:58.625Z verbose hostd[AE40B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-56-585a user=root] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
      2021-05-15T13:05:58.625Z info hostd[AE40B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=vim-cmd-56-585a user=root] Event 763 : User root@127.0.0.1 logged out (login time: Saturday, 15 May, 2021 13:05:58, number of API invocations: 0, user agent: VMware-client/6.5.0)
      2021-05-15T13:05:58.625Z verbose hostd[AE40B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-56-585a user=root] RecordOp ASSIGN: info, haTask--vim.SessionManager.logout-130896485. Applied change to temp map.
      
  • Reading a pending message:
    Accepted password for user root from 127.0.0.1
    2021-05-15T13:06:32.389Z verbose hostd[B040B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-d0-588a] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
    2021-05-15T13:06:32.389Z info hostd[B040B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=vim-cmd-d0-588a] Event 767 : User root@127.0.0.1 logged in as VMware-client/6.5.0
    2021-05-15T13:06:32.389Z verbose hostd[B040B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-d0-588a] RecordOp ADD: sessionList["52967fcb-195c-96b3-429b-4762cbb5fdbd"], ha-sessionmgr. Applied change to temp map.
    2021-05-15T13:06:32.453Z verbose hostd[BBC2B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-d0-5898 user=root] RecordOp ASSIGN: info, haTask--vim.ServiceInstance.retrieveContent-130896487. Applied change to temp map.
    2021-05-15T13:06:32.453Z verbose hostd[BBC2B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-d0-5898 user=root] RecordOp ASSIGN: info, haTask--vim.ServiceInstance.retrieveContent-130896487. Applied change to temp map.
    2021-05-15T13:06:32.455Z verbose hostd[BB81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-d0-5899 user=root] RecordOp ASSIGN: info, haTask--vim.SessionManager.logout-130896488. Applied change to temp map.
    2021-05-15T13:06:32.455Z verbose hostd[BB81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-d0-5899 user=root] RecordOp REMOVE: sessionList["52967fcb-195c-96b3-429b-4762cbb5fdbd"], ha-sessionmgr. Applied change to temp map.
    2021-05-15T13:06:32.455Z verbose hostd[BB81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-d0-5899 user=root] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
    2021-05-15T13:06:32.455Z info hostd[BB81B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=vim-cmd-d0-5899 user=root] Event 768 : User root@127.0.0.1 logged out (login time: Saturday, 15 May, 2021 13:06:32, number of API invocations: 0, user agent: VMware-client/6.5.0)
    2021-05-15T13:06:32.456Z verbose hostd[BB81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-d0-5899 user=root] RecordOp ASSIGN: info, haTask--vim.SessionManager.logout-130896488. Applied change to temp map.
  • A cron event of the automatic configuration backup:
    2021-05-15T13:06:31.559Z info hostd[AE40B70] [Originator@6876 sub=SysCommandPosix] ForkExec(/sbin/backup.sh) 181092
    2021-05-15T13:06:32.798Z info hostd[AE40B70] [Originator@6876 sub=Hostsvc.HostConfigSyncManager] Backup succeeded
  • Powering up a moved virtual machine, leading up to a cancelable task and the message:
    Accepted password for user root from 127.0.0.1
    2021-05-15T13:06:26.505Z info hostd[B081B70] [Originator@6876 sub=Vimsvc opID=vim-cmd-8f-585d] [Auth]: User root
    2021-05-15T13:06:26.505Z verbose hostd[B081B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-585d] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
    2021-05-15T13:06:26.505Z info hostd[B081B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=vim-cmd-8f-585d] Event 764 : User root@127.0.0.1 logged in as VMware-client/6.5.0
    2021-05-15T13:06:26.505Z verbose hostd[B081B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-585d] RecordOp ADD: sessionList["52165943-fe83-da06-513a-6c2c38b0e470"], ha-sessionmgr. Applied change to temp map.
    2021-05-15T13:06:26.548Z info hostd[AE40B70] [Originator@6876 sub=Vimsvc.TaskManager opID=vim-cmd-8f-586a user=root] Task Created : haTask-25-vim.VirtualMachine.powerOn-130896486
    2021-05-15T13:06:26.548Z verbose hostd[AE40B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-586a user=root] RecordOp ADD: recentTask["haTask-25-vim.VirtualMachine.powerOn-130896486"], 25. Sent notification immediately.
    2021-05-15T13:06:26.548Z verbose hostd[AE40B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-586a user=root] RecordOp ADD: recentTask["haTask-25-vim.VirtualMachine.powerOn-130896486"], ha-taskmgr. Applied change to temp map.
    2021-05-15T13:06:26.548Z verbose hostd[B940B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-586a user=root] RecordOp ASSIGN: info, haTask-25-vim.VirtualMachine.powerOn-130896486. Applied change to temp map.
    2021-05-15T13:06:26.551Z verbose hostd[B940B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-586a user=root] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
    2021-05-15T13:06:26.551Z info hostd[B940B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=vim-cmd-8f-586a user=root] Event 765 : archiveteam-warrior-v3-20171013 on host ESXi-X10SRH-CF in ha-datacenter is starting
    2021-05-15T13:06:26.551Z info hostd[B940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013/archiveteam-warrior-v3-20171013.vmx opID=vim-cmd-8f-586a user=root] State Transition (VM_STATE_OFF -> VM_STATE_POWERING_ON)
    2021-05-15T13:06:26.551Z info hostd[B940B70] [Originator@6876 sub=Libs opID=vim-cmd-8f-586a user=root] SIOC: SIOC is notified not to start injector
    2021-05-15T13:06:26.552Z verbose hostd[B940B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-586a user=root] RecordOp ASSIGN: disabledMethod, 25. Sent notification immediately.
    2021-05-15T13:06:26.552Z verbose hostd[B940B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-586a user=root] RecordOp ASSIGN: info.cancelable, haTask-25-vim.VirtualMachine.powerOn-130896486. Applied change to temp map.
    2021-05-15T13:06:26.552Z verbose hostd[B940B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-586a user=root] RecordOp ASSIGN: info.cancelable, haTask-25-vim.VirtualMachine.powerOn-130896486. Applied change to temp map.
    2021-05-15T13:06:26.553Z info hostd[B940B70] [Originator@6876 sub=Libs opID=vim-cmd-8f-586a user=root] DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
    2021-05-15T13:06:26.553Z info hostd[B940B70] [Originator@6876 sub=Libs opID=vim-cmd-8f-586a user=root] Could not expand environment variable HOME.
    2021-05-15T13:06:26.553Z info hostd[B940B70] [Originator@6876 sub=Libs opID=vim-cmd-8f-586a user=root] DictionaryLoad: Cannot open file "~/.vmware/config": No such file or directory.
    2021-05-15T13:06:26.556Z info hostd[B940B70] [Originator@6876 sub=Libs opID=vim-cmd-8f-586a user=root] Starting vmx as /bin/vmx
    2021-05-15T13:06:26.556Z info hostd[B940B70] [Originator@6876 sub=Libs opID=vim-cmd-8f-586a user=root] Starting vmx as /bin/vmx
    2021-05-15T13:06:26.557Z info hostd[B940B70] [Originator@6876 sub=vm:VigorExecVMXExCommon: VM /vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013/archiveteam-warrior-v3-20171013.vmx opID=vim-cmd-8f-586a user=root] in directory /vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013
    2021-05-15T13:06:26.557Z info hostd[B940B70] [Originator@6876 sub=vm:VigorExecVMXExCommon: Exec()'ing /bin/vmx /vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013/archiveteam-warrior-v3-20171013.vmx opID=vim-cmd-8f-586a user=root]
    2021-05-15T13:06:26.557Z info hostd[B940B70] [Originator@6876 sub=Libs opID=vim-cmd-8f-586a user=root] Vigor: VMKernel_ForkExec(/bin/vmx, detached=1): status=0 pid=181085
    2021-05-15T13:06:26.611Z verbose hostd[B081B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: info.cancelable, haTask-25-vim.VirtualMachine.powerOn-130896486. Applied change to temp map.
    2021-05-15T13:06:26.625Z verbose hostd[A0E7B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: info.progress, haTask-25-vim.VirtualMachine.powerOn-130896486. Applied change to temp map.
    2021-05-15T13:06:26.798Z verbose hostd[BBC2B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
    2021-05-15T13:06:26.798Z info hostd[BBC2B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 766 : Message on archiveteam-warrior-v3-20171013 on ESXi-X10SRH-CF in ha-datacenter: This virtual machine might have been moved or copied.
    --> In order to configure certain management and networking features, VMware ESX needs to know if this virtual machine was moved or copied.
    -->
    --> If you don't know, answer "I Co_pied It".
    -->
    -->
    2021-05-15T13:06:26.798Z verbose hostd[BBC2B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: runtime.question, 25. Sent notification immediately.
    2021-05-15T13:06:26.799Z verbose hostd[BBC2B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: summary.runtime.question, 25. Sent notification immediately.
    2021-05-15T13:06:26.799Z verbose hostd[BBC2B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: disabledMethod, 25. Sent notification immediately.
  • The time out while waiting for the answer to the message immediately leads to the actual power on state of the virtual machine:
    2021-05-15T13:10:27.043Z verbose hostd[A0E7B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: info.progress, haTask-25-vim.VirtualMachine.powerOn-130896486. Applied change to temp map.
    2021-05-15T13:10:27.053Z verbose hostd[B040B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: runtime.question, 25. Sent notification immediately.
    2021-05-15T13:10:27.053Z verbose hostd[B040B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: summary.runtime.question, 25. Sent notification immediately.
    2021-05-15T13:10:27.053Z verbose hostd[B040B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: disabledMethod, 25. Sent notification immediately.
    2021-05-15T13:10:27.053Z verbose hostd[B040B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
    2021-05-15T13:10:27.053Z info hostd[B040B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 769 : Message on archiveteam-warrior-v3-20171013 on ESXi-X10SRH-CF in ha-datacenter: This virtual machine might have been moved or copied.
    --> In order to configure certain management and networking features, VMware ESX needs to know if this virtual machine was moved or copied.
    -->
    --> If you don't know, answer "I Co_pied It".
    -->
    -->
    2021-05-15T13:10:27.062Z info hostd[AE81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013/archiveteam-warrior-v3-20171013.vmx] Answered question 5970112
    2021-05-15T13:10:27.062Z info hostd[AE81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013/archiveteam-warrior-v3-20171013.vmx] Answered question 5970112
    2021-05-15T13:10:27.079Z info hostd[AE81B70] [Originator@6876 sub=Hostsvc] Decremented SIOC Injector Flag2
    2021-05-15T13:10:27.080Z verbose hostd[AE81B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
    2021-05-15T13:10:27.080Z info hostd[AE81B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 770 : archiveteam-warrior-v3-20171013 on  ESXi-X10SRH-CF in ha-datacenter is powered on
    2021-05-15T13:10:27.080Z info hostd[AE81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013/archiveteam-warrior-v3-20171013.vmx] State Transition (VM_STATE_POWERING_ON -> VM_STATE_ON)
  • The loggoff of the vim-cmd that tried to power on the moved virtual machine. It ends when the message got the default answer, and the virtual machine fully powered up:
    2021-05-15T13:10:27.116Z info hostd[AE81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/6097a4eb-6c6e4c76-46d3-0cc47aaa9742/base/archiveteam/archiveteam-warrior-v3-20171013/archiveteam-warrior-v3-20171013.vmx] Skip a duplicate transition to: VM_STATE_ON
    2021-05-15T13:10:27.116Z verbose hostd[AE81B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: runtime.featureRequirement, 25. Sent notification immediately.
    2021-05-15T13:10:27.123Z verbose hostd[AE81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-5d23 user=root] RecordOp ASSIGN: info, haTask--vim.ServiceInstance.retrieveContent-130896490. Applied change to temp map.
    2021-05-15T13:10:27.123Z verbose hostd[AE81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-5d23 user=root] RecordOp ASSIGN: info, haTask--vim.ServiceInstance.retrieveContent-130896490. Applied change to temp map.
    2021-05-15T13:10:27.125Z verbose hostd[AE81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-5d24 user=root] RecordOp ASSIGN: info, haTask--vim.SessionManager.logout-130896491. Applied change to temp map.
    2021-05-15T13:10:27.125Z verbose hostd[AE81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-5d24 user=root] RecordOp REMOVE: sessionList["52165943-fe83-da06-513a-6c2c38b0e470"], ha-sessionmgr. Applied change to temp map.
    2021-05-15T13:10:27.125Z verbose hostd[AE81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-5d24 user=root] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
    2021-05-15T13:10:27.125Z info hostd[AE81B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=vim-cmd-8f-5d24 user=root] Event 771 : User root@127.0.0.1 logged out (login time: Saturday, 15 May, 2021 13:06:26, number of API invocations: 0, user agent: VMware-client/6.5.0)
    2021-05-15T13:10:27.125Z verbose hostd[AE81B70] [Originator@6876 sub=PropertyProvider opID=vim-cmd-8f-5d24 user=root] RecordOp ASSIGN: info, haTask--vim.SessionManager.logout-130896491. Applied change to temp map.

Back to answering the question

Let’s first repeat the help:

# vim-cmd help vmsvc/message
Usage: message vmid [messageId] [messageChoice]

Replies to the current pending question on the vm.

Given this message for virtual machine having a vmid of 25 awaiting an answer to messageId number 6233874:

# vim-cmd vmsvc/message 25
Virtual machine message 6233874:
This virtual machine might have been moved or copied. In order to configure certain management and networking features, VMware ESX needs to know if this virtual machine was moved or copied. If you don't know, answer "I Copied It". 
   0. button.uuid.cancel (Cancel)
   1. button.uuid.movedTheVM (I Moved It)
   2. button.uuid.copiedTheVM (I Copied It) [default]

You can answer the question in a separate console/ssh session with either of these:

  • Cancel: vim-cmd vmsvc/message 25 6233874 0 where 25 is the vmid of the virtual machine and 6233874 is the messageId of the message.
    • The Virtual Machine will not power on and the power.on command fails:
      # vim-cmd vmsvc/power.on 25
      Powering on VM:
      Power on fail
  • The virtual machine was moved vim-cmd vmsvc/message 25 6233874 1 where 25 is the vmid of the virtual machine and 6233874 is the messageId of the message.
    • The Virtual Machine will power on and the power.on command succeeds:
      # vim-cmd vmsvc/power.on 25
      Powering on VM:
    • The .vmx file of the virtual machine will change these fields:
      • uuid.location
      • cleanShutdown (for running virtual machines, this always has value "FALSE"; for cleanly shutdown machines the value will be "TRUE")
      • sched.swap.derivedName with a new value for the .vswp file.
      • softPowerOff(for running virtual machines, this always has the value "FALSE"; for cleanly shutdown machines the value will be "TRUE")
  • 2, or wait for more than four (4) minutes:
    • The Virtual Machine will power on, and the power.on command succeeds::
      # vim-cmd vmsvc/power.on 25
      Powering on VM:
    • The .vmx file of the virtual machine will change these fields (you can see this below the signature or in this gist [Archive.is]):
      • uuid.location
      • uuid.bios (which for Windows system will often require a new license key)
      • ethernet0.generatedAddress
      • cleanShutdown (for running virtual machines, this always has value "FALSE"; for cleanly shutdown machines the value will be "TRUE")
      • sched.swap.derivedName with a new value for the .vswp file.
      • softPowerOff(for running virtual machines, this always has the value "FALSE"; for cleanly shutdown machines the value will be "TRUE")

Generating the “answer” command

I prefer to answer these questions manually, but use this fragment to generate an answer command that selects the “Moved” answer:

    message=`vim-cmd vmsvc/message ${vmid}`
    echo "message: $message"
    messageId=`echo "$message" | sed -n -E -e 's/^Virtual machine message (.*):$/\1/p'`
    movedAnswerId=`echo "$message" | sed -n -E -e 's/^ +([[:digit:]])\. button.uuid.* Moved.*$/\1/p'`
    if [[ "$movedAnswerId" == 1 ]]; then
        echo "vim-cmd vmsvc/message $vmid $messageId $movedAnswerId"
    fi

It is based on these regular expression experiments:

–jeroen

Read the rest of this entry »

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 »

Overriding some DNS entries for internal networks

Posted by jpluimers on 2022/01/27

Based on [Wayback] domain name system – Overriding some DNS entries in BIND for internal networks – Server Fault and some further reading, there seem to be two ways used in these scenarios:

I wonder how that would interact best with Pi-Hole based solutions. Would it be best to have your local network use the Pi-Hole server, then have the Pi-Hole server obtain the DNS information it cannot resolve through one of the above solutions? Or would other solutions work better?

So here are a few links:

Pi-Hole seems not interested in RPZ: [Wayback] Implement Response Zone Policies (NXDOMAIN) for end-user performance increase – Feature Requests / Implemented – Pi-hole Userspace

Pi-Hole default blacklist is mentioned in [Wayback/Archive.is] pi-hole/basic-install.sh at master · pi-hole/pi-hole (look for adlistFile which defaults to [Wayback/Archive.is] StevenBlack/hosts: 🔒 Consolidating and extending hosts files from several well-curated sources. Optionally pick extensions for porn, social media, and other categories.).

Since I need this for ESXi: [Wayback/Archive.is] Let’s Encrypt SSL for ESXi

–jeroen

Posted in *nix, *nix-tools, bind-named, DNS, Internet, Linux, Power User | Leave a Comment »

In life, including working life “slow is smooth, and smooth is fast.”

Posted by jpluimers on 2022/01/26

I’ve been agile all my (not just programming) life, and only figured out this century that there is a vocabulary for that, containing the words agile, extreme programming, feature-driven and many more.

Now with the passing of the years, I also realise I have been trying to do “slow and smooth” all my life, and that with age (and less adrenaline) this becomes easier and easier.

I think “slow and smooth” goes well with “agile”, specially when you keep the focus on “doing things right” (and trying to do them right the first time, and keeping it right in incremental steps).

It often reminds me of the Dutch phrase “heeft u haast, gaat dan zitten” which often is attributed to be part of the many Chinese proverbs. It roughly translates to “when in a hurry, take a seat”, and suggests to take a step back and think when under pressure. Maybe this English version of a Chinese proverb comes close: “When you are in a hurry, the horse holds back”.

For is it is intriguing that mainly Chinese, but in a broader sense Asian, proverbs play such an important role, whereas Western proverbs get less and less important. Informal knowledge seems to diminish in Western culture, which I think is a pity.

Maybe all these vocabulary things that started  to make sense way after my puberty also have to do with being diagnosed autistic at 50. That too started a lot of puzzle-pieces to suddenly make sense.

Below the links that inspired me to make this blog post in the first place:

–jeroen

Read the rest of this entry »

Posted in Agile, Conference Topics, Conferences, Development, Event, LifeHacker, Power User, Software Development | Leave a Comment »

 
%d bloggers like this: