According to https://www.virtualbox.org/ticket/13471 Wayland is supposed to work with VMSVGA in VBox. I'm using VBox 6.1.22 on the host. Guest is slackware-current with 6.1.22 guest extensions running kernel 5.10.33.

Is there special configuration required on the guest to run GUI in Wayland? When I choose any Wayland option in chooser, the UI never loads.

I guess that you should have the guest tools properly installed.

The Wayland desktops needs a functional DRM on the Linux console and MESA.

Since nothing in the installer logs indicates the guest tools are not properly installed, can you provide more detail on how you guess they might not be?
The guest has a complete Slackware current install, no missing pkgs, last updated today.

By "extensions", do you mean the extpack or the guestadditions?

The VBoxGuestAdditions_6.1.22.iso is needed according to the online manual found here
https://www.virtualbox.org/manual/Us...resizing-linux

After trying some things, it seems to work. I had to create a new user to test with, it seems there's something in my normal users init or settings thats stopping or hanging the wayland/plasma initialization.

Look, I am not a specialist on virtual machines, but from what I know regarding the bare metal, you need the KMS active on the Linux console, for Wayland to work. Aka modesettings, DRM and so on.

On the bare metal, this means using the proper and accelerated driver of radeon, amdgpu, i915, nouveau, etc.

modesetting and drm don't require acceleration, it just requires a supported card. Amongst the current hardware the supported cards also include the virtual cards provided by vm managers and a bunch of obsolete hardware. Some provide acceleration, some don't. There's also a bunch of modern SOC hardware which often don't have gpl drivers for their acceleration blocks.

In qemu you can configure an ancient cirrus logic vga card and wayland will even start with that. It's too slow to use but it does work albeit with some reduced fx.

Well, in theory you are right, speaking of Wayland in general. Sure, the Weston can do that, the Wayland/Gnome3 can do that.

BUT, we, on Slackware we have today a single implementation of Wayland: Wayland/Plasma5 and it still needs functional DRI drivers even today.

But, looks like they will fix this on the near future:

https://bugs.kde.org/show_bug.cgi?id=436053
https://invent.kde.org/plasma/kwin/c...05a99656938ce9

Let's remember that on Wayland there is not such thing like a generic Wayland server - they are custom tailored by the Wayland desktop environments.

I'm confused here. I can use any of the plasma session options from the login screen via the dumb bochs vga framebuffer device in qemu, using slackware64-current.

How is that not working on slackware?

Well, looks like your "dumb bochs vga framebuffer" has a DRI device and KMS support, via "bochs-drm" module.

Out of curiosity, you can try to boot your device with "nomodeset" parameter on the kernel parameters, and see if Wayland/Plasma5 still works.

Probably not - as @ZhaoLin1457 is right, they still have to release a KWin(_wayland) version capable to run directly on framebuffer with no DRI support, as you seen in that bug report and the associated patch.

No,
No special configuration required. Wayland and Full Wayland works with VMSVGA enabled virtualbox Slackware-current client (VB 6.1.20/kernel 5.12.x - any kernel supporting VMSVGA will do).
Full Wayland is slow, Wayland works but some glitches need to be fixed (e.g. mouse pointer does not work in kate).

by the way the output of your command
is weird.
It should not show anything except video modules. In your case it shows
no way that this is
command... unless vboxsf is video module

proper output: