Your message dated Sun, 22 Mar 2026 07:42:24 +0100 with message-id <[email protected]> and subject line Re: all VMs refuse to start, 0x80004005 / MachineWrap / {85632c68-b5bb-4316-a900-5eb28d3413df} has caused the Debian Bug report #960124, regarding all VMs refuse to start, 0x80004005 / MachineWrap / {85632c68-b5bb-4316-a900-5eb28d3413df} to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 960124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960124 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: virtualbox Version: 6.1.6-dfsg-2 Severity: important Hi, none of my VMs is usable anymore. It was ok in last summer with the latest vanilla kernel back then, but now I am getting: The virtual machine 'liveos' has terminated unexpectedly during startup with exit code 1 (0x1). Fehlercode: NS_ERROR_FAILURE (0x80004005) Komponente: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} And this for all existing VMs in my configuration. The configuration itself looks ok, the modules are there, the modules are loaded. $ find /lib/modules/5.6.0-1-amd64 | grep vbox /lib/modules/5.6.0-1-amd64/misc/vboxnetadp.ko /lib/modules/5.6.0-1-amd64/misc/vboxdrv.ko /lib/modules/5.6.0-1-amd64/misc/vboxnetflt.ko /lib/modules/5.6.0-1-amd64/kernel/drivers/gpu/drm/vboxvideo /lib/modules/5.6.0-1-amd64/kernel/drivers/gpu/drm/vboxvideo/vboxvideo.ko /lib/modules/5.6.0-1-amd64/kernel/drivers/virt/vboxguest /lib/modules/5.6.0-1-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko /lib/modules/5.6.0-1-amd64/updates/dkms/vboxnetadp.ko /lib/modules/5.6.0-1-amd64/updates/dkms/vboxdrv.ko /lib/modules/5.6.0-1-amd64/updates/dkms/vboxnetflt.ko $ lsmod | grep vbox vboxnetadp 28672 0 vboxnetflt 32768 0 vboxdrv 528384 2 vboxnetadp,vboxnetflt Ryzen virtualization is enabled: $ grep svm /proc/cpuinfo | sort -u flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca Looking for that error, reveals: $ grep -i error VBoxSVC.log | grep -v vbox.*File.not.found 00:00:00.576586 nspr-4 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0 00:00:00.576622 nspr-4 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0 00:00:00.576640 nspr-4 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0 00:00:00.576649 nspr-4 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0 00:00:00.576658 nspr-4 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The object functionality is limited}, preserve=false aResultDetail=0 00:00:04.383412 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'liveos' has terminated unexpectedly during startup with exit code 1 (0x1)}, preserve=false aResultDetail=0 Now idea how to continue from here. Any ideas? Maybe this is a variant of https://www.virtualbox.org/ticket/19224 or https://bbs.archlinux.org/viewtopic.php?pid=1887935#p1887935 ? What "access" is required there? I am running VirtualBox as plain user and this has been working for years. Also, assuming that I need to reconfigure something, I tried this: $ dpkg-reconfigure -plow virtualbox insserv: script portmap: service portmap already provided! Job for vboxweb.service failed because the service did not take the steps required by its unit configuration. See "systemctl status vboxweb.service" and "journalctl -xe" for details. $ systemctl status vboxweb.service ● vboxweb.service - VirtualBox Web Service Loaded: loaded (/lib/systemd/system/vboxweb.service; enabled; vendor preset: enabled) Active: failed (Result: protocol) since Sat 2020-05-09 19:29:55 CEST; 1min 3s ago Process: 8721 ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start (code=exited, status=0/SUCCESS) Mai 09 19:29:55 zombie systemd[1]: Starting VirtualBox Web Service... Mai 09 19:29:55 zombie systemd[1]: vboxweb.service: Can't open PID file /run/vboxweb.pid (yet?) after start: Operation not permitted Mai 09 19:29:55 zombie systemd[1]: vboxweb.service: Failed with result 'protocol'. Mai 09 19:29:55 zombie systemd[1]: Failed to start VirtualBox Web Service. Again, something with permissions, what is this about? Best regards, Eduard. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualbox depends on: ii adduser 3.118 ii iproute2 5.6.0-1 ii libc6 2.30-4 ii libcurl3-gnutls 7.68.0-1 ii libdevmapper1.02.1 2:1.02.167-1+b1 ii libgcc-s1 10-20200502-1 ii libgl1 1.3.1-1 ii libgsoap-2.8.91 2.8.91-3 ii libopus0 1.3-1+b1 ii libpng16-16 1.6.37-2 ii libpython3.8 3.8.3~rc1-1 ii libsdl1.2debian 1.2.15+dfsg2-5 ii libssl1.1 1.1.1g-1 ii libstdc++6 10-20200502-1 ii libvncserver1 0.9.12+dfsg-9 ii libvpx6 1.8.2-1 ii libx11-6 2:1.6.9-2+b1 ii libxcursor1 1:1.2.0-2 ii libxml2 2.9.10+dfsg-5 ii libxt6 1:1.1.5-1+b3 ii procps 2:3.3.16-4 ii python3 3.8.2-3 ii python3.8 3.8.3~rc1-1 ii virtualbox-dkms [virtualbox-modules] 6.1.6-dfsg-2 ii virtualbox-modules-5.6.0-1-amd64 [virtualbox-modules] 6.1.6-dfsg-2+5.6.7-1 ii virtualbox-source 6.1.6-dfsg-2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages virtualbox recommends: ii libqt5core5a 5.12.5+dfsg-10 ii libqt5gui5 5.12.5+dfsg-10 ii libqt5opengl5 5.12.5+dfsg-10 ii libqt5widgets5 5.12.5+dfsg-10 ii libxcb1 1.14-2 ii libxext6 2:1.3.3-1+b2 ii virtualbox-qt 6.1.6-dfsg-2 Versions of packages virtualbox suggests: ii vde2 2.3.2+r586-2.2+b1 ii virtualbox-guest-additions-iso 6.1.6-1 -- no debconf information -- Nur eine Kette ist es, die uns gebunden hält: Die Liebe zum Leben. -- Lucius Annaeus Seneca (an Lucilius)
--- End Message ---
--- Begin Message ---triaging / cleaning up old bugs: I think that was an issue with the kernel modules, as this error typically shows up when the modules cannot be loaded or are incompatible. Said that, this bug has been reported 6 years ago, and I can run VMs on unstable, so I'm closing this bug as non-actionable- anymore.
--- End Message ---
