Hi folks,
With the 5.3 release vDGA is now officially supported. It is very good when it runs! :smileygrin:
I'm currently running 4 VM's, each with its own dedicated K2 GPU. The View Administrator reports 4 working desktops and I am able to log in to each desktop.
The problem is that right now I got Windows update running on each machine and after installing .NET 4.5 on friday, Microsoft got 200MB+ with patches for me.
The issue is that I'm unable to use the console in vCenter to access the VM. The machines are running fine, but they appear to be hanging during Windows boot.
The image is from the exact same machine, just two different ways of looking at it.
I guess the console is trying to access the SVGA driver output, but since the K2 is running the display, nothing is presented to the console.
Any suggestions here?
Jan-Arve
Godmorning!
Great that its working well for you, I expect a blog-post soon!
Please share what hardware you have and if you had any issues to get it running.
The frozen/black vCenter console is expected when using vDGA, since we are routing the graphics pipeline another way we will loose the console.
// Linjo
Godmorning!
Great that its working well for you, I expect a blog-post soon!
Please share what hardware you have and if you had any issues to get it running.
The frozen/black vCenter console is expected when using vDGA, since we are routing the graphics pipeline another way we will loose the console.
// Linjo
Thanks,
As you suggested, I'll be using RDP to configure the machines - or install the direct access plugin.. ![]()
Jan-Arve
