This error shows up everytime I install Kali Linux, whenever I try to boot it. Then, it dissapears and the screen blacks out. The error is the following:+[drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message.

Here's also an screenshot of the error: enter image description here

  • 1
    Can you change to a different tty? What virtualization solution are you using? – kemotep Feb 25 '19 at 14:24
  • found answer in this post askubuntu.com/a/817660/714051 – Ivan Kush Nov 26 '19 at 15:54
  • I had the same issue, the problem what that I allocated 64MB video memory and my device couldn't handle that in that time, so I reduced it to 32MB and it was fine then – hossein hayati May 27 at 16:31

enter image description here

Try to change display setting and check

| improve this answer | |
  • 5
    @Harikrisnan C I can confirm that changing my Graphics Controller from VMSVGA to VBoxVGA succeeded in getting my Ubuntu VM to boot without the aforementioned error. However, why did this work? Could you add the reason for this suggestion in your answer please and thank you? :) – z.karl Dec 17 '19 at 18:01
  • 1
    When I change in Linux Mint 19.1 Mate per your suggestion, I get this 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." – whitelightning Jan 15 at 23:43
  • This solution prevents 3D acceleration within the guest OS. Is the error serious enough to warrant this, or is it just a logged error? What is the error from? – Kurt Fitzner Aug 5 at 11:06

I had the same issue installing on Windows 10. I followed the instructions in this video:


...and it seems to work now. Note, I still see those messages ("Failed to send host log message") but it boots all the way into Kali now and I do not have further issues.

Essentially what it boiled down to was a lack of resources. I allocated 2 CPU's, 2 gig of memory, and 16 gig on the virtual HD for it to work.

Also make sure you have virtualization enabled in BIOS.

| improve this answer | |

I've had the same problem today, on my Mac (not sure which host system you're working on).

The fix for me, as suggested on another forum was to downgrade to VirtualBox v5.2. Seems it has been an issue for some Mac users since last yeat.

| improve this answer | |

Not the answer you're looking for? Browse other questions tagged or ask your own question.