Error failed to send host log message linux

Error failed to send host log message linux

This is an unofficial support community for Oracle VM VirtualBox, https://www.virtualbox.org/, which allows you to create virtual machines to install other operating systems on. We are NOT Oracle employees. Any advice you follow here is at your own risk. Please follow the posting rules, or your post will be removed!

Hi ! I already asked the same question on stack exchange but it went unnoticed and I’m starting to panic.

I’m running Linux ubuntu 20.04 on VirtualBox 6.1 from a windows 10 laptop. For the past weeks, it worked almost perfectly. Except I once had a problem with a black screen after the boot-up but it was just a video memory issue.

When I tried to open it today for the first time after a week, the boot-up prompt displayed the following error message :

[drm:vmw_host_log [vmwgfx]] *ERROR* failed to send host log message
The ubuntu logo starts rotating, it disappears and I then get a black screen.

I read a lot of advice on forums today. So far, I tried:

• Updating Virtual Box
• Increased video memory to 128Mb, and double my disk space up to 64Gb
• Turned off / on Windows Hypervisor Platform, Virtual Machine Platform, and combinations of the 2 in Windows Features.
• I apparently didn’t have access to Hyper-V, so I downloaded it. I first tried to disable it using the command lines
  bcdedit /set hypervisorlaunchtype off
  DISM /Online /Disable-Feature:Microsoft-Hyper-V
  I went to check on Windows Features after restarting my pc and Hyper-V was downloaded but still activated. So I just unchecked the Hyper-V box from Windows Features.
• Disable DeviceGuard with gpdedit.msc, but my system seemingly doesn’t have it (it’s Windows 10 Pro only from what I read, I’m running Windows 10 Family). I also disabled Windows Defender’s Core Isolation.
• Finally, I tried c hanging the display settings from VMSVGA to VboxVGA or VboxSVGA. I don’t get the error in the boot-up prompt anymore, but I get an alert «invalid setting detected». It also leads to a black screen after the boot-up. I also tried to find help with that, but it failed.

Also, when I scroll to the bottom of my system information , I have 4 lines related to hyper-v. The value (in the second column) is «yes», as shown in the linked picture . (I think that this only shows if my system has the required configuration to use hyper-v though)

I have no clue what do to next as I’m very new to this type of environment. All the code I’m working with for a project is in this system and I really don’t want to lose it in the process.
Can anyone help me ?

Источник

Why does «drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message» show up and what can I do to fix it?

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:

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

For me this was happening when the Virtual hard drive was out of disk space. Hold Shift right when you start and enter recovery mode, drop to a shell and then delete some stuff.

4 Answers 4

Try to change display setting and check

@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? 🙂

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.»

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?

This does not work in my case. I succeeded however by booting a previous kernel and not changing the graphics setting. See also: askubuntu.com/questions/1284588/….

This removes the error on boot, but the graphic system goes super slow. so I’ve just reverted back to the previous graphic controller

Источник

How To Fix VirtualBox Failed To Send Host Log Message

If you are running the Linux in your VirtualBox, You may encounter the error message during booting and trying to log into your virtual Linux OS.

When you try to boot your Linux OS, you will be blocked by a black screen from entering into the GUI by the following error message.

The VirtualBox Failed To Send a Host Log Message.

The error usually occurs because there is insufficient free disk space to start the desktop environment.

You will be stuck on the initramfs console.

This article will help you fix the issue of VirtualBox Failing to send Host Log Message.

What Causes VirtualBox Fail To Send Host Log Message?

VirtualBox Failed to send Host Log Message means, for some reason the OS cannot launch the GUI.

If the OS display setting mismatches, the Monitor display setting results in VirtualBox Failed To Send Host Log Message.

You might run out of disk space and cannot launch the OS successfully.

If you are using the outdated VirtualBox, you must reinstall the virtual package to the latest to fix the error.

How To Fix VirtualBox Failed To Send Host Log Message

Before getting into the fix, do the following primary step.

• Make sure Virtualization is enabled in your BIOS.
• The primary step is to restart your VirtualBox and reboot your Linux OS. Restarting the virtual machine will remove any minor technical glitches inside the system.

Here are the step-by-step Troubleshooting fixes.

1. Change The Display Setting In VirtualBox

First, wait for 5 minutes before getting into the Troubleshooting process.

The error is a bug in the Linux driver for the VMSVGA Video card.

If there are no other problems, the OS continues to boot without errors.

Else first try changing the Display from the VirtualBox.

Changing the Display setting will help you to eliminate the log error.

• Go to Settings from your VirtualBox
• Click on Display from the setting menu
• Click on Graphic controller in the display menu options
• Select VBoxVGA from the drop-down box
• Tap on Ok.

Now you can see the error is fixed.

Because this is a BUG from VMSVGA Graphic controller, and the issue is not in all versions of VirtualBox.

If you are not using the GUI, add the nomodest command to the kernel boot, which disables the VMSVGA.

• #debian 11
• #/etc/default/grub
• GRUB_CMDLINE_LINUX_DEFAULT=”quiet nomodeset”
• update-grub

You can install the latest version of the VirtualBox to avoid the error.

2. Reinstall The VirtualBox

As mentioned above, the error occurred only in the particular version of the VirtualBox.

You can prevent the error by installing the latest version of VirtualBox.
The bug has been removed in the newest version of VirtualBox.

3. Issue With Your Disk On VirtualBox

If you have any problem other than the bug, the above method doesn’t work.

The Disk partition may be corrupted.

Then you will see the corrupted partition message in the console.

Replace the sdax with your disk name.

You will back in the file system without any errors.

I hope the article helps you to fix the error VirtualBox Failed To Send Host Log Message.

And now you can boot your OS without any issues.

Источник

Error [drm:vmw_host_log [vmwgfx]] in version 6.1.0

This is when I select VMSVGA as the Graphics Controller. This message does not happen if I use the old VBOXVGA. I am unsure what, if anything, this effects.

I have included the machine log to this report.

Вложения (1)

Download all attachments as: .zip

История изменений (16)

by DonC , 4 года ago

comment:1 by GnomeUser , 4 года ago

Can confirm this bug on Ubuntu 18.04.3 kernel 5.0.0 guest. It was also mentioned here earlier this year ​ https://unix.stackexchange.com/questions/502540

comment:2 by sergiomb , 3 года ago

I also see this message on 6.1.4 with VMSVGA

[drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message.

comment:3 by Frank Batschulat (Oracle) , 3 года ago

comment:4 by Frank Batschulat (Oracle) , 3 года ago

The reason why changing the Virtualbox Graphics Controller from VMSVGA back to to VBoxVGA makes this error message disappear is quite simple. Only VMSVGA works in cooperation with the corresponding Vmware vmwgfx kernel driver inside the guest which emitted the error message.

VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device. This emulates the VMware Workstation graphics adapter with the «VMware SVGA 3D» acceleration method. This is the default for Linux guests.

VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device. This is the default graphics controller for Linux guests.

Eventually cooperating with the vmwgfx kernel module in the Linux guest.

The host logging facility of the vmwgfx driver was introduced in 2016:
PATCH 1/2 drm/vmwgfx: Add VMWare host messaging capability
​ https://www.spinics.net/lists/dri-devel/msg105952.html
PATCH 2/2 drm/vmwgfx: Report vmwgfx version to vmware.log
​ https://www.spinics.net/lists/dri-devel/msg105953.html

static int vmw_driver_load(struct drm_device *dev, unsigned long chipset) [. ] snprintf(host_log, sizeof(host_log), "vmwgfx: %s-%s", VMWGFX_REPO, VMWGFX_GIT_VERSION); vmw_host_log(host_log); memset(host_log, 0, sizeof(host_log)); snprintf(host_log, sizeof(host_log), "vmwgfx: Module Version: %d.%d.%d", VMWGFX_DRIVER_MAJOR, VMWGFX_DRIVER_MINOR, VMWGFX_DRIVER_PATCHLEVEL); vmw_host_log(host_log);

* vmw_host_log: Sends a log message to the host * * @log: NULL terminated string * * Returns: 0 on success */ int vmw_host_log(const char *log) [. ] msg = kasprintf(GFP_KERNEL, "log %s", log); if (!msg) < DRM_ERROR("Cannot allocate memory for host log message.\n"); return -ENOMEM; >[. ] if (vmw_open_channel(&channel, RPCI_PROTOCOL_NUM)) goto out_open; [. ] out_open: kfree(msg); DRM_ERROR("Failed to send host log message.\n");

vmw_open_channel() however is attempting to perform a VMWARE HYPERCALL:

* vmw_open_channel * * @channel: RPC channel * @protocol: * * Returns: 0 on success */ static int vmw_open_channel(struct rpc_channel *channel, unsigned int protocol) < unsigned long eax, ebx, ecx, edx, si = 0, di = 0; VMW_PORT(VMW_PORT_CMD_OPEN_CHANNEL, (protocol | GUESTMSG_FLAG_COOKIE), si, di, 0, VMW_HYPERVISOR_MAGIC, eax, ebx, ecx, edx, si, di); if ((HIGH_WORD(ecx) & MESSAGE_STATUS_SUCCESS) == 0) return -EINVAL;

* Hypervisor-specific bi-directional communication channel. Should never * execute on bare metal hardware. The caller must make sure to check for * supported hypervisor before using these macros. [. ] #define VMW_PORT(cmd, in_ebx, in_si, in_di, \ flags, magic, \ eax, ebx, ecx, edx, si, di) \ (< \ asm volatile (VMWARE_HYPERCALL : \ [. ]

/* The low bandwidth call. The low word of edx is presumed clear. */ #define VMWARE_HYPERCALL \ ALTERNATIVE_2("movw $" __stringify(VMWARE_HYPERVISOR_PORT) ", %%dx; " \ "inl (%%dx), %%eax", \ "vmcall", X86_FEATURE_VMCALL, \ "vmmcall", X86_FEATURE_VMW_VMMCALL)

#define X86_FEATURE_VMCALL ( 8*32+18) /* "" Hypervisor supports the VMCALL instruction */ #define X86_FEATURE_VMW_VMMCALL ( 8*32+19) /* "" VMware prefers VMMCALL hypercall instruction */

This was introduced with:
PATCH v2 2/4 x86/vmware: Add a header file for hypercall definitions
​ https://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg276273.html

VMware Fri, 23 Aug 2019 01:14:47 -0700 The new header is intended to be used by drivers using the backdoor. Follow the kvm example using alternatives self-patching to choose between vmcall, vmmcall and io instructions. Also define two new CPU feature flags to indicate hypervisor support for vmcall- and vmmcall instructions.

We do not support that infrastructure callbacks to the host hypervisor. I cannot find more details immediately on its implementation and intended usage.

I consider this a bug in the Vmware vmwgfx driver itself.

That action using vmw_host_log() (print driver version info) does only happen when the vmwgfx kernel module is loaded during Linux boot.

vmw_host_log() does not check and verify whether or not we have a supporting hypervisor befor using vmw_open_channel() and VMW_PORT() - it assumes failure of attempting to perform the hypercall to the host as a generic failure, where in this case here with Virtualbox there is no supporting hypervisor to talk to.

Other then this missing Vmware driver version information reporting in the host I don't think there is any real problem or failure.

Please contact the upstreams Linux driver owner for more questions.

comment:5 by Frank Batschulat (Oracle) , 3 года ago

Источник