Difference between revisions of "Troubleshooting"

From Looking Glass
Jump to navigation Jump to search
Line 5: Line 5:
  
 
==== Obfuscate the VM (Edit Libvirt) ====
 
==== Obfuscate the VM (Edit Libvirt) ====
 +
One option is to try and make it unclear to the host that it's running in a VM. By doing this the checks the NVIDIA Driver performs during installation don't regester that it's within a virtual enviroment and allow the driver to install. We can achieve this by making some tweaks to the .XML file:
 +
<syntaxhighlight lang=text>
 +
<features>
 +
<hyperv>
 +
...
 +
<vendor_id state='on' value='linustech'/>
 +
...
 +
</hyperv>
 +
...
 +
<kvm>
 +
<hidden state='on'/>
 +
</kvm>
 +
</features>
 +
</syntaxhighlight>

Revision as of 14:36, 2 March 2020

There are many different issues that can arise when setting up a system with the level of complexity that goes into configuring Windows to run on-top of GNU/Linux. Below is a list of known issues with potential solutions:

NVIDIA Driver Error/Device Manager Error Code 43

NVIDIA back in 2014, driver version 337.88 installed a feature that checked if the driver was being installed on an OS within a virtual environment. Still included in the latest drivers today while doing this check it looks at which GPU is being used and if it's not on the official support list for use in a VM the driver will refuse to install and Device Manager will report Error 43. There are workarounds for this. Any that have been known to work are listed below:

Obfuscate the VM (Edit Libvirt)

One option is to try and make it unclear to the host that it's running in a VM. By doing this the checks the NVIDIA Driver performs during installation don't regester that it's within a virtual enviroment and allow the driver to install. We can achieve this by making some tweaks to the .XML file:

<features>
	<hyperv>
		...
		<vendor_id state='on' value='linustech'/>
		...
	</hyperv>
	...
	<kvm>
	<hidden state='on'/>
	</kvm>
</features>