All Posts

This issue could be caused by the incorrect version of the VMware SVGA driver installed within the virtual machine, which comes bundled with VMware tools. 1. Try booting the virtual machine into Safe Mode. 2. In the Device Manager, change the driver for the VGA card to the standard MS VGA Driver. (You may also uninstall the driver instead.) 3. Reboot the virtual machine. 4. Uninstall the current incorrect version of VMware tools. 5. Install the latest correct version of VMware tools.         Note: Current, VMTools mapping to ESXi can be found here - https://packages.vmware.com/tools/versions

This of for (at least) vSphere 7.0 U3. "vmx swap file" - for swapping (by the hypervisor) content of RAM used by the VMX process to disk "vswp file" - for swapping (by the hypervisor; and not by the Guest OS) content of RAM used by the Guest OS to disk     Additional info is provided below.   When memory is overcommitted (and provided that there is sufficient free disk space at the time a VM was powered on), the Host can swap part of the memory occupied by the VMX process to disk. This reduces the RAM of the VMX process from about 50MB or more to about 10MB. This file is 80 MB in size, stored in the VM Home folder, named vmx-<VM Name>-<string of Hex digits>.vswp   A running VM has the following processes or userworlds that run in the VMkernel. * VM Executable (VMX) - responsible for      ** handling I/O to devices that are not critical to performance      ** communicating with user interfaces, snapshot managers, and remote console * VM Monitor (VMM); one for each vCPU of the VM      ** responsible for virtualizing the guest OS instructions and managing memory      ** passing storage and network I/O requests to the VMkernel; and passing all other requests to the VMX process * Mouse Keyboard Screen (MKS) - responsible for rendering the guest video and handling Guest OS user input   When a VM is powered on, the Host creates a swap file * size of which = memxize - memory reservation * which, by default, is in the VM Home directory (except for SAN or vVols datastore) and named <VM Name>-<string of 8 Hex digits>.vswp This file is used when the hypervisor wants to swap some part of the Guest OS machine memory to disk.  

Go to the vmware workstation -Maximize the player and under Manager click Virtual Machine Settings.  Click the Processor in the left hand side of the screen and untick the "Virtualize Intel VT-x/EPT or AMD-V/RVI" as per indicated in figure attached herewith .  Restart the virtual machine for the smooth run .    

Let me provide the complete details: My VMware workstation has the below IPConfigured:   As you see with this i have 192.168.159.1 as Vm adapter ip and w.r.t that i have configured 2 ESXI with 192.168.159.5 and 192.168.159.6 and the above update is already there of my configuration. I have not configured any subnet or group. I am new to VMware. All i have done is assign 2 static ip addresses to those 2 esxi's and build the vms as said above inside them

Here is the networking done for Domain Controller, Delivery Controller and Storefront server attached for Citrix components respectively   Domain Controller : IP: 192.168.10.101, SN:255.255.255.0,Gateway:192.168.10.1, DNS 192.168.10.101 Delivery Controller : IP: 192.168.10.102, SN:255.255.255.0,Gateway:192.168.10.1, DNS 192.168.10.101 Storefront : IP: 192.168.10.103, SN:255.255.255.0,Gateway:192.168.10.1, DNS 192.168.10.101   They all reside in the ESXI2 which has static IP of 192.168.159.6

Ok, you explained how the ESXi hosts themselves are connected (NAT), but how about the VMs? How did you configure networking for them on the ESXi host, and in VMware Workstation? Maybe some screenshots will help. André

Here you are:    https://angrysysops.com/2022/03/08/building-home-lab-concept/   Check the section for :   How to enable AMD virtualization in the BIOS How to enable Intel Virtualization Technology in BIOS

Hey man,    Yes, it is, here are the minimum requirements:   A computer must have a compatible x86-64 CPU 4 cores CPU 32 GB of RAM,  It is possible to run your lab with 16GB of RAM, however, it will be painfully slow and maybe a challenge to run a nested lab ( using VMware Workstation as a hypervisor)   Here is my lab:   https://angrysysops.com/sourcing-the-parts/

VMware is a company, sounds like KIO Networks might be a VMware Cloud Provider Program (VCPP) partner - has anyone asked KIO Networks how the migration to their platform might be done? https://www.kionetworks.com/en/migration  

Ok, look citrix is ​​the virtual machine manager and it is mounted on IBM cloud, they want to migrate those virtual machines to another data center called KIO network, but instead of citrix they want to mount it on vmware.

When we did our DC migration we used Veeam to replicate VM's from one DC to the other. That way you perform a staged migration by replicating the bulk of the data upfront, and only sync the last changed blocks on the migration day. Worked flawlessly.