@lamw Any feedback on this? I'm thinking about submitting a Feature Request to have all vsish stuff exposed as an esxcli namespace... (at https://t.co/Ke3vFsQ84Z) Would you support this?
@lamw It's for monitoring purposes. We recently ran out of TCP/IP heap space memory, causing major hiccups. So I'm checking e.g. for all-time minimums below a threshold and allocation failures.
This as well as today's patch for #ESXi 9.0 fix the #VMEscape vulnerability that was recently demonstrated during #Pwn2own Berlin.
Nice to see that both patches are live-patchable! This really helps to get this rolled out quickly.
Yes, 9.1 ist considered an update to 9.0, but ... it introduces architectural changes and requires additional resources in the Management cluster (compared to 9.0). So, plan accordingly and read the upgrade guide completely and carefully: https://t.co/TjEjWwdav2
@lamw My fault (@ESXiPatches)๐... Well, you keep changing the version numbering scheme and confuse the hell out of every detection algorithm. ESXi 8.0.3 is Update 3, but 9.0.1 is *not* Update 1 ๐คท
New patch (U3g) for #VMware#ESXi 8.0 (and vCenter 8.0). Is this a fix for another super critical security vulnerability? Release notes not yet published...: ESXi: https://t.co/LGc2wdNBZs vCenter: https://t.co/3pUtKlqtIj
@alagoutte@virten@ESXiPatches The Imageprofile names still include "ESXi". Well, I don't care really. If they're going to change the name then I would rather expect something like "VCF Hypervisor" ;-)
And here comes the first patch for #VMware#ESXi 9.0. If you are looking for the release notes ... they are buried deep in the VCF documentation here: https://t.co/GPhjAOO8w1
Had to check the date when I woke up ... but it looks like #FreeESXi is now back with the latest 8.0 Update 3e release! ๐ It comes w/an embedded license w/same functions as Free Edition but no need to request key, which is nice!
๐ฟ https://t.co/2rShxGOaTm