![]() At the same time, a VMware source on Twitter volunteered his assistance and quickly came up with some inside information on the issue. In my case it was greater than 30MB but I could not adjust it due to the fact that it was being managed by the View Connection Server. I did a little searching and found similar symptoms in VMware KB 1011971 which speaks to an issue that can arise when Video RAM (VRAM) is greater than 30MB for a virtual machine. The resulting error in the vSphere Client was:Ī general system error occurred: Failed to flush checkpoint data A few weeks ago while working with View 5.0 BETA in the lab, I ran into an issue where a Windows 7 virtual machine would not vMotion from one ESXi 5.0 host to another. General awareness/heads up blog post here on something I stumbled on with VMware View 5.0. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |