Event 18560 in Hyper-V-Worker with CentOS 6.2 guest on Hyper-V cluster RRS feed

  • Question

  • Hi

    After installing CentOS 6.2 with linux IS 3.2 everything seemed to work great, however whenever rebooting the VM a critical event is logged by Hyper-V-Worker

    "Server was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault..." event id 18560

    Even though it does not represent a problem now I'm uncertain about taking the server into production.

    Does anyone have experience with this issue or know why it happens



    • Moved by BrianEhMVP Wednesday, February 22, 2012 9:46 PM (From:Hyper-V)
    Wednesday, February 22, 2012 9:15 PM

All replies

  • Hi,

    I found these links which talk about your issue,they said that you should contact Product Support:
    18560 Source: Hyper-V-Worker
    Hyper-V “triple fault” Event ID 18560 [resolved]
    Event ID 18560 — Virtual Machine Miscellaneous Operations

    Microsoft Certified Technology Specialist: Windows Server 2008 R2,Server Virtualizaton

    Wednesday, February 22, 2012 9:29 PM
  • Does the error message correlate to when the virtual machine was shut down through the UI?

    This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, February 23, 2012 5:13 AM
  • Mike: No. A regular reboot initiated inside the guest generates the error. There is not logged any error when using the UI shutdown.

    I'v also noticed that the guest's network seem to "go to sleep" after being idle for a while. After some time of inactivity there is high packet loss and timeouts when initiating a new session. I don't know if this is related or a separate issue.


    Friday, February 24, 2012 9:59 AM
  • So the triple fault message on a Linux guest reboot is expected - it's how the Linux kernel reboots.

    The network issue is not expected. Can you share more details?

    This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, February 27, 2012 6:39 PM
  • Some more info on the network issue:

    It seems to be a arp related. I haven't done any real digging but the problem has disappeared after adding a static mac entry on the cluster's switch. Even though this works I don't consider it a permanent solution. If anybody has any ideas I would be grateful.

    Note that this is only a problem with my linux VMs.

    Thanks Lars

    Friday, March 2, 2012 10:18 AM
  • Can you try the updated 3.3-pre drivers available here and see if the problem still exists?


    This posting is provided "AS IS" with no warranties, and confers no rights.

    Sunday, March 11, 2012 10:05 PM