Earlier this year I wrote a blog post highlighting an issue that a coworker ran into with XenServer 6.2 Dynamic Memory Control (DMC) and NVIDIA GRID vGPU. You can find that article here: XenServer Dynamic Memory and NVIDIA GRID vGPU, Don’t Do It! Talking with a couple Citrix and NVIDIA folks including Rachel Berry, Jason Southern, and David Cottingham, I have been informed that this was fixed and validated with the XenServer 6.5 release (aka Creedence). Considering XenServer 6.5 has officially released for web today, it's safe to say DMC is now good to go, provided you're running XenServer 6.5! [...]

Updated 2015.1.13: XenServer 6.5 (aka Creedence) has been released to web and this has been resolved in this release. Click here to read my updated article for DMC and vGPU on XenServer 6.5 A couple months back I was working with a colleague of mine (Richard Hoffman on LinkedIn or Twitter) on a blue screen issue he identified on a fairly up-to-date XenServer 6.2, XenDesktop, NVIDIA GRID K1/K2 and vGPU deployment. In his case, he was experiencing crashes related to dxgmms1.sys, nvlddmkm.sys, and various other XenServer errors: xenopsd internal error: Device.Ioemu_failed("vgpu exited unexpectedly") xenopsd internal error: Failure("Couldn't lock GPU with device ID [...]