weizhouapache commented on issue #4566: URL: https://github.com/apache/cloudstack/issues/4566#issuecomment-756031074
> > > thanks. can we change the title to match the problem please. Anyone looking back through commits will be misled. > > > I don't _think_ that the overhead to run a VM is the end-users problem, I _think_ that if I created a VM with 8GB RAM, I would expect to get charged for 8GB. > > > > > > Totally agree. > > by the way, there is a way to get accurate memory usage: memory ballooning. > > see https://libvirt.org/formatdomain.html#memory-balloon-device > > ``` > > <devices> > > <memballoon model='virtio'> > > <stats period='10'/> > > </memballoon> > > </devices> > > ``` > > > > > > we could add a global setting to enable/disable it. > > Personally I'm not really a fan of all the global settings we are introducing in CloudStack. The list gets longer and longer. > yep. but cloudstack is a open source project. There are some features which are used by some users but not used by other users. They might use different setting. It is the certain result if more features and improvements are added. > That said, virtio ballooning is also something which needs to be supported by the guest. Linux does this, but Windows or BSD won't always do this. @wido true. In windows, user have to install virtio driver for memory ballooning. If the driver is installed incorrectly, vm might be frozen after migration. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
