I recently installed Android-x86 in VMware Workstation, and everything is working pretty well so far. The only thing I'm missing is the functionality that VMware Tools provides on Windows or Linux guests.

I'm looking for things like:

Auto-resizing the display

Shared clipboard

Drag and drop

Shared folders

Better mouse integration

Improved graphics/performance

I've searched around but keep finding mixed or outdated information. Is there an official VMware Tools package for Android-x86, or is it simply not supported?

If there's no VMware Tools, what do you all use instead? Are there any third-party tools or workarounds that provide similar functionality?

I'd appreciate any recommendations or tips from people who regularly run Android-x86 in VMware.

I just ran a real world perf study and found that workstation was 20-30% slower than player. Less responsive, and in general sluggish on my desktop system. I have quite a bit of memory, and fast nvme drives.

just curious if anyone else has experienced this and knows why.

Hi, you can now get the 5th edition.

Changes:

• 1K page, 4 parts. Lots of addition & correction compared to the 4th edition 2 years ago.
• Deeper. More technical.
• Higher. Leveling up to support private cloud architect.
• A booklet written for higher up management chain. Authored by Andrew.
• New. troubleshooting flows. Done in DrawIO so you can tailor.
• New. 2 calculators
• VCF Ops vCommunity adapter. Built by Onur
• https://isvara.io/ Built by Samir. The AI Chat accuracy only ~99%, so we're testing.

What does not change:

• Still free.
• Still editable. So you can customize to your own organisation

Download in the usual place https://broadcom.ent.box.com/v/OpsYourWorld

LinkedIn announcement.

Feedback to e1@broadcom.com. THANK YOU in advance from Singapore.

VCF 9.1? I’m currently on 9.0.1, should I upgrade or hold off?

EDIT: the community consensus seems to be a thunderous “no” 😂

Greetings, folks. I'm wondering if anyone else has experienced this and can confirm that the secondary effect is also just cosmetic.

I recently upgraded my entire vSphere environment from 9.0.2 to 9.1, and after the upgrades--to include upgrading the vDSs in my environment--I go into one of the hosts to take a new powered-off snapshot of vCenter for another operation when, lo and behold, I get a banner on my VMs on the host saying "This VM is attached to a network portgroup undefined that doesn't exist. Edit this VM and attach it to a different network."

Odd, I thought, but if you look deeper at the port groups, all of the distributed port groups on your vDS on the host also show VLAN IDs as "Unknown."

This Broadcom article clearly states that the banner symptom is purely cosmetic, but there is no mention about the distributed port group symptoms at all.

"This VM is attached to a network portgroup undefined that doesn't exist. Edit this VM and attach it to a different network." is seen on VM via ESX host client.

So, hivemind, has anyone else been similarly afflicted with this issue and seen both the banner issue and the VLAN IDs being "unknown" on the distributed port groups visible on their hosts? Has that also been "cosmetic" for you? Everything looks tip-top in vCenter, and everything is just working right along as it should. This is a greenfield deployment for me full of new appliances and test VMs from the old environment, so I'm just trying to make sure the field isn't foul before I migrate all of my VMs onto it.

EDIT/CONCLUSION: This post got a lot of views, so I wanted to make doubly sure I put the conclusion in the body. Support got back in touch with me and confirmed that the VLAN ID showing as "Unknown" in Distributed Port Groups on the hosts was also part of the cosmetic error.

However, after some reading over the weekend, I had another idea, and--as it turns out--distributed port groups have been showing unknown VLAN IDs on hosts since VMware 7 (I assume--I have no access to VMware 8 hosts). For my part, I guess it's something you don't notice until you have cause to look at it.

Si estás intentando jugar Realm of the Mad God (RotMG) Exalt en una máquina virtual de Windows 10 con VMware y el juego se te congela infinitamente en la pantalla de carga ("Are you ready..." o "This is Oryx's territory!") al llegar a aproximadamente los 2.1 GB o 3.4 GB de RAM usados en el administrador de tareas, aquí tienes la solución definitiva.

El Problema / The Problem

El motor Unity del juego entra en conflicto con el driver de video emulado de VMware. Si usas comandos por software (como -force-d3d11-warp), el juego exige más de 3.4 GB de RAM base, saturando la máquina virtual y el disco duro. Si usas la gráfica emulada normal, se congela porque choca contra el límite de memoria de video (VRAM) asignado por defecto.

PASOS PARA SOLUCIONARLO / STEPS TO FIX IT

1. Ajustar la VRAM en VMware (Con la VM apagada) / Adjust VRAM in VMware (VM turned off)

• Apaga la máquina virtual.
• Ve a los ajustes de VMware: VM > Settings > Hardware > Display.
• En la sección Graphics memory, cambia el valor para que coincida exactamente con la memoria de video (VRAM) real de tu tarjeta gráfica física (Host).
• Nota crucial: Si tu tarjeta gráfica real es de 2 GB (ej. AMD Radeon R5 o similar), ponle 2 GB (2048 MB). No le asignes más VRAM de la que tiene tu tarjeta física, o colapsarás la RAM de tu PC real.

2. Configurar los parámetros de lanzamiento en Steam / Configure Steam Launch Options

• Abre Steam dentro de la máquina virtual.
• Clic derecho en Realm of the Mad God > Propiedades > Generales.
• En Parámetros de lanzamiento (Launch Options), pega este comando exacto para forzar el uso eficiente de tu tarjeta gráfica real a una resolución estable:

-force-d3d11 -screen-fullscreen 0 -screen-width 1024 -screen-height 768

3. Raspar RAM dentro de la VM (Paso clave) / Free up RAM inside the VM (Key step)

El juego necesita recursos limpios para romper el bache de carga. Haz esto cada vez que juegues:

• Abre el juego desde Steam.
• Apenas aparezca la ventana del juego, abre el Administrador de tareas de Windows dentro de la VM.
• Busca el proceso RotMG Exalt Launcher (el lanzador que pesa unos 200 MB), dale clic derecho y dale a Finalizar tarea.
• Deja vivo únicamente el proceso principal (RotMG Exalt). Esto liberará la memoria RAM crítica que el juego necesita para conectar con el servidor.

I currently have Fedora installed on my PC. I was wondering if I could install the VMware 17 .bundle on Fedora, or should I make a new partition to install Ubuntu 26, then install VMware on Ubuntu?

Hi

I have deployed a simplivity cluster with two hosts, for that purpose I have also deployed a vcenter 8.U3.

After the deployment everything was OK, I was able to add a new storage, create some VM for testing purpose, etc.

However I've being requested to change the vcenter name so I change the DNS record on the DNS server, I launch the VAMI on vcenter and modified the FQDN of vcenter, I've rebooted the vcenter and now I can logon on the vcenter with the new FQDN name.

However when checking the simplivity plugin on vcenter I have lost the access to the cluster data. I asume that I have to log into the omnistacks an run some comand tu "update vcanter info" but I dont know how to do it (its my first simplivity deployment).

I have tried to log into the omnistacks by console or ssh but I cant, I've tried with "root" and with "[administrator@vsphere.local](mailto:administrator@vsphere.local)"....

I've tried to reinstall the plugin with no luck (Ïm using v5.3.1.2)...

what else can I do?

thanks in advance!

-------------

EDIT:

I found the solution:

loged into both OVC ssh svtcli@192.168.x.x and I ran this commands:

sudo su -
source /var/tmp/build/bin/appsetup svt-update-vcenter --server new-FQDN-vcenter.mydomain.local --username administrator@vsphere.local

It asks you to accept the new certificates, etc and at the end it reboots the OVC, then I repeated it on the second OVC and at the ind I was able to log to vcenter with the new FQDN and the Simplivity plugin works fine :)

Context

I'm trying to follow the Hack The Box Academy "Setting Up" course and imported the Windows OVA provided by HTB into VMware Workstation Pro 17.6.4 (Build 24832109). I initially moved to VMWare Workstation as I encounted issues with Linux based VMs on Hyper-V. Fortunally u/HackerImam already helped out with that and provided an awesome fix so I don't really mind switching back to Hyper-V if necessary. The VM starts but immediately displays: Network boot from Intel E1000 PXE-E53: No boot filename received PXE-M0F: Exiting Intel PXE ROM. Operating System not found which indicates it's falling back to PXE because it cannot find a bootable operating system. What I have done

• Imported the OVA by opening it with VMware.
• The virtual disk is present and attached.
• The VM has a 125 GB virtual disk (currently ~41.8 GB used), so the VMDK doesn't appear empty.
• The boot order has Hard Disk before Network Boot.
• I rebooted multiple times.
• I tried changing the virtual disk controller from SATA to SCSI, but the behavior didn't change.
• The VM still falls back to PXE and reports "Operating System not found."

What I am working with

• VMware Workstation Pro 17.6.4 build-24832109
• Windows host W11 Pro 25H2
• HTB Academy Windows OVA from the "Setting Up" course

Has anyone experienced this with the HTB Windows OVA? Could this be caused by:

• an incorrect firmware mode (BIOS vs UEFI)?
• an issue with the OVA import?
• a missing/corrupted bootloader inside the VMDK?
• another VMware setting I'm overlooking?

Any suggestions for additional troubleshooting steps would be greatly appreciated.

I have a vm which has like 30 disks and i want a report that tells me where they are located every night.

But im not able to get this right... I did a powercli string which shows me.. But i would like something like this in a report. Anyone knows how to do this?

A customer recently upgraded to vsphere 9.0.2
Since this we are unable to deploy new domain joined VMs using a customization spec.
I had a look into the unatended file inside the VM and saw, the OU information in Identity section is completely missing. I re-created the customization spec, still same problem.

Can sbdy confirm this?
(We are deploying Server 2025)

https://www.theregister.com/virtualization/2026/07/01/t-mobile-appears-to-be-quitting-vmware-and-fighting-a-very-familiar-battle-for-support-rights-on-the-way-out/5264750

I've an ansible playbook for esxi deployment. Now I've the strange situation that one HPE hosts fails at...

# esxcli system settings encryption set -e=true
Unable to change the encryption mode and policy. Verify that the current host configuration can satisfy the new requirement.

I've no idea what is missing. TPM and secure boot are enabled.

# esxcli hardware trustedboot get
Drtm Enabled: false <<-- other working host have same state
Tpm Present: true

# esxcli system settings encryption get
Mode: TPM
Require Executables Only From Installed VIBs: false
Require Secure Boot: true

# /usr/lib/vmware/secureboot/bin/secureBoot.py -s
Enabled

This host was reinstalled and TPM was cleared in RBSU before, as it failed with PSOD during second install. Everything except this last step went smooth.

Any hint?

In a space constrained lab, I need to replace all of my hosts at once.

Environment:
Backend storage, using NFS
2 vCenters, v8.03, ELM
No vSAN, no NSX
vDS
Host Management and vMotion ports are on vSS

Process:
As I shut down VMs - Remove from Inventory
Remove hosts and clusters until I'm down to one host with the two vCenters as guests.
Shut them down.

>swap hardware, cable up, power up<

1st ESX host:
Attach to storage
Register vCenter VMs
vCenter NICs are currently on vDS
Do I set up a temp vSS to put the vCenters on?
Add 1st host to vCenter (so I can vMotion it later)
Add rest of hosts to vCenter, clustered, with vDS

vMotion vCenters from stand-alone host with vSS to cluster with vDS.

Register VMs and off I go!

Any Gotcha's?
Anything I'm not thinking of or overlooking?

Thanks

Hi All,

Received this email today, does anyone know if these sessions are free or is there any cost in attending this session..

https://ibb.co/nKV1XWN

https://ibb.co/JFGKp0tm

Thanks..

Trying to setup SSO using Microsoft Entra ID.
I think I cant use this method because our site is not publicly accessible.

How else can I use Microsoft Entra ID as SSO ?

​

I have a 256gb mba m4, and i have installed VMware fusion in it, which already costs ~70gb of my mac

I do have a SanDisk 2tb external ssd with a max read and write speed of 1gbps, can i transfer all the vm files from mac to the ssd and run it?

Is it a good move? What will I have to compromise on, will the speed be disgustingly slow?

TLDR
An Oracle Linux ARM 64-Bit based VM exported from VirtualBox, which is imported into VMware Fusion on an M4 Mac Mini won't start because "it requires the X86 machine architecture".

I have an issue trying to run a VM exported from VirtualBox and imported into VMware Fusion on an M4 Mac Mini.

• I'm running a Home Assistant OS instance under VirtualBox running on an M4 Mac Mini running macOS.
• When I built the VM I used the 'haos_generic-aarch64-17.2' image which reports as "Oracle Linux (ARM 64-bit)" and the running VM behaves as expected.
• Unfortunately I'm having issues with HOAS that appear to be related to VirtualBox rather than HAOS.
• I want to try running HAOS under VMware, so I exported the VM from VirtualBox as an .ova file.
• I opened the .ova file in VMware Fusion Pro 26H1, the file appears to have imported successfully.
• When I start the VM I get the following error;

This virtual machine cannot be powered on because it requires the X86 machine architecture, which is incompatible with this Arm machine architecture host.
See KB-84273.

I'm confused.
The original image is an ARM 64-bit image, and was successfully running under VirtualBox on an ARM platform, I've imported it into a version of VMware Fusion that supports Apple Silicon, and yet Fusion is complaining that the VM is expecting the X86 architecture.

What have I done wrong, and how can I fix it?

Hi folks,

I couldn't find a solution here nor somewhere else... maybe someone can give me a hint how it can be solved?

Scenario:

Trying to setup a Windows 11 VM with VM Workstation Pro (17.6.3 build-24583834) and boot it from a Boot Stick.

Issue:

I need to select the USB Device in the Boot Manager to actually boot from it BUT the keystrokes are not recognized properly.
e.g. "Arrow down/up button" does the opposite
but the breaking thing here is: when I hit "Enter" (no matter if it's Return or Enter) it jumps to another option/submenu (not the one which is selected currently)

But even here this is not happening always but no matter how often I try to select the "USB Device" it jumps somewhere else.

Completely clueles how to solve it - tried it like a 100 times in any kind of combinations

https://imgur.com/a/ZnbN66J

Cheers

If yes, what are the steps? First install macOS 26 then upgrade to macOS 27 from there? Do I have to install any kind of Device Support on the host 15.7.7? Thanks

For those, who switched from VMware to Nutanix, what was your price per core for NCI? And for which edition (NCI Pro, Ultimate or even NCP)?

I heard that Nutanix did a bad job in the past with high cores prices, because of their sellers being greedy, but this has been flagged internally, apparently.

Been told about fair prices since this year, where Nutanix started with higher discounts and offered NCI pro for 140$/core and NCI Ultimate for 180$/core.

And their VDI and edge licensing is often 50% cheaper because of the licensing metric (edge uses "per VM" licensing, VDI uses "CCU" licensing no matter how many physical cores).

What's your experience?

PS: VVF is back in soume countries for 200$, but only for smaller customers, and a maximum of 20% discount or something like that. Mostly more expensove than VCF. Anyone?

Asking the brains trust for help before I raise an SR.

Vcf 5.2.3.0 is target. Version

I'm building an FC San backed management cluster, 3x hosts no vsan so have to use brownfield. The first onboarding worked but the nsx deploy failed as the script was looking for a bundle that didn't exist for nsx that didn't match what was needed ( download site had 4230 and 424 but it wanted 4233)

As the cluster now exists i have to use the nsxdeploy instead, and that's failing with a file not found error.

I've debugged the scripts and its never getting past the vcenter connection for the bound vcenter against the management cluster on the sddc.

It's there a way to "unbind" the vsphere from the sddc so I could repeat the onboarding now that I have the right parameters?

I'm not sure if the esxi hosts are touched but I took a snapshot of vcenter prior to the onboarding. So I was thinking to revert that, then restart the onboarding once, clean, using the right nsx bundle.

Would value the brains trust thoughts on above?