xorg-dri-virtio was added via REGEXP to work around the package
missing issue on p9. But it didn't work.

xorg-dri-virtio is a separate package in Mesa 21.1.
But in p9 Mesa 21.0, so the package is added to regexp.

Already in the mainline linux kernel >= 5.10.

There are a few more targets used for Workstation
and Simply images that are rather better plugged
here than patched there.

(still preferring 80-char wide xterm for proofreading)

It's actually sisyphus jeos image that needed this:
open-vm-tools got installed and then removed just
before the final reboot (unlike p8 jeos); not clear
what exactly caused this as subsequent installation
only pulled in libdnet and libicu56, neither of which
were excplicitly removed during cleanup.

Let's make the image a bit leaner until someone asks
for VMware support there.

+vmguest should work everywhere it can at all either;
it's most advanced on x86_64 in terms of hypervisors
available; still aarch64 has kvm too.

'twas somewhat incomplete otherwise,
and these two packages are pretty tiny.

Note that +vmguest is affected too.

xorg-drv-vmmouse should accompany xorg-drv-vmware.
Reported-by: Anton Farygin <rider@altlinux.com>

This might be an overreaction but let's handle
non-x86 virtualization on per-case basis.

Thanks sbolshakov@ for the notice.

This has long been a TODO item but an elegant solution
just didn't come until the night before starterkits...
some services (mostly those operating on real hardware)
do not fit virtual environments at all, won't even start.

These are aimed to test the modules.d/ and auto-pickup
implementation as well as to present an example.

At least 50-net might change (or just get renamed to avoid
auto-pickup) some day as the "net" feature's meaning is
to provide networking upon bootup and these modules are
only needed within stage1 if we're going to netboot;
and that's quite different thing.

armh-cubox bits are prone to get renamed/generalized too
since e.g. ArmadaXP based server images are going to need
this as well.

use/vmguest/vbox/base used to pull in DRM modules
which are required for vboxvideo but useless without
xorg bits; and all of these aren't needed in jeos.

Things might break, doublecheck please.

xorg-drv-vmware is desirable for guests with X11
but undesirable for text-only ones; let's provide
this knob at least but ideal m-p would figure out
that an image with use/x11 and use/vmguest/vmware
should receive this intersection either.

led-ws kernel flavour has gained kernel-modules-vmware
recently, let's add this to the appropriate targets.

It's used in regular-jeos already but THE_ part was missing.

Thanks ildar@ for #30024 and specifically mentioning
that mptspi.ko is missing in jeos flavour (using led-ws).

So as to bring the name bits into harmony with use/install2 ones.

led@ has different kernel-modules-* package set,
some of those "standard" names are provided but
vbox* is not the case.

As our macros and helpers will grok this just fine,
let's add both variants so what's present gets in.

This reverts commit ae441691
as libglx has been fixed already; see #27340 and #28782 for
the details, huge thanks go to Alexey Borisenkov for his
thorough investigation and patches as well as to shrek@
and sin@ for their cooperation to get this fixed in Sisyphus.

This is to cope with #28782 while the culprit is being found out;
not much of a loss while #27340 is open (thus no 3D with vboxdrv
anyways).

I chose to avoid pulling the service related machinery into
vmguest (and haven't got around to factoring it out from live
feature's scripts into a standalone form) so had to tweak these
as well.

Thanks make(1) for the warning, `vmguest' target was
getting pulled in twice indeed.

The "vm" name became a bit confusing with the introduction
of build-vm feature; let's call this one "vmguest" until we do
hierarchical (sub)features.