Hmm, you should definitely have been allowed to bring it back up to 8GB, maybe some rounding issue in our code? What happens if you bring it back to 7GB?
As for Windows reporting memory, that’s normal, that kind of memory release on Windows is handled by the balloon driver, so when you go from 8GB to 6GB, you’ll see your system suddenly using 2GB of memory, that 2GB is what’s released.
@stgraber able to bring it back to 7GB without any issue.
@tomp 8GB -> 6GB -> 8GB should work fine, do we maybe have a rounding problem somewhere?
stgraber@castiana:~$ lxc launch images:ubuntu/20.04 f1 --vm -c limits.memory=8GB
Creating f1
Starting f1
stgraber@castiana:~$ lxc config set f1 limits.memory=6GB
Error: Failed updating memory limit: Failed setting memory to 6000000000 bytes (currently 6909067264 bytes) as it was taking too long
stgraber@castiana:~$ lxc config set f1 limits.memory=6GB
stgraber@castiana:~$ lxc config set f1 limits.memory=8GB
Error: Failed updating memory limit: Cannot increase memory size beyond boot time size when VM is running
stgraber@castiana:~$
I will take a look at that, I don’t recall experiencing that issue when developing the feature, but it seems likely to be a rounding issue as you say.
Yeah, I think it’s a GB vs GiB thing and how that gets rounded to bytes.
This should fix it: