virtual machine freezing up

%3CLINGO-SUB%20id%3D%22lingo-sub-2055193%22%20slang%3D%22en-US%22%3Evirtual%20machine%20freezing%20up%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2055193%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EWe%20have%202%20terminal%20servers%20with%20Windows%20Server%202019%20and%20randomly%20these%20vm's%20would%20freeze%20totally%20like%20you%20can't%20even%20send%20Control%20%2B%20Alt%20%2B%20Delete%20signals%20to%20login.%20So%20we%20had%20to%20use%20'Turn%20off'%20the%20vm%20and%20Start%20it%20back%20on.%20Upon%20checking%20logs%20I%20don't%20see%20any%20critical%20or%20errors%20from%20the%20time%20that%20it%20stops%2Ffreeze.%20There%20are%20errors%20which%20I%20believe%20were%20generated%20after%20the%20timestamp%20because%20some%20services%20are%20going%20to%20a%20stopped%20state%20but%20I%20don't%20see%20any%20errors%20from%20the%20time%20it%20stopped.%20I%20checked%20some%20Hyper-V%20logs%20on%20the%20vm%20and%20the%20only%20thing%20I%20see%20which%20relates%20to%20the%20time%20that%20the%20problem%20starts%20is%20the%20Hyper-V-Guest-Drivers%20which%20I%20attached%20on%20this%20discussion.%20This%20terminal%20server%20has%20Sage%20and%20Office%20365%20apps.%20Is%20there%20a%20monitoring%20or%20not%20sure%20where%20to%20start%20troubleshooting%20for%20this%20vm.%20There%20are%20other%20vm's%20on%20the%20host%20that%20are%20working%20fine%2C%20so%20not%20a%20storage%20thing%20or%20host%20thing%2C%20that%20is%20why%20troubleshooting%20is%20isolated%20to%20this%20vm.%20Same%20goes%20with%20the%20other%20vm%20where%20it's%20located%20on%20a%20different%20host%20and%20other%20vm's%20on%20the%202nd%20host%20are%20all%20working%20fine%20except%20for%20thie%20terminal%20server%20vm.%20I%20did%20dism%20which%20I%20believe%20is%20kinda%20like%20the%20last%20option%20to%20if%20there%20are%20OS%20issues%20but%20ended%20up%20with%20an%20error%20and%20failed%20the%20dism.%20I%20checked%20the%20host%20for%20logs%20and%20seen%20nothing%20for%20errors%20on%20this%20vm.%20Appreciate%20any%20inputs.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ETECH-JEFF%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2055193%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

Hi,

We have 2 terminal servers with Windows Server 2019 and randomly these vm's would freeze totally like you can't even send Control + Alt + Delete signals to login. So we had to use 'Turn off' the vm and Start it back on. Upon checking logs I don't see any critical or errors from the time that it stops/freeze. There are errors which I believe were generated after the timestamp because some services are going to a stopped state but I don't see any errors from the time it stopped. I checked some Hyper-V logs on the vm and the only thing I see which relates to the time that the problem starts is the Hyper-V-Guest-Drivers which I attached on this discussion. This terminal server has Sage and Office 365 apps. Is there a monitoring or not sure where to start troubleshooting for this vm. There are other vm's on the host that are working fine, so not a storage thing or host thing, that is why troubleshooting is isolated to this vm. Same goes with the other vm where it's located on a different host and other vm's on the 2nd host are all working fine except for thie terminal server vm. I did dism which I believe is kinda like the last option to if there are OS issues but ended up with an error and failed the dism. I checked the host for logs and seen nothing for errors on this vm. Appreciate any inputs. 

 

Thanks

TECH-JEFF

 

0 Replies