Virtualization Troubleshooting for CompTIA A+ 220-1101

VM fails to start — common causes: Hardware virtualization not enabled in BIOS: check Task Manager → Performance → CPU → Virtualization: Disabled. Restart and enable VT-x/AMD-V in BIOS/UEFI. Incompatible VM format: opening a VMware VM in VirtualBox or vice versa may fail. Convert the VM using vendor tools (VMware vCenter Converter, VirtualBox's 'Import Appliance' with OVA/OVF). Hyper-V conflict: on Windows, Hyper-V and VirtualBox/VMware (older versions) cannot run simultaneously. Hyper-V uses the hypervisor at a low level, preventing Type 2 hypervisors from accessing hardware virtualization. Solution: disable Hyper-V. In elevated CMD: `bcdedit /set hypervisorlaunchtype off` → reboot. (Or enable in Control Panel → Programs → Windows Features → Hyper-V). Insufficient disk space: VHD file cannot expand. Free space on the host drive. Corrupted VM files: restore from snapshot or backup.

VM has no network connectivity: check VM network adapter mode (Bridged, NAT, Host-only). Check the virtual network adapter is enabled in VM settings. Bridged mode issues: VM needs a DHCP lease on the physical network. If the physical network requires 802.1X authentication, the VM's MAC address may not be authenticated. Check that the bridged adapter is set to the correct physical NIC (laptop Wi-Fi or wired). NAT mode: VM should receive 192.168.X.X from the virtual DHCP server. If not, check that the NAT virtual network is configured in the hypervisor settings. Host-only mode: VM communicates only with host. If internet access is needed, use NAT instead. Virtual switch: in Hyper-V, virtual switches connect VMs to networks. Create an External Virtual Switch to bridge to the physical network. Internal Virtual Switch for host-to-VM only. Private Virtual Switch for VM-to-VM only. Multiple NICs in VM: advanced configurations can route different traffic through different virtual NICs.

VM running slowly: insufficient RAM allocation: allocate at least 2 GB for Windows VMs, 4 GB+ for better performance. Check host RAM — if host is near capacity, all VMs suffer. Too many VMs running simultaneously: resource contention. Close unused VMs. Disk I/O bottleneck: VHD/VMDK stored on an HDD is significantly slower than SSD. Move VM files to SSD. Enable hardware-accelerated disk I/O in VM settings. CPU allocation: ensure the VM is allocated enough vCPUs (2 minimum for Windows VMs under load). Don't allocate more vCPUs than the host has physical/logical CPUs. Graphics: enable 3D acceleration in VM settings for better GUI performance (requires VM guest additions). Install VMware Tools or VirtualBox Guest Additions: driver package that improves performance, enables shared folders, drag-and-drop, and correct display resolution. Always install Guest Additions in VMs.

Snapshot problems: Snapshots accumulate and consume significant disk space (each delta file stores changes since the snapshot). Too many snapshots degrade VM performance. Best practice: take snapshot before a risky change, delete after confirming success. Consolidate snapshots: in VMware — right-click VM → Snapshot → Consolidate. Orphaned VMDKs: old snapshot delta files left on disk after snapshot deletion. Can be safely deleted after VM consolidation. VHD/VMDK space issues: dynamically expanding VHDs grow to the maximum size. The underlying host partition must have enough free space for the VHD to expand. If the host disk is full, the VM crashes. Compact the VHD: VirtualBox — Tools → Virtual Media Manager → optimize. VMware — vmware-vdiskmanager. VHD corruption: if the host loses power while the VM is running, VHD can corrupt. Run chkdsk or fsck inside the VM. Restore from snapshot or backup if repair fails.