Startjob

[Kruedelzuur]

ich habe debian 12
Wenn ich debian 12 in der virtualbox starte habe ich einen 5 menütigen Startjob.
Wiekann ich den Startjob beenden oder verkürzen?

[MSfree]

Wiekann ich den Startjob beenden oder verkürzen?

Code: Alles auswählen

systemd-analyze blame

?

Vermutlich Timeout bei der nicht erfolgreichen Netzwerkkonfiguration.

[Kruedelzuur]

Code: Alles auswählen

systemd-analyze blame
5min 8.144s plymouth-quit-wait.service
 5min 209ms vboxadd.service
     2.748s fwupd.service
     1.940s dev-sda1.device
     1.502s e2scrub_reap.service
     1.203s NetworkManager-wait-online.service
     1.106s systemd-binfmt.service
     1.103s udisks2.service
     1.078s apparmor.service
      966ms apt-daily.service
      951ms accounts-daemon.service
      886ms NetworkManager.service
      809ms networking.service
      788ms ModemManager.service
      781ms systemd-random-seed.service
      694ms power-profiles-daemon.service
      694ms apt-daily-upgrade.service
      673ms polkit.service
      670ms switcheroo-control.service
      573ms blueman-mechanism.service
      544ms systemd-logind.service
      535ms avahi-daemon.service
      503ms keyboard-setup.service

Und was nun?

[MSfree]

Ich bin zwar kein Virtualbox Experte (mehr), aber vboxadd.service hört sich nach Virtual Box Guest Additions an. Sind die bei dir installiert?

[Kruedelzuur]

Ja sind installiert. Weiss jemand Rat?

[MSfree]

Hast du schonmal ins Systemlog geschaut?

Code: Alles auswählen

journalctl --catalog --unit=vboxadd

?

[Kruedelzuur]

Code: Alles auswählen

journalctl --catalog --unit=vboxadd
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal' can see all messages.
      Pass -q to turn off this notice.
-- No entries --

Sieht so aus als hätte es nicht geklappt, weiss jemand Rat?

[JTH]

Sieht so aus als hätte es nicht geklappt, weiss jemand Rat?

Du siehst da mangels Berechtigung keine Logmeldungen. Führe den vorgeschlagenen journalctl-Aufruf entweder als root oder mit sudo aus, dann kommen auch etwaige Meldungen. Oder füg deinen Benutzer zur Gruppe systemd-journal hinzu.

[Kruedelzuur]

un 1

Code: Alles auswählen

