Today I installed VirtualBox-6.1.12-139181-Win and the relative Guest Addon. I did it for all my Virtual Machines, that are all Window 7 based.
After that, all machine crash at startup. I can not use any machine.
I attached one log file.
Please help me.
VB 6.1.12 All machine crash
VB 6.1.12 All machine crash
- Attachments
-
- W764TIA15-2020-07-22-12-44-14.zip
- (31.93 KiB) Downloaded 8 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: VB 6.1.12 All machine crash
I see "guest heartbeat" pauses in the log and a guest reset & reboot, but no Virtualbox problems or crashes.
Did the guest's Virtualbox window stay open and you had automatic guest OS reboots or BSODs? If so, these need to be troubleshot inside the guest OS using Microsoft's methods.
One other thing:
Did the guest's Virtualbox window stay open and you had automatic guest OS reboots or BSODs? If so, these need to be troubleshot inside the guest OS using Microsoft's methods.
Was this a real PC you tried to clone and bring into a Virtualbox guest?00:00:02.311269 File system of 'D:\01_VM\VIRTUALBOX\Win7_Tia15\Clone di SIEMENS.vdi' is ntfs
One other thing:
All your host cores are set to be available for the guest. This can starve the host if all guest cores go to 100%. Reduce guest cores to 2.00:00:02.499193 NumCPUs {in the guest} = 0x0000000000000004 (4)
00:00:03.013572 CPUM: Physical host cores: 4
Re: VB 6.1.12 All machine crash
Thank you for the reply.
"Was this a real PC you tried to clone and bring into a Virtualbox guest?"
I start use these virtual machines more than 5 year ago: I never had problems.The problems happens just yesterday after installing the last VB version and guest additions.
"Did the guest's Virtualbox window stay open and you had automatic guest OS reboots or BSODs"
The machines automatic guest OS reboot and the loop never ending. What means BSOD?
Thank you for the support
"Was this a real PC you tried to clone and bring into a Virtualbox guest?"
I start use these virtual machines more than 5 year ago: I never had problems.The problems happens just yesterday after installing the last VB version and guest additions.
"Did the guest's Virtualbox window stay open and you had automatic guest OS reboots or BSODs"
The machines automatic guest OS reboot and the loop never ending. What means BSOD?
Thank you for the support
Re: VB 6.1.12 All machine crash
Dear All,
may be I found the problem.
If I set on the monitor/Graphic Card/"VBoxVGA", I have automatic guest OS reboot in a never endig loop.
If I set on the monitor/Graphic Card/"VBoxSVGA", everything is OK!
I also reduce the cores from 4 to 2.
Thank you for the support!
may be I found the problem.
If I set on the monitor/Graphic Card/"VBoxVGA", I have automatic guest OS reboot in a never endig loop.
If I set on the monitor/Graphic Card/"VBoxSVGA", everything is OK!
I also reduce the cores from 4 to 2.
Thank you for the support!
Re: VB 6.1.12 All machine crash
It didn't work for me.Mirko73 wrote:Dear All,
may be I found the problem.
If I set on the monitor/Graphic Card/"VBoxVGA", I have automatic guest OS reboot in a never endig loop.
If I set on the monitor/Graphic Card/"VBoxSVGA", everything is OK!
I also reduce the cores from 4 to 2.
Thank you for the support!
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: VB 6.1.12 All machine crash
Though this does not technically answer my question on whether this guest was a P2V from a real computer (age doesn't answer to source), it does say these are old guests that were working for a long time.Mirko73 wrote:I start use these virtual machines more than 5 year ago: I never had problems.The problems happens just yesterday after installing the last VB version and guest additions.scottgus1 wrote:"Was this a real PC you tried to clone and bring into a Virtualbox guest?"
Web-searching can answer this one.Mirko73 wrote:What means BSOD?
This means the guest OS is having problems with something new in the OS, likely the new Guest Additions, which provide drivers for the virtual video card presented by Virtualbox, among other things. That switching from VboxVGA to VboxSVGA stopped the automatic reboots implies that the new GAs were causing a BSOD, and the OS is set to automatically reboot on BSODs. Apparently you changed the new hardware to match the drivers. I am not certain why the old VboxVGA no longer worked, though. VboxVGA is supposed to keep working in 6.1.x as long as 3D acceleration is not used. Did you enable the extra 3D support when you installed the Guest Additions this time?Mirko73 wrote:The machines automatic guest OS reboot and the loop never ending.