Skip to content
FydeOS Help Center

Troubleshooting VMware OVA Boot Issues with FydeOS

Experiencing boot problems with your FydeOS virtual machine in VMware Workstation? This guide covers common issues and solutions to get you up and running.

Adjusting Virtual Machine Compatibility Settings

One potential cause of boot issues can be the compatibility version setting of your FydeOS virtual machine. This setting determines the virtual hardware features exposed to the guest operating system and can sometimes cause conflicts if not configured correctly.

To resolve this, you can manually adjust the compatibility version to either the highest available version or the version that matches your current VMware Workstation installation. Here’s how:

(Instructions would typically go here, referencing the images. Since we can’t directly show interactive steps in markdown, we’ll describe what the images show and how to do it)

  • Locate the Virtual Machine Settings: Right-click on your FydeOS virtual machine in the VMware Workstation library and select “Settings”.
  • Navigate to the “Compatibility” Tab (or similar): Depending on your VMware Workstation version, you should find a tab or section labeled “Compatibility” or “Hardware Compatibility”. change-compatibility
  • Change the Compatibility Version: Use the dropdown menu to select either the “Latest hardware compatibility” or a version number that corresponds to your VMware Workstation version. change-compatibility-2
  • Apply and Restart: Click “OK” to save the changes and then attempt to power on your FydeOS virtual machine again.

Addressing mesa3d Errors on Linux Hosts

If you are running your VMware Workstation on a Linux host operating system and encounter an error message specifically related to mesa3d when starting your FydeOS virtual machine, it often indicates a graphics driver incompatibility.

In such cases, you can try manually modifying the virtual machine configuration file (.vmx file) for your FydeOS VM. Adding the following configuration line can sometimes resolve the issue by allowing the use of potentially blacklisted graphics drivers:

mks.gl.allowBlacklistedDrivers = TRUE