Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Temporary forum to discuss issues and problems during a VirtualBox Beta or Release Candidate phase.
Post Reply
StrakersysK
Posts: 5
Joined: 22. Sep 2022, 16:28
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Windows 11, Windows 10, Ubuntu, OS X, Windows 7, Fedora 36, CentOS, SteamOS
Location: Netherlands

Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by StrakersysK »

Hi all, I'm hoping someone can help as I'm not sure where else to ask anymore.
I am trying to build test Windows 11 images, and due to the Secure Boot and TPM requirements, the 6.1.x branch will not support these features yet.
I understand that the 7.x branch has these features and so I've removed my 6.1.x and installed Virtualbox 7.0.0_BETA1.
I'm getting a `NS_ERROR_FAILURE (0X80004005)` error (full details below).

I've been using Virtualbox 6.1.38 on this dedicated Linux system without any notable issues, for using Hashicorp Packer to create build images but the issue occurs when trying to start ANY VM manually or otherwise.
Nothing else is installed on this Ubuntu system apart from Visual Studio Code, git, python and a few tools.
I removed and purged Virtualbox 6.1.38 (Installed via apt from Oracle repo) from the system and installed Virtualbox 7.0.0_BETA1 (From the .run installer on the Oracle site).
Additionally I installed the matching VirtualBox Extension Pack 7.0.0_BETA1 from the Oracle site.

Can anyone advise a way forward?

I'm running:
Ubuntu 20.04.1 LTS jammy
Virtualbox 7.0.0_BETA1 r153426

When I run any VM, I get this error:

Code: Select all

The VM session was aborted.
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
SessionMachine
Interface:
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
I also regenerated kernel modules:

Code: Select all

StrakersysK@FLIPSIDES2:~/Projects/win11_base_image$ sudo /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
I've got a ~1200 line VM log I'll try to post it below.
Edit: zipped log added here, if there are any additional useful logs please let me know.
Attachments
VirtualBox7B1_log.zip
(14.46 KiB) Downloaded 193 times
Last edited by StrakersysK on 22. Sep 2022, 17:51, edited 2 times in total.
StrakersysK
Posts: 5
Joined: 22. Sep 2022, 16:28
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Windows 11, Windows 10, Ubuntu, OS X, Windows 7, Fedora 36, CentOS, SteamOS
Location: Netherlands

Re: Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by StrakersysK »

It seems that I'm unable to post the log because it's too long, and I'm unable to post URLs because I'm new.

I've put the log on Pastebin:

pastebin
(dot)
com
(slash)
p8qCJwsz

I'm just trying to get some help, it's not spam, maybe an admin can help.
SRE/DevOps Engineer by day, tinkerer by night.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by mpack »

Logs fit when zipped.
StrakersysK
Posts: 5
Joined: 22. Sep 2022, 16:28
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Windows 11, Windows 10, Ubuntu, OS X, Windows 7, Fedora 36, CentOS, SteamOS
Location: Netherlands

Re: Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by StrakersysK »

mpack wrote:Logs fit when zipped.
Sorry, I wasn't aware. I can re-add it if desired.
Does zipping a .txt log make it viewable on the forum?

Edit: Added log to first post, thanks @mpack
SRE/DevOps Engineer by day, tinkerer by night.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by scottgus1 »

The last lines on the log were
00:00:01.262492 rtldrNativeLoad: dlopen('D3DCompiler_47.so', RTLD_NOW | RTLD_LOCAL) failed: D3DCompiler_47.so: cannot open shared object file: No such file or directory
00:00:01.262524 VMSVGA: Single DX device mode: enabled
00:00:01.263453 rtldrNativeLoad: dlopen('libvulkan.so', RTLD_NOW | RTLD_LOCAL) failed: libvulkan.so: cannot open shared object file: No such file or directory
3D acceleration is enabled, which uses the host's video. Maybe that's part of the problem?

