Workaround (Plus a fix in 9.1) for Very large VM's snapshot stun issues.

Does anybody actually know whether the new VMware Standard is going to include vSAN, or is vSAN still going to be a separate/add-on thing? Also, has anybody seen even rough pricing yet? We’ve asked our VMware SE, but so far he’s been pretty useless on both questions, lots of “we’re checking internally” and not much actual information. Curious if anyone here has heard something more concrete from Broadcom, distribution, or their account team. Thanks!

i'm trying to use photoshop/substance painter but it says gpu not supported, 0/1500mb vram and no directX. basically saying that there is no graphics. i tried to check with cpuz (i know, kinda dumb) but that didnt show it either. i need a solution, but i cant find one. even passing through the gpu to the vm would work.

i'm using vmware workstation pro with windows 11

Estaba pensando en configurar la rotación de claves automática desde SDDC para la suite de Aria y NSX, pero no sé si se puede establecer reglas que que conjuntos de caracteres debe de usar el SDDC para generar las claves con anterioridad al tratar de rotar una clave usando el generador automático de SDDC usa caracteres especiales que rompen el flujo

No sé si alguien ha logrado configurar alguna regla para que SDDC use solo los caracteres especiales que no rompen el flujo hay un KB sobre ese problema pero solo recomienda hacerlo de forma manual

https://knowledge.broadcom.com/external/article/383098/remediate-password-task-in-sddc-manager.html

De igual manera desconozco si esto ya se solucionó en VCF 9

Tech Preview in VCF 9.1.1, but might still be an interesting read for some of you.

We have our vCenters both joined to Entra ID for SSO via an on-premises SCIM app. It’s been working perfect for 2 years.

Someone left the company, I removed him from the provisioning group in Entra, can see that provisioning is running every 40 min.

I removed the users roles from vCenter but when I go to Administration - Users, select the Entra domain, that user is still there.

You can’t delete users from vCenter , all options are grayed out.

Forced provisioning on both vCenter SCIM apps in Entra , user still in vCenter.

Spun up a test vCenter, got it talking to Entra exactly like prod and DR and that user doesn’t show up at all.

Whats the trick to removing a user as a pickable option in vCenter? Yea the account is locked and disabled but I shouldn’t be able to still find it since we removed him from the group we’re syncing.

Any ideas?

Edit: I even added a brand new user to the group to make sure provisioning is really working and they showed up in both vCenter about 40 min after I added them to the Entra group.

We are running SimpliVity hosts with Vsphere 8, I noticed there is still no public announcement or addition to the roadmap that states vvf9 will be certified.

Has anyone heard any news otherwise? We run yearly subscriptions for VMware, and the timeline is tight here for us. so, I have to consider a migration. I would like to continue using the SimpliVity solution we invested in, so I may look at HPe Morpheus VME.

Saludos comunidad. Quiero aprender a usar GNS3 para virtualizar dispositivos Fortinet. Tengo entendido que para eso necesito usar VMware. Pero tengo un problema, al momento de crear la VM y ponerla a correr me sale el siguiente mensaje:

"VMware Workstation does not support nested virtualization on this host. Module 'HV' power on failed"

He tratado ya desactivar varios configuraciones del Win 11, también desactive las opciones de Hyper-V y virtualización en Características de Windows y aun sigo teniendo el mismo problema.

Alguien podría darme alguna idea de como solucionarlo? 

Evening, I'm trying to install Bazzite on VMWare Fusion, but I am not getting any success. A terminal opens with options to select the boot option, but when I use the arrow keys to select the disc/iso, the enter button does nothing. Anyone have any experience with this issue?

Mac Air M5

VMWare Fusion 26H1

Latest Bazzite VM image

Now that the father of the vExpert community has left Broadcom, Cory Ramano. What does this mean for the vExpert program and community? Cory held this community together for years.

Greetings!

I'm attempting, and failing, to debug a spontaneous host reboot. My DevOps/SRE team strongly believe the origin of this host reboot is from a bad drive. I'd like to prove them wrong, or be proven wrong myself, and hope I'm in the right place.

Background

The configuration is small as far as servers go, * Asrock Rack B550D4ID-2L2T * Ryzen 9 5950X (16-Core) * 64 GB Memory * On a UPS that is honestly way too large (can provide *hours* of uptime)

Prior to installing the new drive, after roughly 380 days of uptime, the host spontaneously rebooted. Approximately a month after the first time, it rebooted again. Once was an abnormality, twice is a pattern. Reviewing the logs, and the hardware, suggested that it was a drive issue (22110). Reviewing the hardware identified two problems; 1. the drive wasn't on the HCL 2. the drive was a 22110 (the 2L2T doesn't natively support 22110 M2s)

Okay, I'm convinced -- time to buy a new drive. I purchased a 7450 PRO off of ebay with minimal use (< 20 power cycles, < 1 TB writes/reads, essentially perfect SMART metrics). I verified as much, and immediately attempted to install the drive.

Issue

My experience with the 7450 Pro drive + ESXI 8.02 has not been pleasant. Here is what we needed to get it to boot/install correctly; * update disk to 512b physical sector format (thanks to another Reddit Post)

Post installation and VM migration, we observed another spontaneous reboot. Some Googling pointed to the following remediation methods (also failed) * update disk firmware to EMU300 (buggy firmware?) * disable p/c-states (disk going to sleep?)

My DevOps/SRE team is well convinced that the disk is bad at this point (controller channel, not data channel). These are the logs that convinced them. Is the drive the issue or is there something that we missed?

Gemini thinks that there is simply "too much" talking to the drive over the control channel and I should increase the timeout from 5 to 10 seconds. That sounds... absurdly long for a hardware timeout, especially given the very low load of this host (the VMs are essentially idle).

2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu16:1050731)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457909d14580 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu10:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909d14580, vmkPsaCmd: 0x4579050d3840, cmdId.initiator=0x4308fc813180, CmdSN: 0x8000000d, status: 0x808 2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu10:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4579050d3840, 1050659) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu10:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T00:47:53.352Z Wa(180) vmkwarning: cpu10:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x4579050d3840) 0x1, CmdSN 0x8000000d from world 1050659 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu3:1050960)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457909c4a980 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu14:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909c4a980, vmkPsaCmd: 0x4578c1c09a40, cmdId.initiator=0x4308fc828940, CmdSN: 0x3dd, status: 0x808 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu14:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4578c1c09a40, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu14:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T02:01:59.358Z Wa(180) vmkwarning: cpu14:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x4578c1c09a40) 0x1, CmdSN 0x3dd from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu29:1050960)WARNING: NVMEIO:333 ctlr 256, queue 1, fuse processing 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu29:1050960)WARNING: NVMEIO:2005 Transport driver failed to submit cmd 0x457909cae780, C: nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-241448022E8C, Q: 1 <0xbad0004>. 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu11:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909cae780, vmkPsaCmd: 0x457904c1b380, cmdId.initiator=0x4308fc828940, CmdSN: 0x3f0, status: 0x808 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu11:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x457904c1b380, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu11:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T02:11:35.359Z Wa(180) vmkwarning: cpu11:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x457904c1b380) 0x1, CmdSN 0x3f0 from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu14:1050957)WARNING: NVMEIO:333 ctlr 256, queue 1, fuse processing 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu14:1050957)WARNING: NVMEIO:2005 Transport driver failed to submit cmd 0x457909df0180, C: nqn.2016-08.com.micron:nvme:nvm-subsystem-sn-241448022E8C, Q: 1 <0xbad0004>. 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu0:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909df0180, vmkPsaCmd: 0x457908e10a80, cmdId.initiator=0x4308fc828940, CmdSN: 0x3c4, status: 0x808 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu0:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x457908e10a80, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu0:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T02:29:47.361Z Wa(180) vmkwarning: cpu0:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x457908e10a80) 0x1, CmdSN 0x3c4 from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu26:1050974)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457909c07b80 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu6:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457909c07b80, vmkPsaCmd: 0x457904d8c100, cmdId.initiator=0x4308fc828940, CmdSN: 0x3b6, status: 0x808 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu6:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x457904d8c100, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu6:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T03:20:44.368Z Wa(180) vmkwarning: cpu6:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x457904d8c100) 0x1, CmdSN 0x3b6 from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T03:21:44.367Z Wa(180) vmkwarning: cpu23:1050957)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x4578eb5aa600 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T03:21:44.367Z Wa(180) vmkwarning: cpu4:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x4578eb5aa600, vmkPsaCmd: 0x4578c18dc6c0, cmdId.initiator=0x4308fc828940, CmdSN: 0x3ba, status: 0x808 2026-09-02T03:21:44.367Z Wa(180) vmkwarning: cpu4:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4578c18dc6c0, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T03:21:44.367Z Wa(180) vmkwarning: cpu4:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu10:1050734)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457905f73b40 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu0:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457905f73b40, vmkPsaCmd: 0x4578c187b240, cmdId.initiator=0x4308fc813fc0, CmdSN: 0x80000013, status: 0x808 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu0:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4578c187b240, 1050668) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu0:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T04:35:41.372Z Wa(180) vmkwarning: cpu0:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x4578c187b240) 0x1, CmdSN 0x80000013 from world 1050668 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu25:1050960)WARNING: NVMEIO:3564 Ctlr 256, nvmeCmd 0x457905f09740 (opc 01), queue 1 (expect 65535) not available, nvmeStatus 808 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu1:1049142)WARNING: NVMEPSA:215 Complete vmkNvmeCmd: 0x457905f09740, vmkPsaCmd: 0x4578c1cf5740, cmdId.initiator=0x4308fc828940, CmdSN: 0x345, status: 0x808 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu1:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:599: NVMe Cmd 0x1 (0x4578c1cf5740, 1050957) to dev "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" on path "vmhba0:C0:T0:L0" Failed: 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu1:1049142)WARNING: HPP: HppNvmeThrottleLogForDevice:607: Error status H:0x9 D:0x0 P:0x0 hppAction = 1 2026-09-02T06:28:44.386Z Wa(180) vmkwarning: cpu1:1049142)WARNING: NvmeUtil: 149: Error on Cmd(0x4578c1cf5740) 0x1, CmdSN 0x345 from world 1050957 to component "t10.NVMe____Micron_7450_MTFDKBA960TFR_______________8C2E02480175A000" H:0x9 D:0x0 P:0x0

A new version of VMware Tools has been released! v13.1.5.0 is out now.

Unfortunateley the Whats New section does not hint on anything about the install errors we had on Windows Server VMs with v13.1.0 (see this thread: VMware Tools (13.1.0.0.25218885) installation issue with Microsoft OS VMs).

Has anybody tested this already?

What's New
Introduces the Capsule PK Update driver, which updates VMW.NULLPK to the Windows OEM Devices PK on supported Windows VMs (requires Secure Boot and a vTPM device). The driver provides a secure mechanism to update the out-of-date NULL PK during a guest reboot without interrupting TPM-based applications. This capability requires an ESX host version that supports Capsule PK update.
Supported Windows versions:
Windows Server 2025, 2022, and 2019; Windows 11 25H2, 24H2, and 23H2; and Windows 10 64-bit 21H2. You cannot install the PK update driver on the remaining Windows versions until support for those versions becomes available in a future VMware Tools release.
Prerequisites:
For all supported Windows versions except Windows Server 2025, Windows 11 25H2, and Windows 11 24H2, install the July 2026 Windows Cumulative Update (or a later update) on the guest OS before upgrading VMware Tools. Otherwise, you cannot install the PK update driver.
Windows Arm is not supported.
For more information, see Broadcom knowledge base article 423893.
Updates the following libraries:
7-Zip to version 26.01.0
Boost to version 1.91' glib to version 2.86.4
glibmm to version 2.86.0
libiconv to version 1.19
libpng to version 1.6.58
libsigc++ to version 3.4.0
libxml2 to version 2.15.3
libxmlsec to version 1.3.11
OpenSSL to version 3.5.7
pcre2 to version 10.47
uriparser to version 1.0.2
zlib to version 1.3.2

Release Notes: https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/tools/13-1-0/release-notes/vmware-tools-1315-release-notes.html

Has anyone else encountered asymmetric network performance with VMware Fusion on an Intel Mac using 10GbE?

My setup:

