For some strange reason, sometimes we cannot do a VMotion. While trying to resolve this strange issue, we did found a workaround: disable and enable the VMotion port. Once that's done, manual VMotion and VMotion triggered by DRS is working again. So I made a Powershell script to find the interface where VMotion is enabled, disable it and enable it again. Pretty straightforward, but I wanted to share it anyway.
Did you know: that the limit on vCPUs per core has been raised from 8 (or 11 for VDI workloads) to 20. That means you can use all the power in the latest processor technologies!
Hi Bouke, Does this work also for ...
...we did see some ballooning AND swa...
Well... - The desktops use 1,5GB of m...
Yes I know... - We do have a Windows ...
For XP. You'll see greatly reduced fi...