This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] xm mem-set issues

On 11 May 2006, at 20:41, Puthiyaparambil, Aravindh wrote:

1. "xm mem-set <DomID> 32M" causes DomU / Dom0 to freeze irrespective of initial memory size. There is no output on the serial console when this happens so I am not sure where exactly the DomU is crashing. I know doing this is harsh but I think a check is required that will prevent users from shooting themselves in the foot.

Possibly. Perhaps a min-mem parameter in the xend config file or something like that.

2. I am able to do "xm mem-set <DomID> 8G" even if the total system memory is only 4GB. "xm list" reflects the 8GB value. Isn't this also a bug?

The bug here is that 'xm list' shows the current target allocation for the guest (as specified to mem-set) rather than what the guest is currently using. It'd be good to fix this.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>