RE: cobbler mem-max vs mem-set question
Hi Scott:
Thank you for considering it as a future modification. I am currently
working around it but I find that I have gotten so used to cobbler that
I want to put everything in it.
Regards,
Joe
-----Original Message-----
From: Scott Henson [mailto:shenson@redhat.com]
Sent: Tuesday, April 05, 2011 9:40 AM
To: Joe Linoff; cobbler mailing list
Subject: Re: cobbler mem-max vs mem-set question
On Mon, 4 Apr 2011 19:22:32 -0700, "Joe Linoff" <jlinoff(a)tabula.com>
wrote:
Hi Folks:
Cobbler is an awesome tool! Thank you.
I would like to set up my VM's with their maximum memory different
than their set memory. This is because they may migrate to a
hypervisor with more RAM at some time in the future and I would like
to avoid changing them.
On the command line I would use commands like "xm mem-set ..." and "xm
mem-max ...".
In the cobbler GUI there only appears to be one setting for virtual
memory which sets both.
How can I set both max and set memory in cobbler/koan?
If that is not possible, can you suggest a way to do it before the VM
provisioned?
Perhaps something like this would work on hypervisor assuming the
vm-0103 was defined in cobbler with 4096MB of RAM?
Dom0# koan --virt --nogfx --system vm-0103
Dom0# xm mem-set vm-0103 2048 # use half the RAM for now
Dom0# virsh start vm-0103
It all sounds possible. However, it would take a change to cobbler to
add the new field (I would actually add the max mem field) and then to
koan to make use of it.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME