VirtualBox Guest Extension issue

I have just set up 3 new Virtualbox with W10, Arch and Manjaro both on KDE Plasma.

My old setup VM with XFCE Manjaro did have Foldershare, Drag and Drop Extension working fine.

Now, On Windows set up with Insert Guest extension that works fine, but on both Linux VM I could not get that to work.

What I try was linux61, 66 and 67 with all packages needed, the setup with linux66 is:

❯ pacman -Qs virtualbox
local/linux66 6.6.19-1
    The Linux66 kernel and modules
local/linux66-virtualbox-host-modules 7.0.14-9 (linux66-extramodules)
    Virtualbox host kernel modules for Manjaro Kernel
local/virtualbox 7.0.14-2
    Powerful x86 virtualization for enterprise as well as home use
local/virtualbox-ext-oracle 7.0.14-1
    Oracle VM VirtualBox Extension Pack
local/virtualbox-ext-vnc 7.0.14-2
    VirtualBox VNC extension pack
local/virtualbox-guest-iso 7.0.14-1
    The official VirtualBox Guest Additions ISO image
local/virtualbox-guest-utils 7.0.14-2
    VirtualBox Guest userspace utilities
local/virtualbox-sdk 7.0.14-2
    VirtualBox Software Developer Kit (SDK)
❯ pacman -Qs linux66
local/linux66 6.6.19-1
    The Linux66 kernel and modules
local/linux66-acpi_call 1.2.2-46 (linux66-extramodules)
    A linux kernel module that enables calls to ACPI methods through /proc/acpi/call
local/linux66-broadcom-wl (linux66-extramodules)
    Broadcom 802.11 Linux STA wireless driver
local/linux66-headers 6.6.19-1
    Header files and scripts for building modules for Linux66 kernel
local/linux66-nvidia 550.54.14-2 (linux66-extramodules)
    NVIDIA drivers for linux
local/linux66-virtualbox-host-modules 7.0.14-9 (linux66-extramodules)
    Virtualbox host kernel modules for Manjaro Kernel

With sudo ls /media
I can see my Share folder, but I could not mount them.

By trying to Update Guest Additions, I get this error:

Name: /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso

Automatic update of Guest Additions has failed: files were installed, but kernel modules were not reloaded automatically. Please consider rebooting the guest.
Result Code:
IGuestSession {234f0627-866d-48c2-91a5-4c9d50f04928}

also run the insert sudo ./ or the other files and reboot did not help.

I’m happy for any help.

