-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Uri Herrera edited this page Jan 19, 2026
·
8 revisions
Likely, the DDC/CI automation is working correctly, but the Guest OS hasn't yet initialized the display driver. VxM sends VCP code 0x60 (Input Source) to your monitor immediately upon VM launch. Give the Guest OS a moment to boot.
This issue happens because the secondary GPU is not isolated. It may share an IOMMU group with other devices (like a USB controller or a network card). You cannot pass through the GPU without passing through everything in that group. You may need to change PCIe slots.
This problem occurs on NVIDIA hardware because the NVIDIA driver handles rebinding differently. It's known behaviour in this case.
©2026 Nitrux Latinoamericana S.C.
Hardware Constraints
- 1. Dual GPUs are Mandatory
- 2. IOMMU Groups and UEFI Firmware
- 3. "Stubborn" Hardware (AMD Reset Bug)
- 4. Laptop/Mobile GPUs
Software Environment
- 1. Can I use VxM with a single GPU?
- 2. Why is my RAM usage so high when the VM is off?
- 3. How do I release my mouse/keyboard from the VM?
- 4. Can I use Looking Glass?
- 5. Where is the virtual disk located?
- 6. Does Windows 11 work?
- 7. How do I install network and storage drivers during Windows installation?
- 8. How do I reset VxM?
- 9. Do the NVIDIA drivers work with VxM in Windows?
- 1. My monitor switches to a black screen when the VM starts
- 2. I get an "IOMMU Group" error
- 3. Session crashed after the VM stopped