Logging is just another area where Hyper-V and FailOver Clustering need drastic improvement. Download game untuk ps2. I have a HV virtual machine that fell off the network for 35 minutes, after moving from one clustered HV host to another. ![]() Yet no logs on the guest or the cluster nodes give any indication of ANY problem or any reason for the move. It's only from a 3rd party application log on the VM that I have ascertained when exactly network connectivity of the VM was lost – and of course the fact that our Network Operations Center alerted us to the fact the VM was down (actually merely unreachable) and we could not RDP to the VM and then after about 40 minutes we could. Hey Ben, I know I’m currently bumping a topic from 2009, But in Hyper-V 2016 I noticed how the ‘folder’ structure changed in terms of the events collected from the hosts. I wondered if you can make a simillar post for 2016 or atleast help me with some guidance about the following subject: 1. The question I posted here about logs that exist in 2012 but not in 2016: 2.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |