#esxi — Public Fediverse posts

@PurpleJillybeans you #NerdSniped me with this, so down the 🐰🕳️ I went… 🤬😩

I was going to suggest that you reach out to the person who wrote the blog post below, but I see in the comments that he’s already been asked to upload the install media to #InternetArchive and has declined

the article might be of interest to you anyway – he lists his install configs & also links to video playlists of installations of lots of (all? 🤔) versions…

…which are on the official VMware YT channel 🤔

ah, OK. it looks like he currently works for #Broadcom, so that’s probably a dead end as far as getting the installers that he has (access to) preserved on IA 😕
 
 
How to install all versions of ESX and ESXi in VM?

https://williamlam.com/2023/04/how-to-install-all-versions-of-esx-and-esxi-in-vm.html
 
 
it’s so frustrating that vendors don’t just make this available as part of preserving their own product history, if nothing else. I sincerely doubt that anyone’s going to be downloading & running ESX 1.5 in production 20+ years later to avoid buying the current version 🤪

what I’d really like to see is legislation that mandates that all no-longer-supported software be made available publicly & released into the commons, but given the US is allergic to regulating just about anything I don’t see that happening any time soon 😩

#DigiPres
#VMware #GSX #ESX #ESXi
#VintageSoftware
#RetroComputing
  

@PurpleJillybeans you #NerdSniped me with this, so down the 🐰🕳️ I went… 🤬😩

I was going to suggest that you reach out to the person who wrote the blog post below, but I see in the comments that he’s already been asked to upload the install media to #InternetArchive and has declined

the article might be of interest to you anyway – he lists his install configs & also links to video playlists of installations of lots of (all? 🤔) versions…

…which are on the official VMware YT channel 🤔

ah, OK. it looks like he currently works for #Broadcom, so that’s probably a dead end as far as getting the installers that he has (access to) preserved on IA 😕
 
 
How to install all versions of ESX and ESXi in VM?

https://williamlam.com/2023/04/how-to-install-all-versions-of-esx-and-esxi-in-vm.html
 
 
it’s so frustrating that vendors don’t just make this available as part of preserving their own product history, if nothing else. I sincerely doubt that anyone’s going to be downloading & running ESX 1.5 in production 20+ years later to avoid buying the current version 🤪

what I’d really like to see is legislation that mandates that all no-longer-supported software be made available publicly & released into the commons, but given the US is allergic to regulating just about anything I don’t see that happening any time soon 😩

#DigiPres
#VMware #GSX #ESX #ESXi
#VintageSoftware
#RetroComputing
  

Year of free #HPE software a “step in the correct direction” in #VMware rivalry
At #HPEDiscover, HPE announced customers could use its “HPE Morpheus Software—#VMEssentials” offering for free for “up to one year." HPE’s website describes its #virtualization platform as a “VMware alternative.” It includes a hardware virtual machine (HVM) hypervisor and unified management and lets users “manage VMware #ESXi and HVM clusters from one console and migrate when you’re ready.”
https://arstechnica.com/information-technology/2026/06/hpe-tempts-vmware-users-partners-with-year-of-free-virtualization-software/

Year of free #HPE software a “step in the correct direction” in #VMware rivalry
At #HPEDiscover, HPE announced customers could use its “HPE Morpheus Software—#VMEssentials” offering for free for “up to one year." HPE’s website describes its #virtualization platform as a “VMware alternative.” It includes a hardware virtual machine (HVM) hypervisor and unified management and lets users “manage VMware #ESXi and HVM clusters from one console and migrate when you’re ready.”
https://arstechnica.com/information-technology/2026/06/hpe-tempts-vmware-users-partners-with-year-of-free-virtualization-software/

📢 VECT 2.0 : un ransomware RaaS qui détruit irrémédiablement les fichiers par défaut de conception
📝 ## 🔍 Contexte

Publié le 28 avril 2026 par Check Point Research (CPR), cet article présente une analys...
📖 cyberveille : https://cyberveille.ch/posts/2026-04-29-vect-2-0-un-ransomware-raas-qui-detruit-irremediablement-les-fichiers-par-defaut-de-conception/
🌐 source : https://research.checkpoint.com/2026/vect-ransomware-by-design-wiper-by-accident/
#ChaCha20 #ESXi #Cyberveille

СХД, ESXi и LUN ID: теория, практика и немного боли

Хабр, привет! На связи центр компетенций VMware "Инфосистемы Джет". В этой статье расскажем о тонкостях подключения LUN (логических номеров устройств) из системы хранения данных (СХД) к хостам ESXi, которые управляются через vCenter Server. За прошлый год мы не раз сталкивались с проблемами у заказчиков, которых можно было бы избежать при правильной настройке. Как именно — расскажем ниже, не забывая и про теорию.

https://habr.com/ru/companies/jetinfosystems/articles/1013566/

#vmware #esxi #lun #хост #логи #настройки

СХД, ESXi и LUN ID: теория, практика и немного боли

Хабр, привет! На связи центр компетенций VMware "Инфосистемы Джет". В этой статье расскажем о тонкостях подключения LUN (логических номеров устройств) из системы хранения данных (СХД) к хостам ESXi, которые управляются через vCenter Server. За прошлый год мы не раз сталкивались с проблемами у заказчиков, которых можно было бы избежать при правильной настройке. Как именно — расскажем ниже, не забывая и про теорию.

https://habr.com/ru/companies/jetinfosystems/articles/1013566/

#vmware #esxi #lun #хост #логи #настройки

СХД, ESXi и LUN ID: теория, практика и немного боли

Хабр, привет! На связи центр компетенций VMware "Инфосистемы Джет". В этой статье расскажем о тонкостях подключения LUN (логических номеров устройств) из системы хранения данных (СХД) к хостам ESXi, которые управляются через vCenter Server. За прошлый год мы не раз сталкивались с проблемами у заказчиков, которых можно было бы избежать при правильной настройке. Как именно — расскажем ниже, не забывая и про теорию.

https://habr.com/ru/companies/jetinfosystems/articles/1013566/

#vmware #esxi #lun #хост #логи #настройки

Here's how to install VMware ESX

https://thedxt.ca/2025/10/install-vmware-esx/

#ESX #VMware #vExpert #ESXi

Here's how to install VMware ESX

https://thedxt.ca/2025/10/install-vmware-esx/

#ESX #VMware #vExpert #ESXi

LockBit 5.0 als neue Ransomaware-as-a-Service

Die neue LockBit-Variante in Version 5 funktioniert nun auch plattformübergreifend in Windows, Linux und VMware-ESXi-Umgebungen. TrendMicro hat die neuen Angriffstechniken analysiert und stellt fest:
"Die Windows-, Linux- und ESXi-Varianten von LockBit 5.0 unterstreichen, dass kein Betriebssystem und keine Plattform als sicher vor modernen Ransomware-Kampagnen angesehen werden kann."
Damit ermögliche die neue Crossplattform-Strategie Angreifenden gleichzeitige Angriffe auf das gesamte Unternehmensnetzwerk.
Die Windows-Variante von LockBit 5.0 nutze eine starke Verschleierung und Komprimierung, indem sie ihre Payload über DLL-Reflexion lade und gleichzeitig Anti-Analyse-Techniken implementiere. Die Linux-Variante verfüge über ähnliche Funktionen mit Befehlszeilenoptionen für bestimmte Verzeichnisse und Dateitypen. Die ESXi-Variante ziele speziell auf die Virtualisierungsinfrastruktur von VMware ab und sei entwickelt worden, um virtuelle Maschinen zu verschlüsseln.
Die neuen Varianten verwenden zufällige 16-stellige Dateierweiterungen, verfügen über eine Umgehung des russischsprachigen Systems und löschen nach der Verschlüsselung die Ereignisprotokolle.
"Die starke Verschleierung dieser neuen Varianten verzögert die Entwicklung von Erkennungssignaturen erheblich, während technische Verbesserungen wie entfernte Infektionsmarker, schnellere Verschlüsselung und verbesserte Umgehungsmöglichkeiten LockBit 5.0 deutlich gefährlicher machen als seine Vorgänger."

