Refering to this as "balloon-leak" as it looks sort of like a memory-leak, but is instead memory disappearing into the balloon.
There are two things which have been happening more recently which may have exaggerated this problem. First, one of the DomUs is acting as a fileserver and that has been getting more usage recently. Second, I've been testing block-device hotplug as a mechanism to transfer data between VMs (xl block-detach from one VM, then xl block-attach to another VM). The DomUs appear absolutely uneffected by this. Even as Dom0 has gotten to a situation where `shutdown -r now` fails, the DomUs appear to be chugging away with no problems. There is plenty of free memory for creating additional VMs (perhaps too much, and that confused Xen?), so this is really puzzling that memory is being ballooned away from Dom0. At this point I plan after the next restart to double the allocation for Dom0 and see whether Dom0 is able to last more than a week. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