7 07:49:13 debian systemd[1]: Starting vboxadd.service...
░░ Subject: A start job for unit vboxadd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has begun execution.
░░ 
░░ The job identifier is 2022.
Jun 17 07:49:14 debian vboxadd[3971]: VirtualBox Guest Additions: Starting.
Jun 17 07:49:14 debian vboxadd[3996]: VirtualBox Guest Additions: Setting up mo>
Jun 17 07:49:14 debian vboxadd[4005]: VirtualBox Guest Additions: Building the >
Jun 17 07:49:14 debian vboxadd[4005]: modules.  This may take a while.
Jun 17 07:49:14 debian vboxadd[4007]: VirtualBox Guest Additions: To build modu>
Jun 17 07:49:14 debian vboxadd[4009]: VirtualBox Guest Additions:   /sbin/rcvbo>
Jun 17 07:49:14 debian vboxadd[4011]: VirtualBox Guest Additions: or
Jun 17 07:49:14 debian vboxadd[4013]: VirtualBox Guest Additions:   /sbin/rcvbo>
Jun 17 07:49:14 debian vboxadd[4015]: VirtualBox Guest Additions: Kernel header>
Jun 17 07:49:14 debian vboxadd[4015]: 6.1.0-9-amd64. Please install them and ex>
Jun 17 07:49:14 debian vboxadd[4015]:   /sbin/rcvboxadd setup
Jun 17 07:49:14 debian useradd[4016]: failed adding user 'vboxadd', exit code: 9
Jun 17 07:49:14 debian useradd[4017]: failed adding user 'vboxadd', exit code: 9
Jun 17 07:49:15 debian vboxadd[4033]: VirtualBox Guest Additions: Running kerne>
Jun 17 07:49:15 debian vboxadd[4033]: the system is restarted or 'rcvboxadd rel>
lines 1-23...skipping...
Jun 17 07:49:13 debian systemd[1]: Starting vboxadd.service...
░░ Subject: A start job for unit vboxadd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has begun execution.
░░ 
░░ The job identifier is 2022.
Jun 17 07:49:14 debian vboxadd[3971]: VirtualBox Guest Additions: Starting.
Jun 17 07:49:14 debian vboxadd[3996]: VirtualBox Guest Additions: Setting up modules
Jun 17 07:49:14 debian vboxadd[4005]: VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
Jun 17 07:49:14 debian vboxadd[4005]: modules.  This may take a while.
Jun 17 07:49:14 debian vboxadd[4007]: VirtualBox Guest Additions: To build modules for other installed kernels, run
Jun 17 07:49:14 debian vboxadd[4009]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
Jun 17 07:49:14 debian vboxadd[4011]: VirtualBox Guest Additions: or
Jun 17 07:49:14 debian vboxadd[4013]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
Jun 17 07:49:14 debian vboxadd[4015]: VirtualBox Guest Additions: Kernel headers not found for target kernel
Jun 17 07:49:14 debian vboxadd[4015]: 6.1.0-9-amd64. Please install them and execute
Jun 17 07:49:14 debian vboxadd[4015]:   /sbin/rcvboxadd setup
Jun 17 07:49:14 debian useradd[4016]: failed adding user 'vboxadd', exit code: 9
Jun 17 07:49:14 debian useradd[4017]: failed adding user 'vboxadd', exit code: 9
Jun 17 07:49:15 debian vboxadd[4033]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
Jun 17 07:49:15 debian vboxadd[4033]: the system is restarted or 'rcvboxadd reload' triggered
Jun 17 07:49:15 debian vboxadd[3971]: VirtualBox Guest Additions: reloading kernel modules and services
Jun 17 07:54:14 debian systemd[1]: vboxadd.service: start operation timed out. Terminating.
Jun 17 07:54:14 debian systemd[1]: vboxadd.service: Main process exited, code=killed, status=15/TERM
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit vboxadd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 15.
Jun 17 07:54:14 debian systemd[1]: vboxadd.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service has entered the 'failed' state with result 'timeout'.
Jun 17 07:54:14 debian systemd[1]: vboxadd.service: Unit process 4417 (systemctl) remains running after unit stopped.
Jun 17 07:54:14 debian systemd[1]: Failed to start vboxadd.service.
░░ Subject: A start job for unit vboxadd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has finished with a failure.
░░ 
░░ The job identifier is 2022 and the job result is failed.
Jun 17 07:54:14 debian systemd[1]: vboxadd.service: Consumed 1.940s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service completed and consumed the indicated resources.
-- Boot 025786a8d88a4b86ac1a8c81129d4b6f --
Jun 18 09:38:37 debian systemd[1]: Starting vboxadd.service...
░░ Subject: A start job for unit vboxadd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has begun execution.
░░ 
░░ The job identifier is 129.
Jun 18 09:38:39 debian vboxadd[488]: VirtualBox Guest Additions: Starting.
Jun 18 09:38:39 debian vboxadd[637]: VirtualBox Guest Additions: Setting up modules
Jun 18 09:38:39 debian vboxadd[646]: VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
Jun 18 09:38:39 debian vboxadd[646]: modules.  This may take a while.
Jun 18 09:38:39 debian vboxadd[648]: VirtualBox Guest Additions: To build modules for other installed kernels, run
Jun 18 09:38:39 debian vboxadd[650]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
Jun 18 09:38:39 debian vboxadd[652]: VirtualBox Guest Additions: or
Jun 18 09:38:39 debian vboxadd[654]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
Jun 18 09:38:39 debian vboxadd[656]: VirtualBox Guest Additions: Kernel headers not found for target kernel
Jun 18 09:38:39 debian vboxadd[656]: 6.1.0-9-amd64. Please install them and execute
Jun 18 09:38:39 debian vboxadd[656]:   /sbin/rcvboxadd setup
Jun 18 09:38:39 debian useradd[657]: failed adding user 'vboxadd', exit code: 9
Jun 18 09:38:39 debian useradd[658]: failed adding user 'vboxadd', exit code: 9
Jun 18 09:38:40 debian vboxadd[674]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
Jun 18 09:38:40 debian vboxadd[674]: the system is restarted or 'rcvboxadd reload' triggered
Jun 18 09:38:40 debian vboxadd[488]: VirtualBox Guest Additions: reloading kernel modules and services
Jun 18 09:43:37 debian systemd[1]: vboxadd.service: start operation timed out. Terminating.
Jun 18 09:43:37 debian systemd[1]: vboxadd.service: Main process exited, code=killed, status=15/TERM
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit vboxadd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 15.
Jun 18 09:43:37 debian systemd[1]: vboxadd.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service has entered the 'failed' state with result 'timeout'.
Jun 18 09:43:37 debian systemd[1]: vboxadd.service: Unit process 1092 (systemctl) remains running after unit stopped.
Jun 18 09:43:37 debian systemd[1]: Failed to start vboxadd.service.
░░ Subject: A start job for unit vboxadd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has finished with a failure.
░░ 
░░ The job identifier is 129 and the job result is failed.
Jun 18 09:43:37 debian systemd[1]: vboxadd.service: Consumed 1.900s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service completed and consumed the indicated resources.
-- Boot 0c473fdb50684685b24a6824295c2446 --
Jun 19 02:54:04 debian systemd[1]: Starting vboxadd.service...
░░ Subject: A start job for unit vboxadd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has begun execution.
░░ 
░░ The job identifier is 102.
Jun 19 02:54:05 debian vboxadd[511]: VirtualBox Guest Additions: Starting.
Jun 19 02:54:05 debian vboxadd[635]: VirtualBox Guest Additions: Setting up modules
Jun 19 02:54:05 debian vboxadd[644]: VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
Jun 19 02:54:05 debian vboxadd[644]: modules.  This may take a while.
Jun 19 02:54:05 debian vboxadd[646]: VirtualBox Guest Additions: To build modules for other installed kernels, run
Jun 19 02:54:05 debian vboxadd[648]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
Jun 19 02:54:05 debian vboxadd[651]: VirtualBox Guest Additions: or
Jun 19 02:54:05 debian vboxadd[653]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
Jun 19 02:54:05 debian vboxadd[655]: VirtualBox Guest Additions: Kernel headers not found for target kernel
Jun 19 02:54:05 debian vboxadd[655]: 6.1.0-9-amd64. Please install them and execute
Jun 19 02:54:05 debian vboxadd[655]:   /sbin/rcvboxadd setup
Jun 19 02:54:05 debian useradd[656]: failed adding user 'vboxadd', exit code: 9
Jun 19 02:54:05 debian useradd[659]: failed adding user 'vboxadd', exit code: 9
Jun 19 02:54:06 debian vboxadd[677]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
Jun 19 02:54:06 debian vboxadd[677]: the system is restarted or 'rcvboxadd reload' triggered
Jun 19 02:54:06 debian vboxadd[511]: VirtualBox Guest Additions: reloading kernel modules and services
Jun 19 02:59:04 debian systemd[1]: vboxadd.service: start operation timed out. Terminating.
Jun 19 02:59:04 debian systemd[1]: vboxadd.service: Main process exited, code=killed, status=15/TERM
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit vboxadd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 15.
Jun 19 02:59:04 debian systemd[1]: vboxadd.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service has entered the 'failed' state with result 'timeout'.
Jun 19 02:59:04 debian systemd[1]: vboxadd.service: Unit process 1113 (systemctl) remains running after unit stopped.
Jun 19 02:59:04 debian systemd[1]: Failed to start vboxadd.service.
░░ Subject: A start job for unit vboxadd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has finished with a failure.
░░ 
░░ The job identifier is 102 and the job result is failed.
Jun 19 02:59:04 debian systemd[1]: vboxadd.service: Consumed 1.637s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service completed and consumed the indicated resources.
-- Boot 2e61f90875af49eba0bddfcffa3051f9 --
Jun 19 07:25:14 debian systemd[1]: Starting vboxadd.service...
░░ Subject: A start job for unit vboxadd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has begun execution.
░░ 
░░ The job identifier is 104.
Jun 19 07:25:17 debian vboxadd[483]: VirtualBox Guest Additions: Starting.
Jun 19 07:25:17 debian vboxadd[607]: VirtualBox Guest Additions: Setting up modules
Jun 19 07:25:17 debian vboxadd[621]: VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
Jun 19 07:25:17 debian vboxadd[621]: modules.  This may take a while.
Jun 19 07:25:17 debian vboxadd[623]: VirtualBox Guest Additions: To build modules for other installed kernels, run
Jun 19 07:25:17 debian vboxadd[625]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
Jun 19 07:25:17 debian vboxadd[628]: VirtualBox Guest Additions: or
Jun 19 07:25:17 debian vboxadd[630]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
Jun 19 07:25:17 debian vboxadd[632]: VirtualBox Guest Additions: Kernel headers not found for target kernel
Jun 19 07:25:17 debian vboxadd[632]: 6.1.0-9-amd64. Please install them and execute
Jun 19 07:25:17 debian vboxadd[632]:   /sbin/rcvboxadd setup
Jun 19 07:25:17 debian useradd[633]: failed adding user 'vboxadd', exit code: 9
Jun 19 07:25:17 debian useradd[644]: failed adding user 'vboxadd', exit code: 9
Jun 19 07:25:18 debian vboxadd[670]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
Jun 19 07:25:18 debian vboxadd[670]: the system is restarted or 'rcvboxadd reload' triggered
Jun 19 07:25:18 debian vboxadd[483]: VirtualBox Guest Additions: reloading kernel modules and services
Jun 19 07:30:14 debian systemd[1]: vboxadd.service: start operation timed out. Terminating.
Jun 19 07:30:14 debian systemd[1]: vboxadd.service: Main process exited, code=killed, status=15/TERM
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit vboxadd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 15.
Jun 19 07:30:14 debian systemd[1]: vboxadd.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service has entered the 'failed' state with result 'timeout'.
Jun 19 07:30:14 debian systemd[1]: vboxadd.service: Unit process 1151 (systemctl) remains running after unit stopped.
Jun 19 07:30:14 debian systemd[1]: Failed to start vboxadd.service.
░░ Subject: A start job for unit vboxadd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has finished with a failure.
░░ 
░░ The job identifier is 104 and the job result is failed.
Jun 19 07:30:14 debian systemd[1]: vboxadd.service: Consumed 2.452s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service completed and consumed the indicated resources.
-- Boot e0cb4e5debdc49a4a7755b222da658b1 --
Jun 19 07:33:33 debian systemd[1]: Starting vboxadd.service...
░░ Subject: A start job for unit vboxadd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has begun execution.
░░ 
░░ The job identifier is 94.
Jun 19 07:33:34 debian vboxadd[497]: VirtualBox Guest Additions: Starting.
Jun 19 07:33:34 debian vboxadd[607]: VirtualBox Guest Additions: Setting up modules
Jun 19 07:33:34 debian vboxadd[624]: VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
Jun 19 07:33:34 debian vboxadd[624]: modules.  This may take a while.
Jun 19 07:33:34 debian vboxadd[627]: VirtualBox Guest Additions: To build modules for other installed kernels, run
Jun 19 07:33:34 debian vboxadd[630]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
Jun 19 07:33:34 debian vboxadd[634]: VirtualBox Guest Additions: or
Jun 19 07:33:34 debian vboxadd[637]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
Jun 19 07:33:34 debian vboxadd[639]: VirtualBox Guest Additions: Kernel headers not found for target kernel
Jun 19 07:33:34 debian vboxadd[639]: 6.1.0-9-amd64. Please install them and execute
Jun 19 07:33:34 debian vboxadd[639]:   /sbin/rcvboxadd setup
Jun 19 07:33:34 debian useradd[640]: failed adding user 'vboxadd', exit code: 9
Jun 19 07:33:34 debian useradd[647]: failed adding user 'vboxadd', exit code: 9
Jun 19 07:33:34 debian vboxadd[668]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
Jun 19 07:33:34 debian vboxadd[668]: the system is restarted or 'rcvboxadd reload' triggered
Jun 19 07:33:35 debian vboxadd[497]: VirtualBox Guest Additions: reloading kernel modules and services
Jun 19 07:38:33 debian systemd[1]: vboxadd.service: start operation timed out. Terminating.
Jun 19 07:38:33 debian systemd[1]: vboxadd.service: Main process exited, code=killed, status=15/TERM
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit vboxadd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 15.
Jun 19 07:38:33 debian systemd[1]: vboxadd.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service has entered the 'failed' state with result 'timeout'.
Jun 19 07:38:33 debian systemd[1]: vboxadd.service: Unit process 1099 (systemctl) remains running after unit stopped.
Jun 19 07:38:33 debian systemd[1]: Failed to start vboxadd.service.
░░ Subject: A start job for unit vboxadd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has finished with a failure.
░░ 
░░ The job identifier is 94 and the job result is failed.
Jun 19 07:38:33 debian systemd[1]: vboxadd.service: Consumed 1.678s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service completed and consumed the indicated resources.
-- Boot f19729048dd04803924bbb70a77da264 --
Jun 19 09:17:21 debian systemd[1]: Starting vboxadd.service...
░░ Subject: A start job for unit vboxadd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has begun execution.
░░ 
░░ The job identifier is 106.
Jun 19 09:17:23 debian vboxadd[513]: VirtualBox Guest Additions: Starting.
Jun 19 09:17:23 debian vboxadd[614]: VirtualBox Guest Additions: Setting up modules
Jun 19 09:17:23 debian vboxadd[623]: VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
Jun 19 09:17:23 debian vboxadd[623]: modules.  This may take a while.
Jun 19 09:17:23 debian vboxadd[625]: VirtualBox Guest Additions: To build modules for other installed kernels, run
Jun 19 09:17:23 debian vboxadd[627]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
Jun 19 09:17:23 debian vboxadd[629]: VirtualBox Guest Additions: or
Jun 19 09:17:23 debian vboxadd[633]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
Jun 19 09:17:23 debian vboxadd[636]: VirtualBox Guest Additions: Kernel headers not found for target kernel
Jun 19 09:17:23 debian vboxadd[636]: 6.1.0-9-amd64. Please install them and execute
Jun 19 09:17:23 debian vboxadd[636]:   /sbin/rcvboxadd setup
Jun 19 09:17:24 debian vboxadd[672]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
Jun 19 09:17:24 debian vboxadd[672]: the system is restarted or 'rcvboxadd reload' triggered
Jun 19 09:17:24 debian vboxadd[513]: VirtualBox Guest Additions: reloading kernel modules and services
Jun 19 09:22:22 debian systemd[1]: vboxadd.service: start operation timed out. Terminating.
Jun 19 09:22:22 debian systemd[1]: vboxadd.service: Main process exited, code=killed, status=15/TERM
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit vboxadd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 15.
Jun 19 09:22:22 debian systemd[1]: vboxadd.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service has entered the 'failed' state with result 'timeout'.
Jun 19 09:22:22 debian systemd[1]: vboxadd.service: Unit process 1161 (systemctl) remains running after unit stopped.
Jun 19 09:22:22 debian systemd[1]: Failed to start vboxadd.service.
░░ Subject: A start job for unit vboxadd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit vboxadd.service has finished with a failure.
░░ 
░░ The job identifier is 106 and the job result is failed.
Jun 19 09:22:22 debian systemd[1]: vboxadd.service: Consumed 2.777s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit vboxadd.service completed and consumed the indicated resources.
lines 290-327/327 (END)

