similar to: Users of ballooning, please come forth!

Adam Litke <alitke at redhat.com> writes: >> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: >> 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

Adam Litke <alitke at redhat.com> writes: >> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: >> 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

> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: > 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

On 20/02/14 14:53 +1030, Rusty Russell wrote: >Adam Litke <alitke at redhat.com> writes: >>> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: >>> 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

Rusty and Anthony, If I've addressed all outstanding issues, please consider this patch for inclusion. Thanks. Changes since V2: - Increase stat field size to 64 bits - Report all sizes in kb (not pages) - Drop anon_pages stat and fix endianness conversion Changes since V1: - Use a virtqueue instead of the device config space When using ballooning to manage overcommitted memory on a

Rusty and Anthony, If I've addressed all outstanding issues, please consider this patch for inclusion. Thanks. Changes since V2: - Increase stat field size to 64 bits - Report all sizes in kb (not pages) - Drop anon_pages stat and fix endianness conversion Changes since V1: - Use a virtqueue instead of the device config space When using ballooning to manage overcommitted memory on a

Changes since V3: - Do not do endian conversions as they will be done in the host - Report stats that reference a quantity of memory in bytes - Minor coding style updates Changes since V2: - Increase stat field size to 64 bits - Report all sizes in kb (not pages) - Drop anon_pages stat and fix endianness conversion Changes since V1: - Use a virtqueue instead of the device config space

Changes since V3: - Do not do endian conversions as they will be done in the host - Report stats that reference a quantity of memory in bytes - Minor coding style updates Changes since V2: - Increase stat field size to 64 bits - Report all sizes in kb (not pages) - Drop anon_pages stat and fix endianness conversion Changes since V1: - Use a virtqueue instead of the device config space

agl at linux.vnet.ibm.com wrote: > Here are the corresponding changes to the Linux virtio driver... > > virtio: Add memory statistics reporting to the balloon driver > > When using ballooning to manage overcommitted memory on a host, a system for > guests to communicate their memory usage to the host can provide information > that will minimize the impact

agl at linux.vnet.ibm.com wrote: > Here are the corresponding changes to the Linux virtio driver... > > virtio: Add memory statistics reporting to the balloon driver > > When using ballooning to manage overcommitted memory on a host, a system for > guests to communicate their memory usage to the host can provide information > that will minimize the impact

Folks, This posting is made so that others who search for infromation on how to configure Samba for username and password caching will find it. Samba does not control client-side password caching. Caching of domain logon credentials is a client-side activity. There are registry settings on the Windows 2000 Professional and Windows XP Profesional clients that control logon credential caching.

Hello, In our office we would like to do something like "memory overcommitment" or rather "dynamic allocation" for a bunch of windows domUs (server 2003 & 2008). We thought this should be a simple feature, however we did not find any fitting solution. We use Xen 4.2.1 with xl toolstack. The idea is to use ballooning to dynamically (and automatically) change physical

virtio: Add memory statistics reporting to the balloon driver (V2) Changes since V1: - Use a virtqueue instead of the device config space When using ballooning to manage overcommitted memory on a host, a system for guests to communicate their memory usage to the host can provide information that will minimize the impact of ballooning on the guests. The current method employs a daemon running

virtio: Add memory statistics reporting to the balloon driver (V2) Changes since V1: - Use a virtqueue instead of the device config space When using ballooning to manage overcommitted memory on a host, a system for guests to communicate their memory usage to the host can provide information that will minimize the impact of ballooning on the guests. The current method employs a daemon running

Hi, I would send those, but unfortunately we did not think about the journals getting deleted after a reboot. I just made the journals persistent on the servers, we are trying to trigger the error again last time we only got half way through the VM’s when removing the snapshots so we have a good chance that it comes up again. Also the libvirt logs to the journal not to libvirtd.log, i would

Hi Adam, Hi Eric, We had this issue again a few minutes ago. One machine went down exactly the same way as described, the machine had only one snapshot and it was the only snapshot that was removed, before that in the same scriptrun we deleted the snapshots of 15 other Vms, some without, some with 1 and some with several snapshots. Can i provide anything from the logs that helps ? Regards

Hi all, How can I manage automatically memory ballooning under a kvm host (C5.6 and future C6)?? For example if I define a kvm guest to boot up with 512MB of RAM and I have configured 1GB as a maximum memory for this guest, how can I allocate this memory when guest will need it?? And the opposite question, can memory balloon be deallocated?? And is it possible to do this automatically or

On 03/06/15 07:36 +0000, Soeren Malchow wrote: >Dear Adam > >First we were using a python script that was working on 4 threads and >therefore removing 4 snapshots at the time throughout the cluster, that >still caused problems. > >Now i took the snapshot removing out of the threaded part an i am just >looping through each snapshot on each VM one after another, even with

Hello, I am running a functional Xen 4.0 platform. The objective is the project I am currently running is to replace 4 VMWare ESX by 4 Xen 4.0 hypervisors. I have been able to reproduce all the core VMWare features in Xen (but better of course =D) except memory overcommitment. I know this feature has been included since Xen 3.3 but I have found almost no information about it. When I try to

I am having some trouble creating a hierarchy of virtual classes (akin to the class structure in the 'Matrix' package). I think they arise from my not understanding the best way to specify virtual subclasses of a virtual class. please see questions below code. setClass("mom") setClass("kid1", representation("mom", "VIRTUAL"))