Win10 Guests stopped working with upgrade to 5.1.

[isgdre]

I updated to V5.1.0 from V5.0.24 and my Win10 Guests stopped working. During startup it detects a hardware change and tries to fix it. there is of course no hardware change, just the VM change.

I had to roll back to V5.0.24 but will include a zip ups of a couple of VM Logs (including the definitions). If there is anything else You could use let me know.

Here is some basic systeminfo from the host windows 7 64bit computer.

Host Name:                 TWILIGHT
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Thx
Registered Organization:   
Product ID:                00426-065-1786231-86699
Original Install Date:     15/12/2009, 4:51:11 PM
System Boot Time:          11/07/2016, 11:05:55 AM
System Manufacturer:       System Manufacturer
System Model:              System Product Name
System Type:               x64-based PC
Processor(s):              2 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~1995 Mhz
                           [02]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~1995 Mhz
BIOS Version:              American Megatrends Inc. 1009, 02/03/2009
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume3
System Locale:             en-ca;English (Canada)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-06:00) Central Time (US & Canada)
Total Physical Memory:     24,575 MB
Available Physical Memory: 22,157 MB
Virtual Memory: Max Size:  49,223 MB
Virtual Memory: Available: 46,389 MB
Virtual Memory: In Use:    2,834 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    GULFSTREAM
Logon Server:              \\TWILIGHT
Hotfix(s):                 536 Hotfix(s) Installed.
                           [01]: KB2849697
                           [01]: bla bla bla lots of hot fixes;
Network Card(s):           6 NIC(s) Installed.
                           [01]: Intel(R) PRO/1000 PL Network Connection
                                 Connection Name: Local Area Connection
                                 DHCP Enabled:    Yes
                                 DHCP Server:     10.0.0.75
                                 IP address(es)
                                 [01]: 10.0.0.30
                                 [02]: fe80::74fb:2690:81de:ce4d
                           [02]: Intel(R) PRO/1000 PL Network Connection
                                 Connection Name: Local Area Connection 2
                                 Status:          Media disconnected
                           [03]: Intel(R) PRO/1000 EB Network Connection with I/O Acceleration
                                 Connection Name: Local Area Connection 3
                                 Status:          Media disconnected
                           [04]: Intel(R) PRO/1000 EB Network Connection with I/O Acceleration
                                 Connection Name: Local Area Connection 4
                                 Status:          Media disconnected
                           [05]: Microsoft Loopback Adapter
                                 Connection Name: Local Area Connection 5
                                 Status:          Hardware not present
                           [06]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.56.1
                                 [02]: fe80::ad41:e302:b3e2:8e0f

[Frank Mehnert]

What do you mean by "stopped working"? Did the VM process crash? From looking at the log files it seems that you were able to shut down the guest when running with VBox 5.1.0? Or did the guest BSOD?

[isgdre]

Sorry, I thought you may be familiar with it.

No, BSOD. It said it detected a hardware change and ended up in a screen I have never seen before. It wanted me to select form (maybe 8) things like Command Prompt, Recover Console, Restore Mode, etc... I may be getting the exact names wrong. I didn't take a screen shoot. :( Poking around for a sec showed I was in come kind of recovery drive on X:.

I had to get things going again so I restored from backup. The system (host and guess) are running so If you want me to install some test thing into the Win10 box before trying again it is possible.

[Dr. Boris Neubert]

I have experienced a seemingly identical problem.

The machine that was saved under 5.0.24 freezes a few seconds after starting on 5.1.2. The crucial line in the log is

00:00:03.893500 Console: Machine state changed to 'Running' 00:00:07.781204 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

I have to poweroff the machine.

[Dr. Boris Neubert]

Log and config from neubert's report attached.

[derMicha]

I experienced the same issue:

VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

Host: Windows 7 Ultimate Guest Windows 10

After downgrading to 5.0.26 everything is working fine again.

[Frank Mehnert]

neubert, your VM has 8 VCPUs on a system with 4 physical CPUs, in general that's a risky configuration, in particular if the guest is very busy (timing problems). Nevertheless, any change with VBox 5.1.6?

[Dr. Boris Neubert]

Frank, it works for me since 5.1.4. The Xeon CPU has 4 physical hyperthreading cores exposing 8 CPUs to the host. I want to use all of them in the guest. Is this usage scenario supported?

[isgdre]

you can close this ticket