Ich habs passende nicht gefunden, kann jemand helfen?

[JTH]

Code: Alles auswählen

Jun 17 07:49:14 debian vboxadd[4005]: VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
Jun 17 07:49:14 debian vboxadd[4005]: modules.  This may take a while.

Es wird versucht, während des Bootens das Virtualbox-Gast-Kernelmodul zu bauen. Das scheitert aber, weil die zum laufenden Kernel gehörenden Kernelheader nicht installiert sind:

Code: Alles auswählen

Jun 17 07:49:14 debian vboxadd[4015]: VirtualBox Guest Additions: Kernel headers not found for target kernel
Jun 17 07:49:14 debian vboxadd[4015]: 6.1.0-9-amd64. Please install them […]

Die musst du also, wie dort schon steht, nachinstallieren. Am einfachsten: linux-headers-amd64 installieren.

Danach führst du entweder rcvboxadd setup aus, wie dort steht, oder machst nochmal einen Reboot, der wahrscheinlich ein letztes Mal noch etwas länger dauert.

[Kruedelzuur]

Wie instaliert man bei bookworm die Kernel Header
?

[MSfree]

Code: Alles auswählen

apt-get install linux-headers-amd64

als root ausführen.

[Kruedelzuur]

@MSfree
Ich danke dir.

