Man kann #opensource kleinreden wie man will aber eine solche Uptime habe ich bei noch keinem #esxi hinbekommen!
In der #Schweiz sind etwas mehr als 130 Instanzen betroffen (Stand: gestern)
Attacken auf #VMware #ESXi: Immer noch zehntausende Server verwundbar | Security https://www.heise.de/news/Attacken-auf-VMware-ESXi-Immer-noch-zehntausende-Server-verwundbar-10307632.html #Patchday #VMwareESXi
Check the alarms on all ESXi Hosts via Powershell http://dlvr.it/TJKSbF via PlanetPowerShell #PowerShell #ESXi #vCenter #Coding
That's so freaking weird lol... on one of my #Proxmox nodes, I had started a test VM (#RockyLinux/#RHEL), and I was installing a single package on it, and for wtv reason that ended up powering off ALL other VMs on that Proxmox node other than that one test node.
I've never had this happen before in my #homelab, on Proxmox or #ESXi, but it's incredibly concerning for sure lol. I have some critical stuffs on it too like my #TrueNAS server, some of #Kubernetes nodes, etc. and to have them just... power off like that without any alerts or logs explaining it, not on the GUI anyway, is insane.
A new version of check_esxi_hardware, an #opensource monitoring plugin to monitor the hardware of Broadcom #ESXi servers, was just released.
The latest version improves exception handling from the pywbem Python module and also added HTTP exception handling.
To ensure backward compatibility for users using older and newer pywbem versions, the #monitoring plugin now requires the "packaging" Python module.
More details in the blog post.
I have an old NUC 11 that I think is failing. I run ESXi on it, the free version. It has 32GB of ram, 1x 1TB SSD and 1x 2TB SSD. Can anyone recommend a good replacement?
I am sure a lot of people will also recommend Proxmox over ESXi, but I have to run some images that are only ESXi.
Any suggestions would be most welcome
#Microsoft's February 2023 #PatchTuesday Tuesday: Secure Boot issues for #Windows #Server 2022 VMs hosted on #VMware #vSphere Platforms (up to, and including 7.0x)
Workaround:
1. Disable Secure Boot on affected VMs, or
2. Don't install Patch yet, or
3. Upgrade to vSphere 8.0
https://kb.vmware.com/s/article/90947
https://www.catalog.update.microsoft.com/Search.aspx?q=kb5022842
#virtualization Performing VM migration from #VMware to #Hyper-V on a client’s new HPE Proliant Server. I’m using the free #StarWind V2V Converter straight into VMware #ESXi. First VM with Windows Server 2022 at 150Gb finished without error in 1 hour. Confirmed in the Hyper-V console. Thank you StarWind!
Please patch your #VMware #ESXi and #vCenter Server
Severity Level: IMPORTANT
VMSA-2022-0030 - VMware ESXi and vCenter Server updates address multiple security vulnerabilities (CVE-2022-31696, CVE-2022-31697, CVE-2022-31698, CVE-2022-31699)
Please see the advisory here: https://www.vmware.com/security/advisories/VMSA-2022-0030.html
Impacted Products:
VMware ESXi
VMware vCenter Server (vCenter Server)
VMware Cloud Foundation (Cloud Foundation)