https://www.trendmicro.com/en_gb/research/25/i/lockbit-5-targets-windows-linux-esxi.html

#infosec #ransomware #raas #windows #linux #esxi #vmware #lockbit #BeDiS

Released: MITRE ATT&CK v17.0, now with ESXi attack TTPs https://www.helpnetsecurity.com/2025/04/23/released-mitre-attck-v17-0-now-with-esxi-attack-ttps/ #incidentresponse #attacklifecycle #threatmodeling #attacktools #MITREATT&CK #Don'tmiss #Hotstuff #MITRE #News #ESXi

Released: MITRE ATT&CK v17.0, now with ESXi attack TTPs https://www.helpnetsecurity.com/2025/04/23/released-mitre-attck-v17-0-now-with-esxi-attack-ttps/ #incidentresponse #attacklifecycle #threatmodeling #attacktools #MITREATT&CK #Don'tmiss #Hotstuff #MITRE #News #ESXi

Released: MITRE ATT&CK v17.0, now with ESXi attack TTPs https://www.helpnetsecurity.com/2025/04/23/released-mitre-attck-v17-0-now-with-esxi-attack-ttps/ #incidentresponse #attacklifecycle #threatmodeling #attacktools #MITREATT&CK #Don'tmiss #Hotstuff #MITRE #News #ESXi

Released: MITRE ATT&CK v17.0, now with ESXi attack TTPs https://www.helpnetsecurity.com/2025/04/23/released-mitre-attck-v17-0-now-with-esxi-attack-ttps/ #incidentresponse #attacklifecycle #threatmodeling #attacktools #MITREATT&CK #Don'tmiss #Hotstuff #MITRE #News #ESXi

VMware Cloud Foundation のコンポーネント情報 (BOM) とサポート期間の概要
https://qiita.com/sanjushi003/items/1883cf4c77128ab3ebe4?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Broadcom #vmware #ESXi #NSX #vcf

I've successfully migrated my #ESXi #homelab server over to #Proxmox after surprisingly a little bit of (unexpected) trouble - haven't really even moved all of my old services or #Kubernetes cluster back into it, but I'd say the most challenging part I was expecting which is #TrueNAS has not only been migrated, but also upgraded from TrueNAS Core 12 to TrueNAS Scale 24.10 (HUGE jump, I know).

Now then. I'm thinking what's the best way to move forward with this, now that I have 2 separate nodes running Proxmox. There are multiple things to consider. I suppose I could cluster 'em up, so I can manage both of them under one roof but from what I can tell, clustering on Proxmox works the same way as you would with Kubernetes clusters like #RKE2 or #K3s whereby you'd want at least 3 nodes, if not just 1. I can build another server, I have the hardware parts for it, but I don't think I'd want to take up more space I already do and have 3 PCs running 24/7.

I'm also thinking of possibly joining my 2 RKE 2 Clusters (1 on each node) into 1... but I'm not sure how I'd go about it having only 2 physical nodes. Atm, each cluster has 1 Master node and 3 Worker nodes (VMs ofc). Having only 2 physical nodes, I'm not sure how I'd spread the number of master/worker nodes across the 2. Maintaining only 1 (joined) cluster would be helpful though, since it'd solve my current issue of not being able to use one of them to publish services online using #Ingress "effectively", since I could only port forward the standard HTTP/S ports to only a single endpoint (which means the secondary cluster will use a non-standard port instead i.e. 8443).

This turned out pretty long - but yea... any ideas what'd be the "best" way of moving forward if I only plan to retain 2 Proxmox nodes - Proxmox wise, and perhaps even Kubernetes wise?

I've successfully migrated my #ESXi #homelab server over to #Proxmox after surprisingly a little bit of (unexpected) trouble - haven't really even moved all of my old services or #Kubernetes cluster back into it, but I'd say the most challenging part I was expecting which is #TrueNAS has not only been migrated, but also upgraded from TrueNAS Core 12 to TrueNAS Scale 24.10 (HUGE jump, I know).