[thunder11]

Zu spät

Ich vermute mal, das du die Guest-Additions garnicht oder falsch installiert hast.
unter /opt (im Gast) gibt es /opt/VBoxGuestAdditions-7.0.8/uninstall.sh
führe das mal als root aus:

Code: Alles auswählen

sh /opt/VBoxGuestAdditions-7.0.8/uninstall.sh

dann installiere dkms

Code: Alles auswählen

apt install dkms

und dann nochmal die Additions installieren.
mit (Falls du nicht anderes eingebunden hast sollte der Pfad sogar stimmen.)

Code: Alles auswählen

sh /media/cdrom0/VBoxLinuxAdditions.run

Bis du im Host (falls Linux) in der Gruppe vboxusers ?

[Kruedelzuur]

Code: Alles auswählen

apt install dkms

Hat erstmal geholfen und nach einem Reboot war ich ohne Startjob.
Danke @thunder11

[thunder11]

Hat erstmal geholfen und nach einem Reboot war ich ohne Startjob.

An sich ist dkms im Guest nicht mehr notwendig (im Host schon),
da die Guest-Additions dort anders installiert werden.

Aber : dkms ist kürzer als linux-headers-amd64, und zieht alles Benötigte durch Abhängigkeiten mit.
Deshalb bleibe ich bei dieser alten (bequemen) Gewohnheit.

Edit:

Wahrscheinlich weißt du das ja.
Aber im Gast muss man der Gruppe vboxsf beitreten.