Virtualbox 7.2 Linux Guests keep freezing

[tinfoil-hat]

These are the logs of my Kali VM:

Logs/VBox.log:00:00:00.898434 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
Logs/VBox.log:00:00:01.089883   XSaveErPtr - Save/restore error pointers (FXSAVE/RSTOR) = 0 (1)
Logs/VBox.log:00:00:03.758982 VM: Raising runtime error 'DrvVD_DEKMISSING' (fFlags=0x6)
Logs/VBox.log:00:00:03.762028 Console: VM runtime error: fatal=false, errorID=DrvVD_DEKMISSING message="VD: The DEK for this disk is missing"
Logs/VBox.log:19:23:00.201632 VMMDev: Guest Log: 20:10:55.015467 seamless  Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down20:10:55.187094 seamless  Error: Failed to open X11 display
Logs/VBox.log.1:00:00:01.063745 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
Logs/VBox.log.1:00:00:01.254725   XSaveErPtr - Save/restore error pointers (FXSAVE/RSTOR) = 0 (1)
Logs/VBox.log.1:00:00:03.928096 VM: Raising runtime error 'DrvVD_DEKMISSING' (fFlags=0x6)
Logs/VBox.log.1:00:00:03.930540 Console: VM runtime error: fatal=false, errorID=DrvVD_DEKMISSING message="VD: The DEK for this disk is missing"
Logs/VBox.log.1:10:58:16.301563 VMMDev: Guest Log: 17:47:11.250203 dnd       Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down17:47:11.409255 seamless  Error: Failed to open X11 display
Logs/VBox.log.2:00:00:01.054256 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
Logs/VBox.log.2:00:00:01.218681   XSaveErPtr - Save/restore error pointers (FXSAVE/RSTOR) = 0 (1)
Logs/VBox.log.2:00:00:03.891193 VM: Raising runtime error 'DrvVD_DEKMISSING' (fFlags=0x6)
Logs/VBox.log.2:00:00:03.893826 Console: VM runtime error: fatal=false, errorID=DrvVD_DEKMISSING message="VD: The DEK for this disk is missing"
Logs/VBox.log.2:00:01:00.691813 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.2:00:01:00.692817 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.2:00:08:57.191710 VMMDev: Guest Log: 06:40:59.697059 main      Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down06:40:59.743155 control  Guest control service stopped
Logs/VBox.log.2:00:09:28.027639 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.2:00:09:28.028672 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.2:00:10:41.655714 VMMDev: Guest Log: 06:40:59.918712 main      Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down06:40:59.919341 RTThrdPP  Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut downBIOS: VirtualBox 7.2.4
Logs/VBox.log.2:00:13:29.546672 VMMDev: Guest Log: 06:45:31.825730 main      Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down06:45:31.826220 main      Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down06:45:31.929656 control  Guest control service stopped
Logs/VBox.log.2:00:16:38.547616 VMMDev: Guest Log: 06:48:40.986211 dnd       Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down06:48:41.039886 main      Error: Failed to open X11 display
Logs/VBox.log.2:00:16:39.353903 VMMDev: Guest Log: 06:48:41.252334 main      Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down06:48:41.252840 main      Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down06:48:41.846480 seamless  Error: Failed to open X11 display
Logs/VBox.log.3:00:00:01.134372 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
Logs/VBox.log.3:00:00:01.322066   XSaveErPtr - Save/restore error pointers (FXSAVE/RSTOR) = 0 (1)
Logs/VBox.log.3:00:00:03.995543 VM: Raising runtime error 'DrvVD_DEKMISSING' (fFlags=0x6)
Logs/VBox.log.3:00:00:03.999467 Console: VM runtime error: fatal=false, errorID=DrvVD_DEKMISSING message="VD: The DEK for this disk is missing"
Logs/VBox.log.3:00:04:50.270576 VMMDev: Guest Log: 06:31:14.594194 main      Error: A fatal guest X Window error occurred. This may just mean that the Window system was shut down06:31:14.707571 control  Guest control service stopped

 

[tinfoil-hat]

Here they are with syntax highlighting:

PrivateBin

Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.

bin.tinfoil-hat.net

PrivateBin

Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.

bin.tinfoil-hat.net

 

[jpnilson]

I found where the Virtualbox logs are, using grep I found these errors:

Logs/VBox.log:00:00:03.235111 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
Logs/VBox.log:00:00:03.500684   XSaveErPtr - Save/restore error pointers (FXSAVE/RSTOR) = 0 (1)
Logs/VBox.log:00:15:44.365967 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log:00:15:44.366629 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.1:00:00:02.562494   XSaveErPtr - Save/restore error pointers (FXSAVE/RSTOR) = 0 (1)
Logs/VBox.log.2:00:00:04.205312 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
Logs/VBox.log.2:00:00:04.491300   XSaveErPtr - Save/restore error pointers (FXSAVE/RSTOR) = 0 (1)
Logs/VBox.log.2:05:23:12.848314 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.2:05:23:12.848908 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.2:07:37:57.257572 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.2:07:37:57.258128 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.2:07:38:06.611517 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.2:07:38:06.612163 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.3:00:00:00.851557 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
Logs/VBox.log.3:00:00:01.127407   XSaveErPtr - Save/restore error pointers (FXSAVE/RSTOR) = 0 (1)
Logs/VBox.log.3:00:00:39.522257 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.3:00:00:39.522800 QDBus inhibition call error for service org.freedesktop.ScreenSaver: org.freedesktop.DBus.Error.InvalidSignature. Unexpected reply signature: got "<empty signature>", expected "u" (uint)
Logs/VBox.log.3:00:02:37.729416 VMMDev: Guest Log: 19:17:24.196534 main     VBoxClient VMSVGA: Error: Service ended with error VERR_NET_CONNECTION_RESET_BY_PEER

Iooks like you need to reinstall virtualbox guest additions.

 

[bob466]

Some Distros don't run very well in Virtualbox either.

An example...Mint Cinnamon 22.2...freezing and no sound...yet when installed on my spare SSD it works just fine.

 

[PuppyHome]

Since you found no solution since yesterday then it's time to use something more natural for Linux like qemu, virt-manager.

I can't say you won't XP same issue, it happened to me on few occasions as well with quemu after guest was running for longer time.
It appears to happen when guest is idle or when you do nothing with it.

You won the internet today!

Seriously though. In my personal experience nothing holds a candle to Linux's 'native' virtualization application.
The aforementioned 3rd party software is (somewhat) okay for trying out whatever distro or for short periods to use for doing some specific stuff. But when it comes to actually using a virtual machine all day every day nothing beats QEMU/KVM.

For example right now I'm typing this comment from Parrot OS: 5GB of RAM allocated and 5 'CPU's'. That's it. And it will run all day, forwards USB devices effortlessly and without a hitch with just one click. Never any user issues which comes with the the other virtualization solution we hear and read about on a regular basis.

I've never had an issue with freezing after not using it for a while. When I'd be AFK for a longer bit I'd log out of the VM and log back in after like an hour or two and I'm good to go.
The only thing I'd encounter (every now and then, not nearly always) is losing the 'visual input device' (or something to that effect) and even then, 90% of the time that issue is resolved with one move of the mouse. The other 10% would force me to shut down the VM and restart.

My 2 cents.

 

[bob466]

I've just installed Mint xfce 22.2 in Virtualbox..no freezing and sound works just fine...with the same settings as Cinnamon 22.2.

 

[jpnilson]

Iooks like you need to reinstall virtualbox guest additions.

were you able to reinstall guest addition? The errors in your log seemed to be directly related to that.

 

[CaffeineAddict]

These are the logs of my Kali VM:

There you go, this why I'll never embrace or recommend VBox or any other virtualization software similar to it like vmware etc., other than QEUMU/KVM.

Same applies to other similar software, they're mostly corporal that follow their own standards and disregard standards established by Linux communities, such as XDG Base Directory Specification.

1. Such software writes logs to non standard location, opposite to what every other Linux software does, making troubleshooting harder.
2. Conseqently the loging format in unlike traditional loging of well established loging formats used by 99% of Linux software, which means you need to consult developers or software publisher to interpret your logs.
3. Most likely you can't use journalctl to find log entries either.
4. Probably unrelated to distro you're using, but virtualbox is put into "contrib" component in Debian's repo, meaning part of the code contains licenses incompatible with free software vision established by your distro maintainers.
5. VBox is as already said, non native solution (for obvious reasons so far, that are only partial, there is more)

 

[GatorsFan]

Have you tried and disable 3D Acceleration in Virtualbox ?