Starting my W10 virtual machine in VB7.0
Starting my W10 virtual machine in VB7.0
Host system: Windows 11 Home, 64-bit ver 21H2
Virtual machine: StatCrew Machine, Windows 10 32-bit
VirtualBox version: 7.0.0 r153978 (Qt5.15.2) with extension pack
I was successful in running version 6.138, but update to version 7.0.0 but the virtual machine does not start
I have no idea about how to update the Python bindings (if that is preventing the virtual machine from showing up)
Virtual machine: StatCrew Machine, Windows 10 32-bit
VirtualBox version: 7.0.0 r153978 (Qt5.15.2) with extension pack
I was successful in running version 6.138, but update to version 7.0.0 but the virtual machine does not start
I have no idea about how to update the Python bindings (if that is preventing the virtual machine from showing up)
- Attachments
-
- blackscreen.jpg (22.01 KiB) Viewed 1942 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Starting my W10 virtual machine in VB7.0
AFAIK you don't need the Python bindings unless you plan to control VMs using Python. I have no interest in Python myself, hence I always untick the VBox Python stuff in the install dialog.
Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show in Explorer" and then browse into the "Logs" subfolder. Save "VBox.log" (no other file) to a zip file. Attach the zip here.
Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show in Explorer" and then browse into the "Logs" subfolder. Save "VBox.log" (no other file) to a zip file. Attach the zip here.
Re: Starting my W10 virtual machine in VB7.0
Attached are the logs from my attempt to run my Win10 virtual machine in VB 7.0.6
When I hover over the machine in the VB Manager, I get the following:
StatCrew Machine (Snapshot 2)
Running since 11:59
Session locked (which happens when a machine is in use)
So, I have the following question:
1. How do I turn off the snapshot?
When I hover over the machine in the VB Manager, I get the following:
StatCrew Machine (Snapshot 2)
Running since 11:59
Session locked (which happens when a machine is in use)
So, I have the following question:
1. How do I turn off the snapshot?
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Starting my W10 virtual machine in VB7.0
Try that again, please, no logs were seen.grstatdoc wrote:Attached are the logs
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 in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)
Re: Starting my W10 virtual machine in VB7.0
I'll try it another time ... I was irritated enough that I deleted 7.0.6 and went back to 6.1.42
Re: Starting my W10 virtual machine in VB7.0
I encountered a similar problem yesterday when I upgraded from 6.1.42 to 7.0.6 on my W10 host (22H2, build 19045.2486). My various VMs went straight into a paused state on start up and couldn't be unpaused. The only common factor with them is that they are all encrypted by VB. However, the password prompt didn't even appear, only the V7 start up logo.grstatdoc wrote:I'll try it another time ... I was irritated enough that I deleted 7.0.6 and went back to 6.1.42
Like you, I didn't install the Python core and ended up uninstalling 7.0.6 and reinstalling 6.1.42. Everything is fine again thankfully.
-
- Volunteer
- Posts: 825
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WIN11,10, 7, Linux (various)
- Location: United Kingdom
Re: Starting my W10 virtual machine in VB7.0
I understand and empathise, but without a range of VBox.Logs which show the problem, plus corresponding device specs, the Devs will probably struggle to track down a solution as they can only directly test with a with the hardware they have available.
FWIW the only way I've so far been able to achieve a working Windows 10 VM on VirtualBox 7.0.4/6 was by disabling 3D, but that was on a Mac Host, not Windows.
FWIW the only way I've so far been able to achieve a working Windows 10 VM on VirtualBox 7.0.4/6 was by disabling 3D, but that was on a Mac Host, not Windows.
Re: Starting my W10 virtual machine in VB7.0
Luckily I located a log file from last night's boot up on 7.0.6. Unfortunately it's too big to upload in its entirety but here are the opening lines:multiOS wrote:I understand and empathise, but without a range of VBox.Logs which show the problem, plus corresponding device specs, the Devs will probably struggle to track down a solution as they can only directly test with a with the hardware they have available.
FWIW the only way I've so far been able to achieve a working Windows 10 VM on VirtualBox 7.0.4/6 was by disabling 3D, but that was on a Mac Host, not Windows.
I wasn't prompted to install a 7.0.6 extension pack. Is this is what's needed?00:00:03.950112 VirtualBox VM 7.0.6 r155176 win.amd64 (Jan 11 2023 16:38:38) release log
00:00:03.950114 Log opened 2023-01-30T22:42:33.555225800Z
00:00:03.950114 Build Type: release
00:00:03.950130 OS Product: Windows 10
00:00:03.950131 OS Release: 10.0.19045
00:00:03.950131 OS Service Pack:
00:00:03.999442 DMI Product Name: Z170X-UD3
00:00:04.002418 DMI Product Version: Default string
00:00:04.002425 Firmware type: BIOS
00:00:04.002429 Host RAM: 32723MB (31.9GB) total, 26542MB (25.9GB) available
00:00:04.002431 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:04.002431 Process ID: 5640
00:00:04.002432 Package type: WINDOWS_64BITS_GENERIC
00:00:04.003042 Installed Extension Packs:
00:00:04.003063 Oracle VM VirtualBox Extension Pack (Version: 6.1.40 r154048; VRDE Module: VBoxVRDP; Crypto Module: unusable because of 'Failed to load the main module ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxPuelMainVM.DLL'): VERR_MODULE_NOT_FOUND - GetLastError=126')
Thanks.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Starting my W10 virtual machine in VB7.0
The Extension Pack is required to handle encrypted VMs. It has been discovered that 7.0 does not throw a warning when starting an encrypted VM when the EP is not installed. I don't know what earlier Virtualbox versions did in this scenario.Kapitan_S wrote:they are all encrypted by VB. However, the password prompt didn't even appear, only the V7 start up logo.
Zipped logs fit.Kapitan_S wrote:Unfortunately it's too big to upload in its entirety
Yes, the EP is required.Kapitan_S wrote:Crypto Module: unusable because of 'Failed to load the main module ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack...
We'll need further input from OP grstatdoc to decide if their issue is also trying to start an encrypted VM with no EP. If not, we may move Kapitan_S's conversation to a new topic.
Re: Starting my W10 virtual machine in VB7.0
Hopefully this works (rar file)scottgus1 wrote: Zipped logs fit.
Last edited by Kapitan_S on 1. Feb 2023, 20:05, edited 1 time in total.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Starting my W10 virtual machine in VB7.0
Scott already told you what the problem was: no extension pack (or EP with mismatched version, amounts to the same thing).
00:00:03.950112 VirtualBox VM 7.0.6 r155176 win.amd64 (Jan 11 2023 16:38:38) release log
...
00:00:04.003063 Oracle VM VirtualBox Extension Pack (Version: 6.1.40 r154048; VRDE Module: VBoxVRDP; Crypto Module: unusable because of 'Failed to load the main module ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxPuelMainVM.DLL'): VERR_MODULE_NOT_FOUND - GetLastError=126')