Now then. I'm thinking what's the best way to move forward with this, now that I have 2 separate nodes running Proxmox. There are multiple things to consider. I suppose I could cluster 'em up, so I can manage both of them under one roof but from what I can tell, clustering on Proxmox works the same way as you would with Kubernetes clusters like #RKE2 or #K3s whereby you'd want at least 3 nodes, if not just 1. I can build another server, I have the hardware parts for it, but I don't think I'd want to take up more space I already do and have 3 PCs running 24/7.

I'm also thinking of possibly joining my 2 RKE 2 Clusters (1 on each node) into 1... but I'm not sure how I'd go about it having only 2 physical nodes. Atm, each cluster has 1 Master node and 3 Worker nodes (VMs ofc). Having only 2 physical nodes, I'm not sure how I'd spread the number of master/worker nodes across the 2. Maintaining only 1 (joined) cluster would be helpful though, since it'd solve my current issue of not being able to use one of them to publish services online using #Ingress "effectively", since I could only port forward the standard HTTP/S ports to only a single endpoint (which means the secondary cluster will use a non-standard port instead i.e. 8443).

This turned out pretty long - but yea... any ideas what'd be the "best" way of moving forward if I only plan to retain 2 Proxmox nodes - Proxmox wise, and perhaps even Kubernetes wise?

For some reason, I feel like the #RKE2 cluster on my #Proxmox node is more fragile than the cluster on my #ESXi node. Like, on the latter, I can simply shutdown and boot the nodes however I want just like that and everything seems to just get in a working state on tis own. On the former, for some reason, things seem to boot in a non-running start with various status like Unknown, CrashLoopBackOff, etc. - some gets solved by me deleting/restarting the pods, some though will require me to run the killall script and reboot the entire node. Pretty weird, when both clusters were deployed/configured the exact same way and runs the exact same version.

For some reason, I feel like the #RKE2 cluster on my #Proxmox node is more fragile than the cluster on my #ESXi node. Like, on the latter, I can simply shutdown and boot the nodes however I want just like that and everything seems to just get in a working state on tis own. On the former, for some reason, things seem to boot in a non-running start with various status like Unknown, CrashLoopBackOff, etc. - some gets solved by me deleting/restarting the pods, some though will require me to run the killall script and reboot the entire node. Pretty weird, when both clusters were deployed/configured the exact same way and runs the exact same version.

I'm gonna try and install #Proxmox today on my mini PC and set up a second #Kubernetes #RKE2 cluster in my #homelab.

What I plan to do, not knowing if possible or not:

- Install Proxmox. I'd love if I had 2 identical SSDs lying around so I could set up RAID1 but I don't, so likely the OS and VM storage will just be that 1x 1TB NVME SSD. I'm hoping the onboard 2.5G LAN port would just work, despite my hardware being very much not server hardware.

- Try and see if I could carry over and reuse my vmdk + vmx VM templates I made on my main #ESXi server, on the new Proxmox server.

- Prepare 5 #RockyLinux VMs to set up 1 login node, 1 master node, and 3 worker nodes.

- Setup and deploy the cluster environment using my Orked scripts (and test them once again in the process).

- If all is done and works as expected, I'll start migrating some stuffs from the first cluster to the second cluster so that loads on the former are lighten up a bit.

🔗 https://github.com/irfanhakim-as/orked

Домашняя лаба. Как собрать домашнюю инфраструктуру мечты

Мой первый опыт на Хабре получился не очень положительным, и, признаюсь, до сих пор смотря на комментарии и оценки, мне стыдно и больно где-то внутри. Потому в имя исправления ошибок молодости решил написать серию статей о том, как дома собрать свою "идеальную" хранилку, или сервак, или мини облако. Поделюсь опытом, своими знаниями и пониманием, а также мыслями, которые могут помочь выполняя похожую задачу для себя.

https://habr.com/ru/articles/808751/

#NAS #plexmediaserver #docker #ubuntu #zfsonlinux #synology #esxi #diy #лаба #домашний_сервер

#proxmox and #QEMUKVM gonna get a whoooooole lotta new users now #esxi is dead https://kb.vmware.com/s/article/2107518?lang=en_US

#proxmox and #QEMUKVM gonna get a whoooooole lotta new users now #esxi is dead https://kb.vmware.com/s/article/2107518?lang=en_US

