Hello list,
I have been testing these new windows 8.1 drivers and have a strange issue for months since they were released that I cannot figure out. I've been testing to see if the new drivers are stable for our configuration and they are not for me. I've rebuilt twice now Windows 2008 R2 and 2012 R1 test VM's and they both become unresponsive after a few days of essentially idling doing nothing. I've noticed something interesting in that the servers do still respond to ping's but it's like the Windows GUI environment is crashed. When I connect to VNC console the console is crashed (e.g. blank and unresponsive). This happens repeatedly.
Host server:
CentOS 6.8 (fully updated)
xen_version : 4.6.3-4.el6
Xen is built via SolusVM slave script (http://files.soluslabs.com/install.sh)
The same production Xen server is running other Windows only guests on the previous drivers (ejbpv_Vista2008x64_1.0.1105.msi) without this issue. The Xen server has plenty of resources available.
I have installed all 5 driver packages of version 8.1 in each Windows guest. This is correct right?
Has anyone else had anything like this happen?
I'm lost as for what it could be. I have a large amount of Xen servers and Xen guests running the previous ejb drivers fine including on the same host server as these test VM's.
I appreciate any suggestions if anyone has a suspicion what might be happening.
Is there perhaps a paid support option anywhere that I can get help in troubleshooting this?
Finally, I was wondering will there ever be a point that anyone can foresee that these older drivers (ejbpv_Vista2008x64_1.0.1105.msi) no longer work? I'm stuck in a situation where I cannot use these new drivers until this problem is figured out and I have a large number of VMs depending on these older drivers.
Brandon
