Lemonde
  • Lemonde
  • 100% (Exalted)
  • Advanced Member Topic Starter
6 years ago
Is this a problem with incompatibility with the Hyper-V platform for CentOS 7?
This is on a 2016 box:

Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 15/08/2018 08:57:44
Event ID: 18560
Task Category: None
Level: Critical
Keywords:
User: NT VIRTUAL MACHINE\ID
Computer: VMHOSTNAME.domain.suffix
Description:
'VMNAME' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID )
Event Xml:



18560
0
1
0
0
0x8000000000000000

1500574


Microsoft-Windows-Hyper-V-Worker-Admin
VMHOSTNAME.domain.suffix




VMNAME


0x13
0x10000
0x106e192fd63
0xffffffffbcc538b7
0xffff994380bffd70
0xffff994380bffdc0
0x0
0xffffffffbd408978
0x1
0x1
0xffffffffbd941e20
0xffff994380bfface
0x0
0xfffffffe
0xcf9
0x1
0xffffffffbcc538c5
0x10046
7F030000000000000000000000000000
0000000000000000C09F0000FFFF0000
0x8005003b
0x7f90c19ef1a0
0xba730000
0x6f0
0x0
0x0
0x0
0x0
0x0
0x0
0xffff0ff0
0x400
0000000000000000FFFFFFFF00000000
0000000000000000FFFFFFFF10009BA0
0000000000000000FFFFFFFF180093C0
0000000000000000FFFFFFFF00000000
405825C2907F0000FFFFFFFF00000000
000060824399FFFFFFFFFFFF00000000
0000000000000000FFFFFFFF00000000
004060824399FFFF8720000040008B00
00000000000000000000000000000000
0000000000007F0000C060824399FFFF
0x106e1973c21
0xfee00900
0x10
0xffffffffbd323450
0x0



Sponsor

Want to thank us? Use: Patreon or PayPal or Bitcoins: bc1q4whppe29dw77rm4kv4pln0gqae4yjnxly0dny0hky6yhnafukzjsyrsqhk

All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.


Lemonde
  • Lemonde
  • 100% (Exalted)
  • Advanced Member Topic Starter
6 years ago
Which host version are you using?

The version we are running on 2016 runs very well for our Wordpress set-up but we are yet to try 2019.
2012 R2 did report errors in the event log but still ran just fine.