Increíble que tarde más en cargar la mierda de #iDRAC que poner un host #ESXi en mantenimiento y parcharlo.

Fucking #DELL

Probleme mit #Microsoft #Windows #Server 2022 (KB5022842) unter #VMware #vSphere #ESXi 7.0 - Mögliche Lösungen und Workarounds:
https://varni.de/2023/vmware/probleme-mit-windows-server-2022-kb5022842-unter-vmware-esxi/
#vExpert #vCommunity

Probleme mit #Microsoft #Windows #Server 2022 (KB5022842) unter #VMware #vSphere #ESXi 7.0 - Mögliche Lösungen und Workarounds:
https://varni.de/2023/vmware/probleme-mit-windows-server-2022-kb5022842-unter-vmware-esxi/
#vExpert #vCommunity

This week's newsletter is hot off the press, get it here: https://opalsec.substack.com/p/soc-goulash-weekend-wrap-up-b16

The #ESXiArgs escapades have gone from bad to okay and back to bad again, after attackers revised their encryption routine to bypass CISA's recovery script, and launched a 2nd wave of attacks that resulted in the reinfection of hundreds of hosts. Worst yet - we don't know how they're doing it, as the OpenSLP service (believed to be their method of ingress) has been disabled in a number of reported infections.

PowerShell isn't dead - The DFIR Report published their analysis of an apparent attack by Iran's Oilrig/APT34, whose initial infection relied exclusively on PowerShell and remained undetected for a significant period of time.

Proofpoint have unveiled #TA866, a savvy threat group that leverages the 404 Traffic Distribution System and little known AutoHotKey scripting language to cherry pick their targets.

#RedTeam members might find the BokuLoader Reflective Loader for #CobaltStrike useful in their next engagements, as well as #LocalPotato - the latest PrivEsc technique to join the Potato family.

#BlueTeam - check out a list of resources that popped up last week to help analyse #ASyncRAT malware and infections, as well as some helpful how-tos on hunting IIS backdoors and DLL abuse techniques

Happy reading, and happy Monday!

https://opalsec.substack.com/p/soc-goulash-weekend-wrap-up-b16

#infosec #CyberAttack #Hacked #cyber #news #cybernews #infosecnews #informationsecurity #cybersecurity #hacking #security #technology #hacker #vulnerability #vulnerabilities #malware #ransomware #dfir #redteam #soc #threatintel #threatintelligence #vmware #ESXi

This week's newsletter is hot off the press, get it here: https://opalsec.substack.com/p/soc-goulash-weekend-wrap-up-b16

The #ESXiArgs escapades have gone from bad to okay and back to bad again, after attackers revised their encryption routine to bypass CISA's recovery script, and launched a 2nd wave of attacks that resulted in the reinfection of hundreds of hosts. Worst yet - we don't know how they're doing it, as the OpenSLP service (believed to be their method of ingress) has been disabled in a number of reported infections.

PowerShell isn't dead - The DFIR Report published their analysis of an apparent attack by Iran's Oilrig/APT34, whose initial infection relied exclusively on PowerShell and remained undetected for a significant period of time.

Proofpoint have unveiled #TA866, a savvy threat group that leverages the 404 Traffic Distribution System and little known AutoHotKey scripting language to cherry pick their targets.

#RedTeam members might find the BokuLoader Reflective Loader for #CobaltStrike useful in their next engagements, as well as #LocalPotato - the latest PrivEsc technique to join the Potato family.

#BlueTeam - check out a list of resources that popped up last week to help analyse #ASyncRAT malware and infections, as well as some helpful how-tos on hunting IIS backdoors and DLL abuse techniques

Happy reading, and happy Monday!

https://opalsec.substack.com/p/soc-goulash-weekend-wrap-up-b16

#infosec #CyberAttack #Hacked #cyber #news #cybernews #infosecnews #informationsecurity #cybersecurity #hacking #security #technology #hacker #vulnerability #vulnerabilities #malware #ransomware #dfir #redteam #soc #threatintel #threatintelligence #vmware #ESXi