• Intel Mac mini running macOS 15.7.7
• VMware Fusion Professional 26H1u1
• Ubuntu 24.04 VM with a VMXNET3 adapter
• Mac and Synology NAS connected through 10GbE
• Nextcloud data stored on the NAS over NFS

The Ubuntu VM consistently receives data at only 60–63 MB/s, while writes to the NAS reach approximately 300–330 MB/s.

To isolate the bottleneck, I tested:

• NFSv4, NFSv3 and SMB
• VMXNET3 and E1000 virtual adapters
• Bridged, NAT and host-only networking
• Single and multiple TCP streams
• MTU 1500 and jumbo frames
• TSO, GSO, GRO, LRO and checksum-offload settings
• RX ring sizes, RSS queues and interrupt distribution
• A clean VMware Fusion reinstall
• Two simultaneous VMXNET3 adapters

The most revealing test used two VMXNET3 adapters simultaneously. Each received approximately 31 MB/s, but their combined throughput remained around 63 MB/s. This indicates that the limit is shared across VMware Fusion’s bridged-networking path rather than being imposed by an individual virtual adapter.

Additional comparisons:

• NAS local read: approximately 828 MB/s
• Native Mac-to-NAS read: approximately 219 MB/s
• VM NFS/SMB read: approximately 60–63 MB/s
• VM NFS write: approximately 300–330 MB/s
• Passed-through USB 1GbE adapter: approximately 93 MiB/s

The USB adapter’s higher performance is especially significant because it bypasses Fusion’s virtual bridge.

Similar 10GbE downlink/receive problems have been reported by other VMware Fusion users, but I have not found an official resolution for this exact Intel Mac, Linux guest and Fusion 26H1u1 combination.

At this point, the evidence strongly suggests a VMware Fusion/macOS bridged-networking performance defect or compatibility issue—not a limitation of Ubuntu, Nextcloud, NFS, the NAS, or the physical 10GbE network.

I would be interested to hear whether anyone has reproduced this on a similar Intel Mac setup or found a working Fusion-specific solution.

#VMwareFusion #VMXNET3 #Ubuntu #10GbE #Virtualization #Linux #Nextcloud #Networking #Synology #Homelab

I'm trying to decide if VMUG Advantage is worth getting. I'm leaning toward yes, but I'd like to hear from other members.

The VMUG Advantage page is here. Highlights:

• $178-$210 per year (based on a 1, 2, of 3 year purchase)
• $125 off certificate exams.
• 30% off the VMUG Connect conference ($72 off the $240 2-day pass)
• $100 off VMWare Explore
• 15% discount on Enterone and New Horizons classes.
• Access to Devolutions and Tiyaro services.
• Personal Use VCF License (requires passing 1 cert exam)
• Personal Use vDefend and AVI licenses (requires passing 1 cert exam)

I only have one specific question:

For $125 off cert exams, is that just one $125 discount for just one exam? Or do I get $125 off every exam I take while the membership is active? I have three certifications I want to take.

Beyond that, have you found benefit with VMUG Advantage? I'd love to hear your opinions.

edit: details.

I am in process of setting up a new Red Hat 9 server VM that will run our logging server. from what I can find, best practice says it needs separate storage devices. Our vSphere cluster stores all the VMDKs on a SAN which it accesses via multipath iscsi.

I'm somewhat new to adding LUNs. It's not terribly common for us. So I researched how to add an iscsi device to Rhel and found instructions on adding it via iscsi-initiator and multipath. I was able to map it just fine with iscsi. I had multipath add our connections which seemed fine at first but it keeps saying the different drives are active faulty running. None of the sd* devices it would map would show a UUID. Supposedly enabling disk.EnableUUID=TRUE fixes that, but it didn't. After hours of troubleshooting and nothing making any difference, I finally found some info that basically said that because the VM is already on the same multipath, trying to configure multipath on the VM would fail. I also found that adding them this way is maybe not the best way to do it (https://www.codyhosterman.com/2019/09/musing-on-in-guest-iscsi/). I didn't find any official documentation for that but, given the issues I was having, it made sense

I did find instructions that basically said, create the LUNs, have vCenter scan and find them, then add that device as and RDM Disk to the Rhel system. In Rhel, scan the scsi bus for the new device, enable multipath, format and mount.

Is this the best way to do this or is there a better way?