#esxi — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #esxi, aggregated by home.social.
-
VMkatz: скрытая угроза для виртуальной инфраструктуры
В 2026 году был опубликован инструмент VMkatz. По функционалу он напоминает широко известный инструмент Mimikatz, но, в отличие от него, целью VMkatz является извлечение учетных данных напрямую из файлов виртуальных машин (снимков памяти и виртуальных дисков) без необходимости входа внутрь гостевых Windows-систем. VMkatz может работать с файлами виртуальных машин разных платформ, включая VMware ESXi, Microsoft Hyper-V, VirtualBox и QEMU/KVM.
https://habr.com/ru/companies/pt/articles/1057588/
#mimikatz #dfir #vmkatz #инструментарий #esxi #vmware_esxi #virtualbox
-
@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
-
@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
-
@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/ -
New instance, new #introduction, right?
Hi there! I'm Vito! 30-something self-taught computer #engineer ✨
I currently live in São Paulo, Brazil, with plans to move to Italy some time in the future. Maybe.I have a reeeally deep interest in #parsers, #interpreters & #compilers, but I'm also using my free time to build computers from scratch based on architectures from the 70's, 80's, and 90's, and some other projects, sometimes around #retrocomputing.
I'm usually using Macs (#Mac Studio Ultra/M4 #MacBook Pro <3) I also have a large #ESXi host hosting a lot of VMs and a "bare-metal" K8s cluster, but I've been a long-time user of #BSD and #Linux! <3
If I follow you, I will end up interacting with your toots in some way! Either boosting, replying, or favouriting them! Please do let me know in case any of that makes you uncomfortable!
Also feel free to let me know in case I missed a CW, Alt, or said something wrong or technically incorrect!
I think that's about it! Thanks for reading! Have a nice day! 🌻 :floofHeart:
-
New instance, new #introduction, right?
Hi there! I'm Vito! 30-something self-taught computer #engineer ✨
I currently live in São Paulo, Brazil, with plans to move to Italy some time in the future. Maybe.I have a reeeally deep interest in #parsers, #interpreters & #compilers, but I'm also using my free time to build computers from scratch based on architectures from the 70's, 80's, and 90's, and some other projects, sometimes around #retrocomputing.
I'm usually using Macs (#Mac Studio Ultra/M4 #MacBook Pro <3) I also have a large #ESXi host hosting a lot of VMs and a "bare-metal" K8s cluster, but I've been a long-time user of #BSD and #Linux! <3
If I follow you, I will end up interacting with your toots in some way! Either boosting, replying, or favouriting them! Please do let me know in case any of that makes you uncomfortable!
Also feel free to let me know in case I missed a CW, Alt, or said something wrong or technically incorrect!
I think that's about it! Thanks for reading! Have a nice day! 🌻 :floofHeart:
-
> The only alternative to #ESXi that I'm aware of is #Proxmox though
Proxmox is great, I use it at work and in the homelab :) There is also https://xcp-ng.org , never used it myself, but have never heard anything negative about them.
-
> The only alternative to #ESXi that I'm aware of is #Proxmox though
Proxmox is great, I use it at work and in the homelab :) There is also https://xcp-ng.org , never used it myself, but have never heard anything negative about them.
-
Talking to my IT guy at work looking for help with a #VMware issue I'm having. Since the broadcom takeover, I've been a bit interested in moving away from VMware. He suggested moving to #HyperV. The thought of having all of our VMs running on a Windows host is just anxiety inducing. As person who would gladly never touch another Microsoft product the rest of my life, the last thing I feel I'd want is to move to hyper-v. The only alternative to #ESXi that I'm aware of is #Proxmox though.
-
Talking to my IT guy at work looking for help with a #VMware issue I'm having. Since the broadcom takeover, I've been a bit interested in moving away from VMware. He suggested moving to #HyperV. The thought of having all of our VMs running on a Windows host is just anxiety inducing. As person who would gladly never touch another Microsoft product the rest of my life, the last thing I feel I'd want is to move to hyper-v. The only alternative to #ESXi that I'm aware of is #Proxmox though.
-
📢 VECT 2.0 : un ransomware RaaS qui détruit irrémédiablement les fichiers par défaut de conception
📝 ## 🔍 ContextePublié 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 -
Kyber Ransomware Targets Windows, VMware with Post-Quantum Encryption
Meet the Kyber Ransomware, a potent threat that targets both Windows and VMware environments with cutting-edge, post-quantum encryption. This sophisticated malware has been found to strike multiple systems at once, as seen in a March 2026 incident where two variants were deployed on the same network.
#KyberRansomware #RansomwareOperations #Vmware #Esxi #PostquantumEncryption
-
СХД, ESXi и LUN ID: теория, практика и немного боли
Хабр, привет! На связи центр компетенций VMware "Инфосистемы Джет". В этой статье расскажем о тонкостях подключения LUN (логических номеров устройств) из системы хранения данных (СХД) к хостам ESXi, которые управляются через vCenter Server. За прошлый год мы не раз сталкивались с проблемами у заказчиков, которых можно было бы избежать при правильной настройке. Как именно — расскажем ниже, не забывая и про теорию.
https://habr.com/ru/companies/jetinfosystems/articles/1013566/
-
СХД, ESXi и LUN ID: теория, практика и немного боли
Хабр, привет! На связи центр компетенций VMware "Инфосистемы Джет". В этой статье расскажем о тонкостях подключения LUN (логических номеров устройств) из системы хранения данных (СХД) к хостам ESXi, которые управляются через vCenter Server. За прошлый год мы не раз сталкивались с проблемами у заказчиков, которых можно было бы избежать при правильной настройке. Как именно — расскажем ниже, не забывая и про теорию.
https://habr.com/ru/companies/jetinfosystems/articles/1013566/
-
СХД, ESXi и LUN ID: теория, практика и немного боли
Хабр, привет! На связи центр компетенций VMware "Инфосистемы Джет". В этой статье расскажем о тонкостях подключения LUN (логических номеров устройств) из системы хранения данных (СХД) к хостам ESXi, которые управляются через vCenter Server. За прошлый год мы не раз сталкивались с проблемами у заказчиков, которых можно было бы избежать при правильной настройке. Как именно — расскажем ниже, не забывая и про теорию.
https://habr.com/ru/companies/jetinfosystems/articles/1013566/
-
Hackers chineses exploraram falhas no VMware ESXi um ano antes da descoberta
🔗 https://tugatech.com.pt/t76590-hackers-chineses-exploraram-falhas-no-vmware-esxi-um-ano-antes-da-descoberta -
Explotan VMware ESXi con herramienta de vulnerabilidad https://blog.elhacker.net/2026/01/explotan-vmware-esxi-con-herramienta-de.html #vulnerabilidad #seguridad #exploit #hackeo #vmware #esxi
-
Explotan VMware ESXi con herramienta de vulnerabilidad https://blog.elhacker.net/2026/01/explotan-vmware-esxi-con-herramienta-de.html #vulnerabilidad #seguridad #exploit #hackeo #vmware #esxi
-
Migration Windows VM von ESXi zu Proxmox https://www.bjoerns-techblog.de/2024/03/migration-windows-vm-von-esxi-zu-proxmox/ #ESXI #migration #proxmox #Virtualisierung #Windows
-
I really love Immich, bringing back old memories day by day
This is the first 'server' from circa 2015, at first an ESXi host for various tinkering, nowadays in a better looking box running OpenMediaVault and the data backbone of the home infrastructure
What a journey
#homelab #selfhosted #immich #memories #vmware #esxi #omv #openmediavault #linux #server #nas #hardwaregore
-
I really love Immich, bringing back old memories day by day
This is the first 'server' from circa 2015, at first an ESXi host for various tinkering, nowadays in a better looking box running OpenMediaVault and the data backbone of the home infrastructure
What a journey
#homelab #selfhosted #immich #memories #vmware #esxi #omv #openmediavault #linux #server #nas #hardwaregore
-
Here's how to install VMware ESX
-
Here's how to install VMware ESX
-
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
-
ESXi Root and Domain Admin Access to Vietnamese Private Company Allegedly for Sale https://dailydarkweb.net/esxi-root-and-domain-admin-access-to-vietnamese-private-company-allegedly-for-sale/ #UnauthorizedAccesses #InitialAccessBroker #activedirectory #PrivateCompany #cyberattack #databreach #Vietnam #ESXi
-
ESXi Root and Domain Admin Access to Vietnamese Private Company Allegedly for Sale https://dailydarkweb.net/esxi-root-and-domain-admin-access-to-vietnamese-private-company-allegedly-for-sale/ #UnauthorizedAccesses #InitialAccessBroker #activedirectory #PrivateCompany #cyberattack #databreach #Vietnam #ESXi
-
FBI: Over 900 Organizations Hit by Play Ransomware, SimpleHelp Exploits and ESXi Variants Used
https://forum.hashpwn.net/post/642
#playcrypt #ransomware #RaaS #simplehelp #exploit #esxi #hashpwn #cybersecurity #news
-
FBI: Over 900 Organizations Hit by Play Ransomware, SimpleHelp Exploits and ESXi Variants Used
https://forum.hashpwn.net/post/642
#playcrypt #ransomware #RaaS #simplehelp #exploit #esxi #hashpwn #cybersecurity #news
-
FBI: Over 900 Organizations Hit by Play Ransomware, SimpleHelp Exploits and ESXi Variants Used
https://forum.hashpwn.net/post/642
#playcrypt #ransomware #RaaS #simplehelp #exploit #esxi #hashpwn #cybersecurity #news
-
FBI: Over 900 Organizations Hit by Play Ransomware, SimpleHelp Exploits and ESXi Variants Used
https://forum.hashpwn.net/post/642
#playcrypt #ransomware #RaaS #simplehelp #exploit #esxi #hashpwn #cybersecurity #news
-
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
-
BlackLock ransomware onslaught: What to expect and how to fight it https://www.helpnetsecurity.com/2025/02/18/blacklock-ransomware-what-to-expect-how-to-fight-it/ #enterprise #ransomware #ReliaQuest #Don'tmiss #extortion #Hotstuff #Windows #VMware #News #ESXi #SMBs #tips
-
BlackLock ransomware onslaught: What to expect and how to fight it https://www.helpnetsecurity.com/2025/02/18/blacklock-ransomware-what-to-expect-how-to-fight-it/ #enterprise #ransomware #ReliaQuest #Don'tmiss #extortion #Hotstuff #Windows #VMware #News #ESXi #SMBs #tips
-
VMware Cloud Foundation のコンポーネント情報 (BOM) とサポート期間の概要
https://qiita.com/sanjushi003/items/1883cf4c77128ab3ebe4?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
VMware Cloud Foundation のコンポーネント情報 (BOM) とサポート期間の概要
https://qiita.com/sanjushi003/items/1883cf4c77128ab3ebe4?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
VMware Cloud Foundation のコンポーネント情報 (BOM) とサポート期間の概要
https://qiita.com/sanjushi003/items/1883cf4c77128ab3ebe4?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
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? -
Man I prolly have hard-rebooted my #Proxmox server almost or over 10 times now probably - all bcos, somehow, after adding a PCI device (passthrough), particularly a SATA card to my #TrueNAS VM, each time I boot it up Proxmox would just... hang forever and become inaccessible despite still "running".
The error it spits out is:Pool 'rpool' has encountered an uncorrectable I/O failure and has been suspended
This move away from #ESXi is a lot more painful than I imagined.
---
Update: Might have found the culprit, and that it possibly has to do with its #IOMMU group number. That is, on Proxmox, even when you think you're sharing the one PCI device you've selected, you're actually also sharing the entire IOMMU group sharing the same number, which in my case is like... almost everything else.
I'm just perplexed by how ESXi was able to passthrough the device just fine, on the exact same hardware setup? I really don't wanna go back tho, but I'm not sure if there's even a solution to this, since I couldn't really move this SATA card anywhere else.
🔗 https://forum.proxmox.com/threads/proxmox-freeze-when-launching-gpu-passthroughed-vm.104801
RE: https://sakurajima.social/notes/a1vvx0jo6u -
Man I prolly have hard-rebooted my #Proxmox server almost or over 10 times now probably - all bcos, somehow, after adding a PCI device (passthrough), particularly a SATA card to my #TrueNAS VM, each time I boot it up Proxmox would just... hang forever and become inaccessible despite still "running".
The error it spits out is:Pool 'rpool' has encountered an uncorrectable I/O failure and has been suspended
This move away from #ESXi is a lot more painful than I imagined.
---
Update: Might have found the culprit, and that it possibly has to do with its #IOMMU group number. That is, on Proxmox, even when you think you're sharing the one PCI device you've selected, you're actually also sharing the entire IOMMU group sharing the same number, which in my case is like... almost everything else.
I'm just perplexed by how ESXi was able to passthrough the device just fine, on the exact same hardware setup? I really don't wanna go back tho, but I'm not sure if there's even a solution to this, since I couldn't really move this SATA card anywhere else.
🔗 https://forum.proxmox.com/threads/proxmox-freeze-when-launching-gpu-passthroughed-vm.104801
RE: https://sakurajima.social/notes/a1vvx0jo6u -
A new version of check_esxi_hardware, an #opensource #monitoring plugin to monitor the hardware of VMware ESXi servers, is available.
The newest release fixes a #Python deprecation warning. More importantly the new version removes support for legacy and meanwhile EOL versions of Python2 and pywbem 0.7.0.
As the purpose of check_esxi_hardware is to query the #CIM server on an #ESXi server - which will be removed - this may be the last and final release of the plugin. 😿
https://www.claudiokuenzler.com/blog/1455/check_esxi_hardware-20241129-python2-support-removed
-
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 thekillallscript and reboot the entire node. Pretty weird, when both clusters were deployed/configured the exact same way and runs the exact same version.