Hello friends. After I bought a new PC I am not able to virtualize guest Windows 7 on a computer with Xubuntu 22.04 installed. I have a .vdi backup of Windows 7 that already has all my programs installed. It opens in VirtualBox, but after about 2 minutes it crashes, and it is necessary to kill the virtualbox process. So I tried to format Windows 7 using an .iso image file, but it crashes before the screen to choose the language and partition the disk.
I tried to virtualize a Windows 10 guest and it worked normal, just like an Ubuntu guest.
I am using the following software and hardware:
OS: Xubuntu 22.04
Virtualbox: 6.1.34 (installed from repository via apt)
Dell Optiplex 7000
Processor: i5-12500T
Memory: 8GB DDR4 3200Mhz
Windows 7 frozen
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 7 frozen
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.
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.
Re: Windows 7 frozen
Hello scottgus1. The vm is fully powered off, I'm not using the save state option. Today when trying to open before the login screen already crashes the system. Attached is the log of 3 attempts to open the VM.
- Attachments
-
- Log windows 7.zip
- (62.56 KiB) Downloaded 10 times
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 7 frozen
Logs 0 and 2 are not complete.
If "kill the virtualbox process" means you're using the host command line, task manager, etc to kill VirtualboxVM.exe, or something like that, it can kill off what's necessary to finish the log and provide more diagnostic data. If the VM window is still open and the VM OS is unresponsive etc it may be only necessary to close the VM window with Power Off option chosen. Then the full log gets written.
Log 0 VM shows that the OS inside the VM had stopped working for a while "vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive." This means the VM 'hardware' was still working. I don't see why the VM OS stopped working, though.
Only two things I can see so far:
In what way does this "crash" manifest itself? Does Virtualbox on the host crash? Or is the crash something happening inside the VM OS?raulrmr wrote:after about 2 minutes it crashes, and it is necessary to kill the virtualbox process.
If "kill the virtualbox process" means you're using the host command line, task manager, etc to kill VirtualboxVM.exe, or something like that, it can kill off what's necessary to finish the log and provide more diagnostic data. If the VM window is still open and the VM OS is unresponsive etc it may be only necessary to close the VM window with Power Off option chosen. Then the full log gets written.
Log 0 VM shows that the OS inside the VM had stopped working for a while "vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive." This means the VM 'hardware' was still working. I don't see why the VM OS stopped working, though.
Only two things I can see so far:
Turn on NX/XD in the host BIOS.00:00:00.661475 NX - No-Execute/Execute-Disable = 0 (1)
In two logs the RAM was overprovisioned. I can't see if this caused trouble though.00:00:00.516940 Host RAM: 7640MB (7.4GB) total, 2104MB (2.0GB) available
00:00:00.555502 RamSize <integer> = 0x00000000bb800000 (3 145 728 000, 3 000 MB, 2.9 GB)
-
- 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: Windows 7 frozen
Windows 7-log0.log wrote:00:00:00.644639 Ext Features 00:00:00.644640 Mnemonic - Description = guest (host) 00:00:00.644648 NX - No-Execute/Execute-Disable = 0 (1)
No, you're misinterpreting things here: NX/XD is already enabled in the host BIOS, but it's not provided to the guest OS, because the VM is configured for a 32-bit Windows 7.scottgus1 wrote:Turn on NX/XD in the host BIOS.
Regarding the OP's problem, I didn't see the cause either.
Re: Windows 7 frozen
Good Morning. After several attempts I managed to solve it. I installed windows from a 64 bit iso. I've always used 32-bit Windows and never had any problems. But this computer with 12th generation intel processor did not run Windows 32 bits, only 64 bits.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 7 frozen
Yep, got my guests and hosts backwards, thanks, fth0!
Glad you got the OS running, Raul! However, I think there's still something missing in the diagnosis, though I can't put my finger on it. Doesn't seem reasonable that a modern 64-bit CPU can't run a 32-bit VM. There's an undistributed middle term in there somewhere...
Glad you got the OS running, Raul! However, I think there's still something missing in the diagnosis, though I can't put my finger on it. Doesn't seem reasonable that a modern 64-bit CPU can't run a 32-bit VM. There's an undistributed middle term in there somewhere...