billgates:
Dynamic:
Virtualising anything creates its own small set of issues, as you have just added another OS to maintain and another layer that can misbehave.
We had a client call late Wednesday advising their network drives were not accessible. It appeared the guest OS was unable to communicate with the LAN, even though we were able to communicate with the host OS on the same network card just fine. A reboot of the host server got the guest back online and we scheduled some time this weekend to work on the issue. Unfortunately the same issue happened half an hour ago and another quick reboot has got it back online once again. This is on a server that has been in place for just about a year and has behaved flawlessly until now.
Considering computers are just a giant pocket calculator, more than their fair share of witchcraft is required. Especially if you don't want to 'release the magic smoke' as one of my team amusingly chimes in with occasionally.
Virtualization does not add issues but you rather save on power, resources and physical space. Event logs is the key to your issues. From the issue you are describing it sounds like you need ot turn off.
https://community.spiceworks.com/how_to/124202-how-to-disable-vmq-with-powershell
Virtualization of a single box doesn't save any of those resources.