Ubuntu error failed to send host log message

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

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

Jonathan E. Landrum's user avatar

asked Feb 23, 2019 at 16:58

A user of Kali Linux's user avatar

4

enter image description here

Try to change display setting and check

answered Mar 1, 2019 at 10:25

Harikrishnan C's user avatar

5

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

https://tr-my.net/watchvideo/how-to-install-kali-linux-on-virtualbox-exdj6PNPuxA.html

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

answered Feb 27, 2019 at 1:38

JOD's user avatar

This is a bug of VMSVGA which is waiting for the upstream fix. Check these websites for more information:
https://www.virtualbox.org/ticket/19168#comment:4
https://forums.virtualbox.org/viewtopic.php?t=101326

To fix this, if you are not using gui (like gnome,kde), you can just add nomodeset to the kernel boot parameters, to disable VMSVGA on boot.

#debian 11
#/etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"

update-grub

If you are using gui, just ignore the message, it’s not a real error.

By the way , VBoxVGA and VBoxSVGA is abandoned in the latest version of virtualbox (6.1).

answered Oct 21, 2021 at 1:38

ws_'s user avatar

1

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.

answered Oct 26, 2020 at 14:20

TobyG's user avatar

TobyGTobyG

1413 bronze badges

Содержание

  1. virtualbox.org
  2. «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  3. «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  4. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  5. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  6. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  7. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  8. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  9. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  10. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  11. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  12. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  13. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  14. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  15. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  16. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  17. Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host
  18. virtualbox.org
  19. drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  20. drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  21. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  22. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  23. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  24. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  25. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  26. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  27. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  28. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  29. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  30. virtualbox.org
  31. drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  32. drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  33. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  34. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  35. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  36. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  37. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  38. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  39. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  40. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  41. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  42. virtualbox.org
  43. drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  44. drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  45. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  46. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  47. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  48. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  49. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  50. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  51. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  52. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
  53. Re: drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message

virtualbox.org

End user forums for VirtualBox

  • Board indexGeneralVirtualBox on Windows Hosts
  • Change font size
  • Print view
  • FAQ
  • Login

«Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

«Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by onrocketfalls » 8. Jan 2021, 19:40

I’ve tried multiple solutions I’ve seen after looking through different threads with this same error, but I’m still not finding anything that will help me. On my laptop, I do still get the «Failed to send host log» message, but Ubuntu still boots. In this case, on a different PC, it will not boot after the message below. First, the problem, and then what I’ve tried so far:

After installing Ubuntu on the VM, when I try to start it, I get:
/dev/sda5: recovering journal
/dev/sda5: clean, 198517/2588672 files, 2251253/10353920 blocks
[ 9.295673] [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message.
[ 9.297899] [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message.

So far, I’ve tried:
— Giving it more memory to work with (up to half of my RAM, so 16gbs)
— Reinstalling Ubuntu (about five times)
— Changing the graphics controller to VBoxVGA (didn’t give the same text as above, but didn’t boot either)
— Changing the video memory up to 128mb
— Rebooting with and without the Ubuntu installation iso mounted
— Unchecking the floppy disk in the boot order, and also both unchecking and moving it to the bottom
— Moving the VM installation folder from my SSD where my host OS is to a HDD on the same PC

I have made sure virtualization is enabled in the startup menu and that it has also been enabled in Windows itself.

and maybe some other stuff I forgot, I was at it for like three hours last night trying stuff and retrying stuff I’d already tried. Shelled out for Windows 10 Pro to get virtualization, and then my gaming rig still can’t seem to do a thing that my semi-ancient work laptop with 6gb of RAM can do. pls help

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by scottgus1 » 9. Jan 2021, 01:04

The «Failed to send host log message» error is apparently a bug in the Linux OS’s drivers that appears when the Virtualbox VMSVGA video card for Linux VMs is used. It can safely be ignored and does not interfere with the VM’s operation.

Hope you didn’t pay much. Though Home doesn’t have the ‘virtualization’ you probably thought you needed, it does have the underlying structure, called Hyper-V, which many times interferes with Virtualbox. (Home and Pro both have services that can use Hyper-V. Only Pro can run Hyper-V-based VMs. Read on. )

If this is a Windows PC, right-click the guest in the main Virtualbox window’s guest list, choose Show Log.

Search the far left tab’s log for this text:

Attempting fall back to NEM

If you find it, Hyper-V is enabled. If you are still running 6.1.14 or earlier, update to 6.1.16, and try again.

If the 6.1.16 log still shows these words, Hyper-V needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

If you don’t find that text, save the far left tab’s log, zip the log file, and post the zip file, using the forum’s Upload Attachment tab.

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by onrocketfalls » 9. Jan 2021, 02:54

I’m trying a fresh install now and while I’d love to get to where I can try what you said to try, I can’t even get to the install page. It shows Ubuntu, it shows the spinning loading icon, the icon freezes, and nothing progresses. What a cluster this is turning into. I’ll update as soon as I figure this new and exotic and extremely frustrating problem out (open to suggestions, though).

Edit: Checked the log just for the hell of it, though, and «Attempting fall back to NEM» was in there. I’ll try that route for this problem too.

Edit again: It worked. Thank you, thank you, thank you, thank you, thank you. And also, if you have any suggestions for what Windows 10 Pro is good for over Home, lmk. At least it was only $20.

P.S.: Thank you. I would have probably given up soon.

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by scottgus1 » 9. Jan 2021, 15:40

Great! Glad you’re up and running.

I didn’t know Home could go to Pro for only $20. I might have to do that on my Home laptop & tablet.

Pro has a few other things Home doesn’t have. Pro can join a domain, not much of a biggie for the average user, but good for the office.

The biggest benefit of Pro, to me, in the Windows 10 era, is better control of automatic updates, because of access to the Group Policy Editor. GPE has settings to notify but not download or apply updates until I give the go-ahead (and make sure VMs are all shut down first), which let’s me make backup images beforehand:

Start menu > Run. > gpedit.msc > Local Computer Policy > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates > set «Configure automatic updating» dropdown to 2 (Notify for download and auto install) or possibly 3 (Auto download and notify for install).

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by scottgus1 » 9. Jan 2021, 16:13

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by Paola » 28. Jul 2021, 19:03

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by scottgus1 » 28. Jul 2021, 19:07

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by mpack » 29. Jul 2021, 10:41

For me, the main advantage is that «Pro» has the ability to be an RDP (Remote Desktop Protocol) server. Home editions of Windows can be clients , i.e. they can RDP into RDP servers, but home editions can’t be RDP servers themselves: nothing can call into your home edition Windows PC. A server means that you can install Win10Pro on some small form factor (SFF) box (or single board computer — SBC) that sits in the corner of a room taking up almost no space, but when you need to you can RDP into it from your main PC and access whatever apps caused you to want that small PC in the first place. I have PCs in my home set up to prepare media for a NAS media server (it’s a Synology NAS, but it could have been another PC), I have a PiHole running (though that’s on a Raspberry Pi, also running an RDP server), and I’m considering other functions like my own fully functioned router that I can control better. It opens up a whole new level of gadgetry.

There are probably ways that you can force something similar to RDP server capability onto Win10 Home, but I frankly don’t trust such hacks, so for just a little extra I prefer to have the real thing.

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by Paola » 30. Jul 2021, 18:12

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by scottgus1 » 30. Jul 2021, 18:14

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by Paola » 30. Jul 2021, 18:30

No, no side effects on VirtualBox. This is not to hide error message, this is to solve the error. «nomodeset» says to kernel not load video drivers (xf86-video-vmware eg.) at boot. Instead, use bios settings till the system is properly ok.

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by fth0 » 30. Jul 2021, 19:18

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by Paola » 30. Jul 2021, 19:45

Yes, no error. But i’ve tested only on openSUSE.

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by fth0 » 30. Jul 2021, 20:46

Ok, thanks for checking.

These «*ERROR*» messages do not indicate a real error anyway. Their background is well understood and explained in 19168#comment:4.

Re: «Failed to send log host message.» error using Ubuntu on Windows 10 Pro Host

by Paola » 31. Jul 2021, 04:38

fth0 wrote: Ok, thanks for checking.

These «*ERROR*» messages do not indicate a real error anyway. Their background is well understood and explained in 19168#comment:4.

Thank you very much for this more detailed explanation! I tried to solve the «problem» myself, and I racked my brain trying to solve it. Then when the error stopped, I was so happy that I decided to try to help other people by posting on the forum.

Источник

virtualbox.org

End user forums for VirtualBox

  • Board indexGeneralVirtualBox on Windows Hosts
  • Change font size
  • Print view
  • FAQ
  • Login

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

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

by JamesLin » 18. Jun 2021, 18:15

For whatever reason when I restarted Linux machine, my Linux guest failed normal boot with following error:

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

Give root password for maintenance
(or press Control-D to continue)

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

by scottgus1 » 18. Jun 2021, 18:19

It is a bug in Linux’s driver for the VMSVGA virtual video card. The VM continues to boot if it has no other problems.

The following error is from the OS, not Virtualbox. You’ll have to use the OS’s help channels to fix this one:

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

by JamesLin » 18. Jun 2021, 18:22

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

by scottgus1 » 18. Jun 2021, 18:22

You may have broken something by

Random thrashing does not often help, rather it hurts. It is better, especially after getting on the forum to ask for help, to stop and wait for the help to arrive.

We cannot tell what was damaged in this VM. You may have to start over.

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

by JamesLin » 18. Jun 2021, 18:39

I even restored last working snapshot but it still gives me maintenance mode.

Is there bug in recent VirtualBox? or is this induce by Windows update?

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

by scottgus1 » 18. Jun 2021, 18:40

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

by scottgus1 » 18. Jun 2021, 18:49

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

by janwilmans » 10. May 2022, 15:43

The messages are persisting since 2019,

The message «*ERROR* Failed to send host log message» from vmwgfx can be safely ignored, and seems to have no side-effects, can we just remove it already? Can I help?

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

by mpack » 10. May 2022, 18:35

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

by fth0 » 10. May 2022, 22:08

Источник

virtualbox.org

End user forums for VirtualBox

  • Board indexGeneralVirtualBox on Windows Hosts
  • Change font size
  • Print view
  • FAQ
  • Login

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

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

by JamesLin » 18. Jun 2021, 18:15

For whatever reason when I restarted Linux machine, my Linux guest failed normal boot with following error:

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

Give root password for maintenance
(or press Control-D to continue)

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

by scottgus1 » 18. Jun 2021, 18:19

It is a bug in Linux’s driver for the VMSVGA virtual video card. The VM continues to boot if it has no other problems.

The following error is from the OS, not Virtualbox. You’ll have to use the OS’s help channels to fix this one:

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

by JamesLin » 18. Jun 2021, 18:22

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

by scottgus1 » 18. Jun 2021, 18:22

You may have broken something by

Random thrashing does not often help, rather it hurts. It is better, especially after getting on the forum to ask for help, to stop and wait for the help to arrive.

We cannot tell what was damaged in this VM. You may have to start over.

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

by JamesLin » 18. Jun 2021, 18:39

I even restored last working snapshot but it still gives me maintenance mode.

Is there bug in recent VirtualBox? or is this induce by Windows update?

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

by scottgus1 » 18. Jun 2021, 18:40

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

by scottgus1 » 18. Jun 2021, 18:49

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

by janwilmans » 10. May 2022, 15:43

The messages are persisting since 2019,

The message «*ERROR* Failed to send host log message» from vmwgfx can be safely ignored, and seems to have no side-effects, can we just remove it already? Can I help?

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

by mpack » 10. May 2022, 18:35

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

by fth0 » 10. May 2022, 22:08

Источник

virtualbox.org

End user forums for VirtualBox

  • Board indexGeneralVirtualBox on Windows Hosts
  • Change font size
  • Print view
  • FAQ
  • Login

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

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

by JamesLin » 18. Jun 2021, 18:15

For whatever reason when I restarted Linux machine, my Linux guest failed normal boot with following error:

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

Give root password for maintenance
(or press Control-D to continue)

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

by scottgus1 » 18. Jun 2021, 18:19

It is a bug in Linux’s driver for the VMSVGA virtual video card. The VM continues to boot if it has no other problems.

The following error is from the OS, not Virtualbox. You’ll have to use the OS’s help channels to fix this one:

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

by JamesLin » 18. Jun 2021, 18:22

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

by scottgus1 » 18. Jun 2021, 18:22

You may have broken something by

Random thrashing does not often help, rather it hurts. It is better, especially after getting on the forum to ask for help, to stop and wait for the help to arrive.

We cannot tell what was damaged in this VM. You may have to start over.

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

by JamesLin » 18. Jun 2021, 18:39

I even restored last working snapshot but it still gives me maintenance mode.

Is there bug in recent VirtualBox? or is this induce by Windows update?

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

by scottgus1 » 18. Jun 2021, 18:40

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

by scottgus1 » 18. Jun 2021, 18:49

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

by janwilmans » 10. May 2022, 15:43

The messages are persisting since 2019,

The message «*ERROR* Failed to send host log message» from vmwgfx can be safely ignored, and seems to have no side-effects, can we just remove it already? Can I help?

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

by mpack » 10. May 2022, 18:35

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

by fth0 » 10. May 2022, 22:08

Источник

  • Home
  • Forum
  • The Ubuntu Forum Community
  • Ubuntu Specialised Support
  • Virtualisation
  • [ubuntu] VirtualBox Ubuntu Install Error Messages

  1. Unhappy VirtualBox Ubuntu Install Error Messages

    I’m attempting to install Ubuntu on VirtualBox. (My PC’s OS is Windows 10). After it installed, the following error messages appeared:

    «mtd device must be supplied (device name is empty)»
    «*ERROR* Failed to send host log message»

    When I searched these messages, the general response was that they’re bugs. However, it’s frozen on this screen.

    Does anyone have ideas on how to resolve it?

    Thank you!

    Last edited by ebryski; October 1st, 2022 at 12:31 AM.


  2. Re: VirtualBox Ubuntu Install Error Messages

    Moved to Virtualisation which is a better fit for this question.


  3. Re: VirtualBox Ubuntu Install Error Messages

    Installing Ubuntu in VirtualBox is usually a given.

    That error is a bug, but (usually) does not prevent it from booting. I have 2 machines (metal) that have those error messages and still boot. The error just means that a file is not empty during boot, which then prompts that message. More of a nuisance.

    What is the host machine and OS? What is the version of VirtualBox? What version of Ubuntu are you trying to install?


  4. Re: VirtualBox Ubuntu Install Error Messages

    In addition to MAFoElffen’s questions, do you see something more informative if you open the GRUB menu at VM startup and boot its Ubuntu without quiet splash boot parameters?


  5. Re: VirtualBox Ubuntu Install Error Messages

    Meaning… If, Press <Esc> after the Bios Post messages, at the Grub2 boot menu, press the <E> key. <Arrow-down> to the line that starts with «linux». <Arrow-right> and delete the words «quiet splash». Then press <Cntrl><X> to boot…

    More details on this about mid-post in my «Graphics Resolution» sticky in my signature line…


  6. Re: VirtualBox Ubuntu Install Error Messages

    Quote Originally Posted by MAFoElffen
    View Post

    What is the host machine and OS? What is the version of VirtualBox? What version of Ubuntu are you trying to install?

    In the OP, he says Win10 is the hostOS. Are there different versions of that?

    Don’t see any mention of the vbox version or which Ubuntu release and DE/flavor.

    I put the error message into google and hit enter. Found this: https://askubuntu.com/questions/1417…-name-is-empty Which says it has something to do with systemd and that it has been fixed.

    For someone new, perhaps 22.04 isn’t the best release. There are a number of things that are odd in it as Canonical uses the «defaults» to get more testers.


  7. Re: VirtualBox Ubuntu Install Error Messages

    The error message is a sideline issue, not to be confused with not booting (which that bug report states that.)

    @TheFu — I saw that bug report (https://bugs.launchpad.net/ubuntu/+s…d/+bug/1981622) about a couple weeks ago, when my laptop was still giving that message. The bug (in the details near the end, most recent) says it was patched for 22.10 DEV. Not backported to 22.04 (yet)…

    EDIT: Don’t do the «work-around» that was suggested there. It is a two edged sword. They said that you have to back off that work-around, for the new patch to work… Meaning if you did that work-around, and you get the update with that patch, that it will prevent the patch from being applied… Which I will need to back-off on one of my systems when it gets backported to 22.04 LTS….

    I am part of that Bug Report. I notice that besides me, it also affects oldfred.

    Last edited by MAFoElffen; October 1st, 2022 at 09:33 PM.


  8. Re: VirtualBox Ubuntu Install Error Messages

    If I’m reading that bug correctly, they are just messages and safely ignored. In the old mainframe days, we called them «standard errors», meaning that if the error wasn’t there, it was a problem.

    Is this for all hypervisors or just vbox?
    Also, seems to be for 22.04, not 18.04 or 20.04.


  9. Re: VirtualBox Ubuntu Install Error Messages

    It’s also showing that error when I boot my VMs of Xubuntu 22.10 and 22.04, both running in KVM/QEMU, so it’s not just in VBox.


  10. Re: VirtualBox Ubuntu Install Error Messages

    That’s what I told TheFu in PM. Both for KVM and RHEV.

    But I have an EUFI Laptop (metal) and a Legacy Boot workstation (metal) that are hypervisors that have this error. Their 22.4 & plus guests have this error…

    oldfred’s is on metal and is not a hypervisor… So not just hypervisor’s. I’ve talked to him about possibly running VM’s and he doesn’t run any.

    Last edited by MAFoElffen; October 2nd, 2022 at 03:42 PM.


Tags for this Thread

Bookmarks

Bookmarks


Posting Permissions

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Ask Question

Asked
4 months ago

Modified
3 months ago

Viewed
2k times

0

I am getting this error while restarting my vbox (OS: Ubuntu). It is throwing error as «failed to start docker container engine».
Kindly help me how to resolve this issue. Is there any way where I can stop the docker as I am not able to access the terminal.

enter image description here

  • vbox

edited Sep 22, 2022 at 8:49

Sonali Sethi

asked Sep 22, 2022 at 8:47

Sonali Sethi's user avatar

Sonali SethiSonali Sethi

12 bronze badges

Add a comment
 | 

1 Answer

Sorted by:

Reset to default

1

For me, I ran out of disk space.

I increased the virtual hard drive disk size from 10GB to 100GB, the error disappeared and it than booted normally.

edited Oct 24, 2022 at 3:06

answered Oct 24, 2022 at 3:04

Graham's user avatar

GrahamGraham

112 bronze badges

1

  • Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

    – Community
    Bot

    Oct 27, 2022 at 20:43

Add a comment
 | 

Your Answer

Sign up or log in

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you’re looking for? Browse other questions tagged

  • vbox

or ask your own question.

  • The Overflow Blog
  • Engineering’s hidden bottleneck: pull requests

    sponsored post

  • Three layers to secure a software development organization

  • Featured on Meta
  • Accessibility Update: Colors

  • Collectives: The next iteration

  • Temporary policy: ChatGPT is banned

  • We’ve made changes to our Privacy Notice for Collectives™

Related

0

Connection (offline) to OracleDB on CentOSVM using Vbox doesn’t work

Hot Network Questions

  • At what point is it «legal» to overthrow the government?

  • Fine-tuning of methods before main analysis: p-value hacking?

  • How can we exactly calculate the volume?

  • How does the ability to solve a new problem comes to a person?

  • Aggregate a list in Python without using any libraries

  • Why should bulk modulus always be positive?

  • Writing a vector has a linear combination of two vectors: is the solution unique?

  • My cat is fighting for his life with chronic calicivirus

  • First science fiction story to use the word «laser»?

  • Is Heightened(4th) Silence spell balanced?

  • Why is 1Password sign-in to new device secure without MFA?

  • Roll a painted cube

  • Why isn’t something like compound syscalls not implemented?

  • Distribute arguments over a function in all ordered combinations

  • De Gruyter and De Gruyter Mouton: the difference

  • Is 2 years of recent continuous employment required to get a mortgage?

  • Creating dieline for inkjet printing

  • How to temporarily catch leaks trickling down the outside of a pipe

  • Why are some pH standard solutions 6.86 and 9.18?

  • Why is Turkey campaigning to get their name changed to Türkiye in English but not other languages?

  • Execute reverse search in terminal mode at startup

  • First work to depict Mr. Hyde as superhuman

  • A better long ≝ (defining equals, equals to by definition) without bumps

  • What is done in Revelation 16:17?

more hot questions

Question feed

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Понравилась статья? Поделить с друзьями:
  • Ubuntu error 0x800701bc
  • Ubuntu device descriptor read 64 error 32
  • Ubuntu chroot exec format error
  • Ubuntu busybox initramfs как исправить
  • Ubuntu apt update error