For some reason, my Win7 Guest machines are not starting anymore with VirtualBox 6.1.32
My host is a Linux Mint 20.3.
I have a black screen when I try to run the Win7, this VM simply does not start.
I have also another 3 Win7 VM and the same behavior occurs.
Can someone help me?
Win7 guest does not run anymore in VB 6.1.32
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Win7 guest does not run anymore in VB 6.1.32
Please pick one VM and provide a VM log file. 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.
-
- Posts: 5
- Joined: 19. Nov 2015, 01:23
Re: Win7 guest does not run anymore in VB 6.1.32
Here it is.
- Attachments
-
- Win7-2022-04-12-12-45-57.log.zip
- (24 KiB) Downloaded 8 times
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Win7 guest does not run anymore in VB 6.1.32
Hmm. The VM doesn't seem to get any further than starting the VM - it basically just dies, it doesn't even attempt to boot. But the VDI header must be ok, otherwise VirtualBox would complain.
The fact that the same thing is seen with three other Win7 VMs implies that the problem is not caused by a corrupted VDI file... provided that the three VMs are independant, and not all recent copies of an original corrupted file. To that end I'd be more comfortable if you said that a different OS entirely still exhibited the same problem.
I do notice that you are not actually using VirtualBox, you are using a third party build instead:
And make sure you don't have any other VM platforms running at the same time (e.g. KVM).
The fact that the same thing is seen with three other Win7 VMs implies that the problem is not caused by a corrupted VDI file... provided that the three VMs are independant, and not all recent copies of an original corrupted file. To that end I'd be more comfortable if you said that a different OS entirely still exhibited the same problem.
I do notice that you are not actually using VirtualBox, you are using a third party build instead:
So I suggest that you purge the distro build, install the official version from this site, then increase vCPUs to 2 and graphics RAM to 128KB, then let's see where that gets us.00:00:00.793383 VirtualBox VM 6.1.32_Ubuntu r149290 linux.amd64 (Feb 8 2022 12:20:46) release log
And make sure you don't have any other VM platforms running at the same time (e.g. KVM).
-
- Volunteer
- Posts: 5668
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Win7 guest does not run anymore in VB 6.1.32
This!mpack wrote:And make sure you don't have any other VM platforms running at the same time (e.g. KVM).