Upgraded to 7.0.14 - and all my vms stopped running - All logs show same error all of the sudden.
Any assistance here would be appreciated!
Thank you,
Art
Windows 11 and 7.0.14 vms stopped working
-
- Posts: 11
- Joined: 3. May 2010, 14:36
- Primary OS: MS Windows 7
- VBox Version: OSE Debian
- Guest OSses: windows xp
Windows 11 and 7.0.14 vms stopped working
- Attachments
-
- VBox.log
- (40.36 KiB) Downloaded 42 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 11 and 7.0.14 vms stopped working
Regrettably, the actual error message is hard to determine. Was there a human-readable message shown?00:00:06.467084 VMSetError: D:\tinderboxa\win-7.0\src\VBox\VMM\VMMR3\VM.cpp(341) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,unsigned __int64,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *) noexcept,void *,int (__cdecl *)(struct UVM *,struct VM *,const struct VMMR3VTABLE *,void *) noexcept,void *,struct VM **,struct UVM **); rc=VERR_UNRESOLVED_ERROR
00:00:06.467092 VMSetError: Unresolved (unknown) host platform error.
00:00:06.468344 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={Unresolved (unknown) host platform error. (VERR_UNRESOLVED_ERROR)}, preserve=false aResultDetail=-35
If you downgrade back to what you had before, do the VMs start running again? If so, what was the older version?
-
- Posts: 11
- Joined: 3. May 2010, 14:36
- Primary OS: MS Windows 7
- VBox Version: OSE Debian
- Guest OSses: windows xp
Re: Windows 11 and 7.0.14 vms stopped working
No message. Starts up and creates window and then exits immediately. I'll try reverting back to 7.0.12
- Attachments
-
- Screenshot 2024-02-19 090151.png (58.62 KiB) Viewed 1255 times
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Windows 11 and 7.0.14 vms stopped working
The first error recorded in the VBox.log file is "Unhandled error 1455", which is ERROR_COMMITMENT_LIMIT ("The paging file is too small for this operation to complete.").
How did you configure the paging file on the host?
Does the host disk have enough free disk space left?
How did you configure the paging file on the host?
Does the host disk have enough free disk space left?
Re: Windows 11 and 7.0.14 vms stopped working
In log I see you are trying to start machine with 6GB RAM. System has 10GB of 32GB free.
00:00:05.821550 Host RAM: 32727MB (31.9GB) total, 10633MB (10.3GB) available
00:00:06.050952 RamSize <integer> = 0x0000000188900000 (6 586 105 856, 6.1 GiB)
Are you running other VMs or what is using 20GB of RAM? Can you stop it and try again if this VM starts up?
Also, you are using HyperV:
00:00:06.051489 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
Check this link, even if this may not be related to current memory issue. Running virtualbox with Hyper-V is experimental feature:
viewtopic.php?t=99390
00:00:05.821550 Host RAM: 32727MB (31.9GB) total, 10633MB (10.3GB) available
00:00:06.050952 RamSize <integer> = 0x0000000188900000 (6 586 105 856, 6.1 GiB)
Are you running other VMs or what is using 20GB of RAM? Can you stop it and try again if this VM starts up?
Also, you are using HyperV:
00:00:06.051489 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
Check this link, even if this may not be related to current memory issue. Running virtualbox with Hyper-V is experimental feature:
viewtopic.php?t=99390
-
- Posts: 11
- Joined: 3. May 2010, 14:36
- Primary OS: MS Windows 7
- VBox Version: OSE Debian
- Guest OSses: windows xp
Re: Windows 11 and 7.0.14 vms stopped working
reinstalled vb 7.0.12 and rebooted and all vm's worked fine.
upgraded to vb 7.014 a second time and rebooted and all vms' now seem to be working okay.
-with regard to paging files: was not running other vm's simultaneously - just had a lot of other things running on system too.
system has a huge amount of available HD space available.
-hypervisor - had installed it a long time ago and the uninstalled it. must be some remnants remaining on system.
all seems good at the moment - thanks for the various answers and suggestions.
upgraded to vb 7.014 a second time and rebooted and all vms' now seem to be working okay.
-with regard to paging files: was not running other vm's simultaneously - just had a lot of other things running on system too.
system has a huge amount of available HD space available.
-hypervisor - had installed it a long time ago and the uninstalled it. must be some remnants remaining on system.
all seems good at the moment - thanks for the various answers and suggestions.
Re: Windows 11 and 7.0.14 vms stopped working
It looks like there's an error related to VirtualBox. To resolve this issue, you can try the following steps:
story saver
1. Make sure you have the latest version of VirtualBox installed.
2. Check if there are any updates available for your host operating system.
3. Restart your computer and try starting the Virtual Machine again.
4. If the issue persists, try reinstalling VirtualBox.
If none of these steps work, please provide more information about your setup, such as the host operating system, VirtualBox version, and any recent changes you've made to your system.
story saver
1. Make sure you have the latest version of VirtualBox installed.
2. Check if there are any updates available for your host operating system.
3. Restart your computer and try starting the Virtual Machine again.
4. If the issue persists, try reinstalling VirtualBox.
If none of these steps work, please provide more information about your setup, such as the host operating system, VirtualBox version, and any recent changes you've made to your system.
Re: Windows 11 and 7.0.14 vms stopped working
Suggestion: Turn off Memory Integrity (Windows Security, Device Security, Core Isolation) as this enables some sort of Hyper-V hypervisor (I am not the first to notice this, but someone else helpfully pointed this out).