Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, August 9, 2011 3:32 AM
any idea what is wrong if anything?
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 8/7/2011 11:39:51 PM
Event ID: 18560
Task Category: None
Level: Critical
Keywords:
User: NETWORK SERVICE
Computer: rocky
Description:
'Suse VM3 Prod' 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 6C3CFD6B-965D-4C56-B3AB-7BEBB6C9CFD4)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
<EventID>18560</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2011-08-08T04:39:51.569790700Z" />
<EventRecordID>2610</EventRecordID>
<Correlation />
<Execution ProcessID="6172" ThreadID="5500" />
<Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
<Computer>rocky</Computer>
<Security UserID="S-1-5-20" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>Suse VM3 Prod</VmName>
<VmId>6C3CFD6B-965D-4C56-B3AB-7BEBB6C9CFD4</VmId>
</VmlEventLog>
</UserData>
</Event>
All replies (8)
Tuesday, August 9, 2011 5:57 AM âś…Answered
Hi,
This error might happen if :
* a power saving setting in bios is enabled
* at least one cpu hardware problem
you may refer to following post :
hope it helps.
MCTS, 2008R2 Server Virtualization http://erkanaksoy.net
Tuesday, February 19, 2019 10:33 AM | 1 vote
YEARS later, Server 2019 (not that it is ready OS for Production)
Same happens.
Deleted VM, re-created, works fine
So there is something odd about it (it was in fact VM that was "taken" over from Hyper-V after server upgrade to 2019)
Thursday, March 7, 2019 1:30 PM
Try changing the MAC address of the machine and booting it. If you have a Dynamic MAC assigned, set it to static and change it. You can change it back if needed. I came across this in Server2019 (different OS) than the original post. But this could help you.
Source:
http://www.checkyourlogs.net/?p=59953
Server 2016 and 2019 are similar enough that this could be the fix for you. Heck MS has a history of reintroducing bugs. Don't try replicating MS Office files using DFS-R in server 16/19 either... You'll lose data. That was a bug that has existing since Windows Server 2003 R2 and they've reintroduced it in every version of server OS since then.
Windows<g class="gr_ gr_21 gr-alert gr_gramm gr_inline_cards gr_run_anim Punctuation multiReplace" data-gr-id="21" id="21">....</g> It's a special OS...
Thursday, March 7, 2019 1:31 PM | 1 vote
Try changing the MAC address of the machine and booting it. If you have a Dynamic MAC assigned, set it to static and change it. You can change it back if needed. I came across this in Server2019 But it is an acknowledged bug in 2019.
Source:
http://www.checkyourlogs.net/?p=59953
Heck MS has a history of reintroducing bugs. Don't try replicating MS Office files using DFS-R in server 16/19 either... You'll lose data. That was a bug that has existing since Windows Server 2003 R2 and they've reintroduced it in every version of server OS since then.
Windows<g class="gr_ gr_21 gr-alert gr_gramm gr_inline_cards gr_run_anim Punctuation multiReplace" data-gr-id="21" id="21">....</g> It's a special OS...
Thursday, March 14, 2019 7:28 PM
Absolutely, that is the "workaround" due to the now known bug.
Why did I not think about it in first place? Maybe because I still had some faith left in Microsoft. But not any more. They do make half a**ed solutions in just about every product they release
Tuesday, April 2, 2019 5:26 AM
Worked for me! Thanks. :)
Monday, February 24, 2020 9:48 PM
When I do read this blog post - I just have 1 question : https://american-boffin.com/2019/01/17/virtual-machines-do-not-boot-after-moving-from-windows-server-2012-r2-to-windows-server-2019/
Have anybody tried to note down the STATIC MAC, before change to Dynamic, and then boot up - shutdown, and change back to STATIC MAC as origin?
I know we have alot of customers which have assigned a STATIC MAC for license purpose - this will cause them alot of pain, that I would love to avoid. :(
Wednesday, March 11, 2020 9:34 AM
Microsoft?
Anybody?
I dont have installed this : KB4497934 - since I installed the Server 2019 later, I only has this installed KB4532691.
Can I apply KB4497934, or is it superseeded - and does it even work as Ben states here : https://american-boffin.com/2019/01/17/virtual-machines-do-not-boot-after-moving-from-windows-server-2012-r2-to-windows-server-2019/
Thank you so much!