> On Wed, Dec 24, 2008 at 2:32 PM, Dan Magenheimer
> <dan.magenheimer@xxxxxxxxxx> wrote:
> > Yes, its just that with your fix, Windows VM users are much more
> > likely to use memory overcommit and will need to be "trained" to
> > always configure a swap disk to ensure bad things don't happen.
> > And this swap disk had better be on a network-based medium or
> > live migration won't work.
>
> You mean they may be much more likely to under-provision memory to
> their VMs, booting with (say) 64M on the assumption that they can
> balloon it up to 512M if they want to? That seems rather unlikely to
> me... if they're not likely to start a Windows VM with 64M normally,
> why would they be more likely to start with 64M now? I'd've thought
> it would be likely to go the other way: if they normally boot a guest
> with 256M, they can now start with maxmem=1G and memory=256M, and
> balloon it up if they want.
What I mean is that now that they CAN start with memory=256M and
maxmem=1G, it is now much more likely that ballooning and memory
overcommit will be used, possibly hidden by vendors' tools.
Once ballooning is used at all, memory can not only go above
the starting memory= threshold but can also go below.
Thus, your patch will make it more likely that "memory pressure"
will be dynamically applied to Windows VMs, which means swapping
is more likely to occur, which means there had better be a
properly-sized swap disk.
For example, on a 2GB system, a reasonable configuration might be:
Windows VM1: memory=256M maxmem=1GB
Windows VM2: memory=256M maxmem=1GB
Windows VM3: memory=256M maxmem=1GB
Windows VM4: memory=256M maxmem=1GB
(dom0_mem=256M, Xen+heap=256M for the sake of argument)
Assume that VM1 and VM2 are heavily loaded and VM3 and VM4
are idle (or nearly so). So VM1 and VM2 are ballooned up
towards 1G by taking memory away from VM3 and VM4. Say
VM3 and VM4 are ballooned down to about 128M each. Now
VM3 and VM4 suddenly get loaded and need more memory.
But VM1 and VM2 are hesitant to surrender memory because
it is fully utilized. SOME VM is going to have to start
swapping!
So, I'm just saying that your patch makes this kind of
scenario more likely, so listing the need for a swap disk
in your README would be a good idea.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home