This is the 7.0 Beta, so I'll move this to the Beta forum.
fth0
Volunteer
Posts: 5677
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by fth0 »

I've been wondering why you didn't mention that your dedicated Linux system is a QEMU/KVM VM, but the following statement seems to explain it:
StrakersysK wrote:I've been using Virtualbox 6.1.38 on this dedicated Linux system without any notable issues
Now I'm wondering why it worked with VirtualBox 6.1.38 running nested inside a QEMU/KVM VM. Or did you use QEMU without KVM so far, or even never run a VirtualBox VM?
StrakersysK
Posts: 5
Joined: 22. Sep 2022, 16:28
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Windows 11, Windows 10, Ubuntu, OS X, Windows 7, Fedora 36, CentOS, SteamOS
Location: Netherlands

Re: Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by StrakersysK »

scottgus1 wrote:The last lines on the log were
00:00:01.262492 rtldrNativeLoad: dlopen('D3DCompiler_47.so', RTLD_NOW | RTLD_LOCAL) failed: D3DCompiler_47.so: cannot open shared object file: No such file or directory
00:00:01.262524 VMSVGA: Single DX device mode: enabled
00:00:01.263453 rtldrNativeLoad: dlopen('libvulkan.so', RTLD_NOW | RTLD_LOCAL) failed: libvulkan.so: cannot open shared object file: No such file or directory
3D acceleration is enabled, which uses the host's video. Maybe that's part of the problem?

This is the 7.0 Beta, so I'll move this to the Beta forum.
Actually, yes, I managed to find that myself as well a few hours ago after trauling throught the logs bit by bit.
Disabling the Hardware Video Acceleration worked, and I've managed to get a few Windows 11 builds started with Packer.
I'm not sure why this worked with v6.1.38, but that version worked more or less flawlessly, apart from the lack of Secure Boot and TPM support.


fth0 wrote:I've been wondering why you didn't mention that your dedicated Linux system is a QEMU/KVM VM, but the following statement seems to explain it:
StrakersysK wrote:I've been using Virtualbox 6.1.38 on this dedicated Linux system without any notable issues
Now I'm wondering why it worked with VirtualBox 6.1.38 running nested inside a QEMU/KVM VM. Or did you use QEMU without KVM so far, or even never run a VirtualBox VM?
Sorry, I forgot to mention that part, basically everything I do runs in VMs so I didn't think to mention that in particular. I'm literally in VMs all day every day without a workstation, so "dedicated" in my mind is another VM that serves a single purpose. This particular VM is Packer and VirtualBox running inside a Ubuntu 20.04.1 KVM host, as you rightly noted. VirtualBox runs just fine nested inside this VM, and I run Hyper-V nested concurrently in another VM on the same host. No notable issues apart from a performance overhead hit occasionally.
As it is, I've had no issues building everything in this VM using VirtualBox v6.1.38, but 7.0.0_BETA1 was a bit painful to install, and required a complete purge of ever trace of v6.1.38 as I noted earlier. That was before I encountered the issue in this thread, which eventually I traced down to the Video Acceleration being enabled.
Everything in the VM works perfectly otherwise, so I'm not sure why v7.0.0_BETA1 had this issue, but then it is BETA, I suppose.
SRE/DevOps Engineer by day, tinkerer by night.
klaus
Oracle Corporation
Posts: 1133
Joined: 10. May 2007, 14:57

Re: Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by klaus »

The 3D code in VirtualBox 7 is all new (and has a bug expecting libvulkan.so to be present, which is only the case if you install the libvulkan-dev package - which is the workaround to get it going). Needs a fix to use libvulkan.so.1 which is in package libvulkan1 which I assume you have installed.
fth0
Volunteer
Posts: 5677
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by fth0 »

StrakersysK wrote:This particular VM is Packer and VirtualBox running inside a Ubuntu 20.04.1 KVM host, as you rightly noted. VirtualBox runs just fine nested inside this VM, and I run Hyper-V nested concurrently in another VM on the same host. No notable issues apart from a performance overhead hit occasionally.
Thank you for the information, good to know! :)

Nesting hypervisors from different manufacturers didn't work in many combinations in the past, and I wasn't aware that QEMU/KVM can host VirtualBox and Hyper-V nowadays. How long (in years) are you running such a setup?
StrakersysK
Posts: 5
Joined: 22. Sep 2022, 16:28
Primary OS: Linux other
VBox Version: OSE other
Guest OSses: Windows 11, Windows 10, Ubuntu, OS X, Windows 7, Fedora 36, CentOS, SteamOS
Location: Netherlands

Re: Virtualbox 7.0.0_BETA1 host on Ubuntu 22.04.1, Win11 guest - Error NS_ERROR_FAILURE (0x80004005)

Post by StrakersysK »

klaus wrote:The 3D code in VirtualBox 7 is all new (and has a bug expecting libvulkan.so to be present, which is only the case if you install the libvulkan-dev package - which is the workaround to get it going). Needs a fix to use libvulkan.so.1 which is in package libvulkan1 which I assume you have installed.
Oh, thanks for letting me know. I'll definitely test that and see if I can enable Acceleration. Awesome.


fth0 wrote:
StrakersysK wrote:This particular VM is Packer and VirtualBox running inside a Ubuntu 20.04.1 KVM host, as you rightly noted. VirtualBox runs just fine nested inside this VM, and I run Hyper-V nested concurrently in another VM on the same host. No notable issues apart from a performance overhead hit occasionally.
Thank you for the information, good to know! :)

Nesting hypervisors from different manufacturers didn't work in many combinations in the past, and I wasn't aware that QEMU/KVM can host VirtualBox and Hyper-V nowadays. How long (in years) are you running such a setup?
Oh yeah, if you want to know more I'd be happy to chew your ear off, most people don't really have a passion for it like me. :D :lol:
I'm running UnRAID on an AMD Ryzen setup, Unbuffered-ECC memory and a mix of NVME storage and disk archive array. My workstation is a Windows 11 VM with a paravirtualised RTX 3090 for work and play.
The hardware was quite carefully picked, but it's worked out very well and I'm super happy with it. Even play VR games at 90fps within my Windows 11 VM.
I can post the full specs if you're interested, but its essentially my dream setup I envisioned years ago. I've been operating like this 24/7 for a few of years now for work and play.

Edit: Here are the specs, this is my current functioning setup:
UnRAID1 (6.10.2 Pro) Primary: Ryzen 9 5950x, ASUS TUF GAMING X570-PLUS (WI-FI), 128GB (4x32GB) Kingston Unbuffered ECC PC4-25600 DDR4-3200, Gigabyte RTX3090 Turbo 24G, 1x980 Pro 1TB NVME (Cache+VMs), 1x970 EVO Plus 1TB NVME (VMs), 860 EVO 256GB SSD (VMs), 840 EVO 1TB SSD (VMs), 2x WD Red 8TB (Parity), 6x WD Red 8TB (Storage). Networking: 10Gbit with Mellanox ConnectX-3 Dual-port NIC, 1Gbit with onboard Realtek L8200A.
UnRAID2 (6.10.2 Pro) Backup: Ryzen 5 3600, ASUS TUF GAMING X570-PRO (WI-FI), 128GB (4x32GB) Micron Unbuffered ECC PC4-25600 DDR4-3200, EVGA GTX1080Ti FTW3 GAMING, 1x980 Pro 2TB NVME (Cache+VMs), 1x970 EVO Plus 1TB NVME (VMs), 1x840 EVO 256GB (VMs), 1x WD Red 8TB (Parity), 4x WD Blue 6TB (Storage). Networking: 10Gbit with Mellanox ConnectX-3 Dual-port NIC, 1Gbit with onboard Intel® I225-V.
SRE/DevOps Engineer by day, tinkerer by night.
Post Reply