search for: auto_max

...we currently do in oVirt with the Memory Overcommitment Manager [2]. This allows customers to expect a certain minimum amount of performance. In order to support both modes of operation (at the same time) how about supporting two virtio configuration variables in the balloon driver: auto_min and auto_max. These variables would allow the host to restrict the range in which the auto-balloon algorithm may operate. Setting both to 0 would disable auto-ballooning and require all inflate/deflate commands to come from the host. I think there are some very interesting possibilities how auto-balloon can b...

Hi all! We're debating the design of the balloon for the OASIS spec. Noone likes the current one, but there are fundamental usage pattern questions which we're fumbling with. So if you know anyone who is using it in production? If, so, how? In particular, would you be happy with guests simply giving the host back whatever memory they can spare (as Xen's self-balloon does)?

Hi all! We're debating the design of the balloon for the OASIS spec. Noone likes the current one, but there are fundamental usage pattern questions which we're fumbling with. So if you know anyone who is using it in production? If, so, how? In particular, would you be happy with guests simply giving the host back whatever memory they can spare (as Xen's self-balloon does)?

...the opposite point: that if you're charging customers by the MB of memory, it's easy to get them to balloon themselves. > In order to support both modes of operation (at the same time) how > about supporting two virtio configuration variables in the balloon > driver: auto_min and auto_max. These variables would allow the host > to restrict the range in which the auto-balloon algorithm may operate. > Setting both to 0 would disable auto-ballooning and require all > inflate/deflate commands to come from the host. I think there are > some very interesting possibilities ho...

...the opposite point: that if you're charging customers by the MB of memory, it's easy to get them to balloon themselves. > In order to support both modes of operation (at the same time) how > about supporting two virtio configuration variables in the balloon > driver: auto_min and auto_max. These variables would allow the host > to restrict the range in which the auto-balloon algorithm may operate. > Setting both to 0 would disable auto-ballooning and require all > inflate/deflate commands to come from the host. I think there are > some very interesting possibilities ho...

...would certainly shift the burden of conservation onto the guest and this could be preferred for some customers. > >> In order to support both modes of operation (at the same time) how >> about supporting two virtio configuration variables in the balloon >> driver: auto_min and auto_max. These variables would allow the host >> to restrict the range in which the auto-balloon algorithm may operate. >> Setting both to 0 would disable auto-ballooning and require all >> inflate/deflate commands to come from the host. I think there are >> some very interesting...