Hyper-V 2022 - VMSS logs constantly about Hyper-V-VmSwitch

%3CLINGO-SUB%20id%3D%22lingo-sub-3300377%22%20slang%3D%22en-US%22%3EHyper-V%202022%20-%20VMSS%20logs%20constantly%20about%20Hyper-V-VmSwitch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3300377%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20guys%2C%3C%2FP%3E%3CP%3Eany%20hyper-v%20gurus%20around%3F%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2F%40B71AFCCE02F5853FE57A20BD4B04EADD%2Fimages%2Femoticons%2Fcool_40x40.gif%22%20alt%3D%22%3Acool%3A%22%20title%3D%22%3Acool%3A%22%20%2F%3E%20I%20have%20a%20new%202022%20host%20which%20will%20be%20deployed%20to%20production%20soon.%20I've%20found%20by%20luck%20that%20vmms%20process%20(Virtual%20Machine%20Management%20service)%20constantly%20logs%20Verbose%20messages%20about%26nbsp%3B%22Ioctl%20Begin%20ioctlCode%3A%200xD15%22%20and%20%22%26nbsp%3BIoctl%20End%26nbsp%3BioctlCode%3A%200xD15%2C%26nbsp%3Bdelta%20(100%20ns)%3A%2080%2C%26nbsp%3BntStatus%3A%26nbsp%3B%200x80000005(NT%3DBuffer%20Overflow)%22%20with%20%3CSTRONG%3EEvent%20ID%200%3C%2FSTRONG%3E%20and%20source%20%3CSTRONG%3EHyper-V-VmSwitch%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22vmms01.png%22%20style%3D%22width%3A%20567px%3B%22%3E%3Cspan%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22vmms01.png%22%20style%3D%22width%3A%20567px%3B%22%3E%3Cimg%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F368426i1A01AD272D872B90%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22vmms01.png%22%20alt%3D%22vmms01.png%22%20%2F%3E%3C%2Fspan%3E%3C%2FSPAN%3EI've%20looked%20around%20and%20had%20no%20luck%20finding%20the%20cause.%20It's%20happening%20even%20if%20I%20stop%20all%20the%20VMs%20and%20I%20even%20removed%20the%20vSwitch%20-%20there%20is%20no%20vSwitch%20on%20the%20host%20and%20it%20still%20logs%20like%20hell.%20The%20source%20is%20well%20know%20%3CSTRONG%3ESID%201-5-18%3C%2FSTRONG%3E%20(SECURITY_LOCAL_SYSTEM_RID)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20saw%20this%20before%20or%20have%20any%20idea%20what%20could%20be%20the%20issue%20here%3F%3C%2FP%3E%3CP%3EThanks%20for%20any%20ideas%3C%2FP%3E%3CP%3EMartin%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3300377%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Evmms%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Evmswitch%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi guys,

any hyper-v gurus around? :cool: I have a new 2022 host which will be deployed to production soon. I've found by luck that vmms process (Virtual Machine Management service) constantly logs Verbose messages about "Ioctl Begin ioctlCode: 0xD15" and " Ioctl End ioctlCode: 0xD15, delta (100 ns): 80, ntStatus:  0x80000005(NT=Buffer Overflow)" with Event ID 0 and source Hyper-V-VmSwitch.

vmms01.pngI've looked around and had no luck finding the cause. It's happening even if I stop all the VMs and I even removed the vSwitch - there is no vSwitch on the host and it still logs like hell. The source is well know SID 1-5-18 (SECURITY_LOCAL_SYSTEM_RID)

 

Anyone saw this before or have any idea what could be the issue here?

Thanks for any ideas

Martin

 

0 Replies