I have reported an issue to my Hyper-V hosting provider where I see a uncommon behaviour on my Hyper-V guest even when freshly deployed.
The Hyper-V Host system is Windows 2012 (assumingly Datacenter, clustered), the guest machine is a Generation 1 Windows 2012 R2, fully patched. Dynamic RAM is configured according to the Hyper-V Server provider.
The problem I see:
In my business environment (Windows 2012 R2 Host, Windows 2012 (R2) guests, with dynamic memory configured, aswell as in my testlab (Windows 10 CTP b10240 Host, Windows 2012 R2 guest generation 2) this problem does not occour.
After I have reported this to the Server provider, it now also occours in my Testlab. So it seems that a Windows Update is responsible for the problem.
Summary:
- RAM allocation in the taskmanager in the guest machine does not reflect the usage of the guest machine
- system performance incl. Windows UI is degraded in the guest OS, like it really would suffer full RAM, start swapping etc.
- this was not an issue before some days in my testlab, but now behaves the same. (all updates applied on the host, no updates applied on the guest)
- it does not matter if the guest OS is fully patched or not, it will show the same issue at the moment.
Evidence:
Normal behaviour of RAM consumption / allocation with Hyper-V dynamic RAM enabled on the Host (testlab, fresh installed machine, no updates on guest OS). The same situation exists in our productive environment Windows 2012 R2 Host, clustered but the hosts are
not fully patched, yet.
http://imageshack.com/a/img909/5853/7ABr0Z.png (dynamic RAM enabled)
http://imageshack.com/a/img540/1921/9QDhAB.png (dynamic RAM disabled)
current behaviour of RAM consumption / allocation with Hyper-V dynamic RAM enabled on the Host (testlab, fresh installed machine, no updates on guest OS).
http://imageshack.com/a/img673/7048/K4Pgc2.png
current behaviour of RAM consumption / allocation with Hyper-V dynamic RAM enabled on the Host (Hosting provider, fresh installed machine, fully patched, incl. optional updates)
http://imageshack.com/a/img661/2030/xlBvZO.png
Because it is evident that the behaviour changed in the last few days, I hope this will raise awareness at Microsoft and hopefully help to identify the issue, moreover as this affects Hyper-V guests across plaforms.
What do you think?
cheers,
Karl
MCP Windows Server, MCSA Windows 2008 / 2012, MCITP Hyper-V SCCM