virtualbox.org

Virtual box 6.1.34 150636 does not setup any virtual machine under Windows 11 OS-
Windows 10 x64 21H2
Windows 11 x64
Ubuntu 22.04
all of these machines are not loaded from iso images, each setup stucks if tried to load the guest OS, guest OS setups work very slow.
HyperV turned off.
Notebook configuration - i7-11800H, 16RAM.
Logs are attached.

What does "does not setup" mean? I don't know of any circumstances in which a properly installed VirtualBox will refuse to create any VMs.

But do read HMR3Init: Attempting fall back to NEM (Hyper-V is active).

I believe that you can in fact set up VMs, they just run slowly, maybe crash. In which case a VM log will be available and should be provided. Choose one VM, make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

That is news to me. I have Windows 10 and Windows 11 vms set up and running on my Windows 11 Host.

VmWare 16.2.3 works without problems. As I understand, the problem is in the HyperV support, but I've tried to remove HyperV from the system from Programs and features, using bcedit with reboot, using all other types of settings. I have a sequre boot that uses a HyperV platform also, but it is impossbile to disable the sequre boot due to compatibility with Win 11 platform. Please make the VB compatible with the new Windows 11 OS like the VmWare.

mpack wrote:What does "does not setup" mean? I don't know of any circumstances in which a properly installed VirtualBox will refuse to create any VMs.

I believe that you can in fact set up VMs, they just run slowly, maybe crash. In which case a VM log will be available and should be provided. Choose one VM, make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

It creates VMs, but after loading, each VM is not set up the Windows/Ubuntu at all.
What is "manager UI"?

Inqizitor wrote:What is "manager UI"?

This is the main Virtualbox window, where you can see the list of VMs. Bill has a screenshot of it above.

I dont have an old VB, but I have the same symptoms on my PC with 6.1.34 VB, Tiger Lake CPU 11800H, Windows 11 x64, may be hyper v enabled (I don't know cause all checkboxes about hyperv and virtualizations are off in Programs and Features windows components) - all variants of the interfaces including hyper-v are working slow or not work at all. Please make VB working again.

AndyCot wrote:VB Version Boot Time (MM:SS)
6.1.30 1:05
6.1.32 3:13
6.1.34 3:01
6.1.35 r150972 0:52

So 6.1.35 r150972 is good.

Please share the 6.1.35 r150972 VB here to download and check it with my configuration.

Inqizitor wrote:Please share the 6.1.35 r150972 VB here to download and check it with my configuration.

Please use the current test build. Note the "(or newer)" in viewtopic.php?f=6&t=105816#p517874.

fth0 wrote:

Inqizitor wrote:Please share the 6.1.35 r150972 VB here to download and check it with my configuration.

Please use the current test build. Note the "(or newer)" in viewtopic.php?f=6&t=105816#p517874.

Thank you.
After trying to start the VM with the HyperV interface the VM crashed. (6.1.35 r151573)
The VM session was aborted.
Result Code:
E_FAIL (0x80004005)
Component:
SessionMachine
Interface:
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

EventData
Caption VirtualBoxVM.exe - Application Error
Message The instruction at 0x00007FF9DE79A9E4 accessed memory at 0x0000000000000000. The memory cannot be read. "OK" -- shutting down the application "Cancel" -- debugging the application
Logs are attacvhed.

Please reproduce the issue and provide a (zipped) VBox.log file of the complete VM run (after closing the error dialog).

Inqizitor, I have combined your posts on your issue in this one topic. Spreading your issue around will dilute the help, confuse others, and runs south of the forum rules. Please continue your discussion here.

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.