My System
  Kernel: 6.6.19-1-MANJARO arch: x86_64 bits: 64
  Desktop: Xfce v: 4.18.1 Distro: Manjaro Linux
  Type: Laptop System: Dell product: XPS 15 9570 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 0D0T05 v: A00 serial: <superuser required> UEFI: Dell
    v: 1.31.0 date: 03/13/2023
  ID-1: BAT0 charge: 32.1 Wh (100.0%) condition: 32.1/97.0 Wh (33.0%)
  Info: 6-core model: Intel Core i7-8750H bits: 64 type: MT MCP cache:
    L2: 1.5 MiB
  Speed (MHz): avg: 2928 min/max: 800/4100 cores: 1: 3104 2: 3117 3: 3130
    4: 3122 5: 3123 6: 3130 7: 3125 8: 3130 9: 800 10: 3120 11: 3109 12: 3130
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia
    v: 550.54.14
  Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 driver: X:
    loaded: modesetting,nvidia dri: iris gpu: i915 resolution: 1: 1920x1080~60Hz
    2: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,kms_swrast,nvidia,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.0.2-manjaro1.1
    renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  API: Vulkan v: 1.3.276 drivers: intel,nvidia surfaces: xcb,xlib
  Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel
  API: ALSA v: k6.6.19-1-MANJARO status: kernel-api
  Server-1: PipeWire v: 1.0.3 status: active
  Device-1: Intel Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
  IF: wlp59s0 state: up mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: pan1 state: down mac: <filter>
  Device-1: Intel Wireless-AC 9260 Bluetooth Adapter driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: <filter> bt-v: 5.1
  Local Storage: total: 1.82 TiB used: 1.6 TiB (87.9%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
    size: 1.82 TiB
  ID-1: / size: 1.79 TiB used: 1.6 TiB (89.3%) fs: ext4 dev: /dev/dm-0
  ID-2: /boot/efi size: 256 MiB used: 220 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-1: swap-1 type: file size: 13.02 GiB used: 2.19 GiB (16.8%)
    file: /swapfile
  System Temperatures: cpu: 97.0 C pch: 64.0 C mobo: 76.0 C
  Fan Speeds (rpm): cpu: 4890 fan-2: 4878
  Memory: total: 32 GiB note: est. available: 30.97 GiB used: 15.38 GiB (49.6%)
  Processes: 525 Uptime: 3h 17m Shell: Zsh inxi: 3.3.33

Search is your friend :mag: upper right corner

Manjaro and Arch guests does not require guest ISO - in fact you may harm the system using it.

  • On Manjaro mhwd handles the system related packages on installation
  • On Arch you need to install virtualbox-guest-utils

See #manjaro-guest-configuration for more information (applicable for Arch as well)


Thanks for your Guide.

Well, then your Guide seems outdated, because it pointed to that ISO and the AUR.

I’m stuck at that Guide already at:

 status vboxservice
○ vboxservice.service - VirtualBox Guest Service
     Loaded: loaded (/usr/lib/systemd/system/vboxservice.service; enabled; preset: disabled)
     Active: inactive (dead)
  Condition: start condition unmet at Wed 2024-03-13 10:01:09 CET; 20min ago
             └─ ConditionVirtualization=oracle was not met

Mär 13 10:01:09 terashy systemd[1]: VirtualBox Guest Service was skipped because of an unmet condition check (ConditionVirtualization=oracle).

Just for giggle, I did also set up an XFCE VM, and there everything is fine.
So the problem is somehow in combine with KDE Plasma.

also, Plasma was really a bumpy Road until all 400-500 Package updated by a fresh installation. The Systems Freeze multiply times, changed in to Black screen and force me to Hard restart,

At the end I was really afraid to playing around in the settings while the update was going, it is long ago I felt that way…

Why do you think that?

The list is not mandatory - it is a guide - and the guide is generic - if you install a windows guest you need the guest ISO - if you install a Manjaro guest - you do not.

If you need the service provided by the extension - you need the extensions - if you do not need the advanced options then you do not.

You are aware that the guest utils package is to be installed inside the guest - right ?
And the service is to enabled inside the guest - right ?

The virtualbox-guest-utils package is packaged upstream - so if the service condition is not met - perhpas due to a change in VirtualBox - that will have to be reported upstream.

Manjaro Team does not fix upstream issues.

 $ pamac info virtualbox-guest-utils
Name                  : virtualbox-guest-utils
Version               : 7.0.14-2
Description           : VirtualBox Guest userspace utilities
URL                   :
Licenses              : GPL custom:CDDL
Repository            : extra
Installed Size        : 4,0 MB
Groups                : --
Depends On            : glibc pam libx11 libxcomposite libxdamage libxext libxfixes libxmu libxt xorg-xrandr
                        xf86-video-vmware VIRTUALBOX-GUEST-MODULES
Optional Dependencies : --
Provides              : --
Replaces              : virtualbox-archlinux-additions virtualbox-guest-additions virtualbox-guest-dkms
Conflicts With        : virtualbox-archlinux-additions virtualbox-guest-additions virtualbox-guest-utils-nox
Packager              : Christian Hesse <>
Build Date            : fre 19 jan 2024 14:54:29 CET
Validated By          : MD5 Sum  SHA-256 Sum  Signature

Because you said I don’t need that.

This Post is about pointing out that there is en error, if anyone have the same issue I’m glad to hear about it and maybe find a solution are got the in confirmation that more people have the same issue.

If you want to share the information that there is an Upstream issue going, that is fine as well. So we can expand and create an upstream issue if needed.

Then reread my comment.

You specifically mention Manjaro and Arch guest - and for those you don’t need the guest ISO - which I specifically pointed out.

I use VirtualBox every day - Linux and Windows alike and I have no problems with shared folders.

The guide has been written using that knowledge and occasional maintained if I encounter issue.

But I rarely do - thus the guide has been the same for a long time.

However - due to your way of reading - I have specifically noted that the guest ISO and the extensions are optional components depending on your use case.

I mention, I did set up two VM, one with Manjaro KDE Plasma and one with Arch KDE Plasma to compare while using Manjaro XFCE.

And show the Package I used, there was no attack against you are anyone.
I’m glad it’s working for you, what I did mention was “I try and fail” so I pointed that out.

So has you knowhow it should be done and see the error above how it should be done. I would be happy to hear about it.

Which is what I responded to when I say - you don’t need to do that with Manjaro or Arch.

Well - the virtualbox-guest-utils which provides the vboxservice is to be installed into the Manjaro or Arch guest NOT the host.

I think you have installed the package to the host - and therefore when you attempt to start the service - it will exit with the condition not met message.

So in reality your issues is caused by misunderstanding and installing the a package where it is of no use…

I cannot think of any knowledge I have - related to VirtualBox - which is not in the topic I linked you to.

Sample VM
 $ systemctl status vboxservice --no-pager
● vboxservice.service - VirtualBox Guest Service
     Loaded: loaded (/usr/lib/systemd/system/vboxservice.service; enabled; preset: disabled)
     Active: active (running) since Wed 2024-03-13 12:52:16 CET; 46min ago
    Process: 289 ExecStartPre=/usr/bin/modprobe vboxguest (code=exited, status=0/SUCCESS)
    Process: 294 ExecStartPre=/usr/bin/modprobe vboxvideo (code=exited, status=0/SUCCESS)
    Process: 300 ExecStartPre=/usr/bin/modprobe vboxsf (code=exited, status=0/SUCCESS)
   Main PID: 312 (VBoxService)
      Tasks: 9 (limit: 4676)
     Memory: 4.0M (peak: 6.7M)
        CPU: 126ms
     CGroup: /system.slice/vboxservice.service
             └─312 /usr/bin/VBoxService -f

mar 13 12:52:16 nix-virtualbox VBoxService[312]: 11:52:16.183150 main     7.0.14 r161095 started. Verbose level = 0
mar 13 13:15:43 nix-virtualbox VBoxService[327]: 12:15:43.384517 main     VBoxClient 7.0.14 r161095 (verbosity: 0) linux.amd64 (Jan 19 2024 13:54:29) release log
mar 13 13:15:43 nix-virtualbox VBoxService[327]: 12:15:43.384518 main     Log opened 2024-03-13T12:15:43.384514000Z
mar 13 13:15:43 nix-virtualbox VBoxService[327]: 12:15:43.384783 main     OS Product: Linux
mar 13 13:15:43 nix-virtualbox VBoxService[327]: 12:15:43.384866 main     OS Release: 6.6.19-1-MANJARO
mar 13 13:15:43 nix-virtualbox VBoxService[327]: 12:15:43.384973 main     OS Version: #1 SMP PREEMPT_DYNAMIC Fri Mar  1 18:16:16 UTC 2024
mar 13 13:15:43 nix-virtualbox VBoxService[327]: 12:15:43.385140 main     Executable: /usr/bin/VBoxDRMClient
mar 13 13:15:43 nix-virtualbox VBoxService[327]: 12:15:43.385140 main     Process ID: 327
mar 13 13:15:43 nix-virtualbox VBoxService[327]: 12:15:43.385140 main     Package type: LINUX_64BITS_GENERIC (OSE)
mar 13 13:15:43 nix-virtualbox VBoxService[327]: 12:15:43.385515 main     VBoxDRMClient: already running, exiting

 $ inxi -M
  Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2
    serial: <superuser required>
  Mobo: Oracle model: VirtualBox v: 1.2
    serial: <superuser required> BIOS: innotek GmbH v: VirtualBox
    date: 12/01/2006

You are right, I misunderstand that part.
I guess because of setting up XFCE in the VM this part is used to be already done, and ready to go.
So I did also not recognize that guide part and flayed over it.

Now also I run in to that copy and paste problem you have posted where I also just recognize on KDE Plasma

So now is the Share Folder working, problem is that above, freeze and black screen some time.
Just a bit less with 3D Acceleration turn off.

Again, thank you so far for your Guide.

Copy and Paste works on Plasma(X11)

Now that’s something I was unaware of, despite using VB for years now! Thanks for that tip.

N.B.: Without previously knowing this, I did wonder why when inserting the Guest ISO, the guest OS (Manjaro KDE Unstable in this case) treated it like any other media and displayed the contents in the file manager.