Richard W.M. Jones wrote: > >> 2) Should SetMaxMem be able to be called on a running guest? This code >> allows it, since maxmem is basically a metavalue that doesn't directly >> affect a guest. >> >> 3) Should maxmem be able to be set lower than the currently allocated mem? >> This code does not allow this. If this changed, would also need to take >> into account how we would handle this if we can change the maxmem while >> the guest is running. After rethinking, we probably should be able to >> do this, but I haven't changed the code. > > As far as I understand what maxmem means (for Xen), this seems to be > correct behaviour. > > Rich. > I just checked this: xm seems to explicitly reject setting maxmem lower than current mem for a guest in any state, but going through virsh you can set maxmem to any value on an inactive guest. But it is probably better to just stick with the xm convention. - Cole -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list