When I start one of my VMs I get the error [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send log and then the VM "hangs"
Host server is Red Hat 6.10
Guest VM is Red Hat 7.4
Interestingly I have cloned this VM to another VM and I do still get the error message in the console but the VM does start.
Log file attached.
Critical Error [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send log
Critical Error [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send log
- Attachments
-
VBox.log- (73.53 KiB) Downloaded 67 times
Re: Critical Error [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send log
Hello,
I have the same problem on most guests OS, and there is a confusion:
- one is supposed to use VBoxVGA in order not to have this error message, but
- only VMSVGA supports 3D acceleration, trying to use this option with VBoxVGA gives the message "This VM is configured to use 3D acceleration using the VBoxVGA graphics controller. Support for this will be removed with version 6.1.0. ALL saved states and snapshots will cease to work when using this configuration. Either switch to the VMSVGA graphics controller and update guest additions, or disable 3D acceleration."
Since it seems to work despite this error message, I suppose it's a glitch in the boot with how the VM handles the display, I couldn't find any explanation.
I have the same problem on most guests OS, and there is a confusion:
- one is supposed to use VBoxVGA in order not to have this error message, but
- only VMSVGA supports 3D acceleration, trying to use this option with VBoxVGA gives the message "This VM is configured to use 3D acceleration using the VBoxVGA graphics controller. Support for this will be removed with version 6.1.0. ALL saved states and snapshots will cease to work when using this configuration. Either switch to the VMSVGA graphics controller and update guest additions, or disable 3D acceleration."
Since it seems to work despite this error message, I suppose it's a glitch in the boot with how the VM handles the display, I couldn't find any explanation.