Re: [Xen-users] migrating ballooned domains

["M.A. Williamson" <maw48@xxxxxxxxx>]

> This error is due to the destination xend trying to create a domain
> of the original size, rather than allocating just the shurnk size.
> I can successfully migrate a domain created small enough to fit on the
> destination host at the domain's original size.
>
> Is this a fundamental issue, or just a bug in xend?   I'm still scarred
> from the last time I hunted through the xend python so I have not actually
> tried to run this down this myself.
It's a feature ;-)

OK, so maybe not.  IIRC, the issue was something like:

origin machine retrieves domain size from Xen, Xen reports original memory 
allocation
origin machine tries to reserve that amount of space on destination

bam

There've been mails about this in the past, with some discussion as to what 
needed doing. I'd say it should be possible to fix this at the control 
plane - I don' think it's a terribly fundamental issue, and it is one we've 
occasionally run across before.
If we support migrating ballooned domains, I guess we *might* have to 
prevent the domain from ballooning itself up whilst it's being migrated - 
otherwise it could break the migration process. This could probably be done 
by just lowering its memory limit whilst the pre-copy phase is taking 
place.
HTH

Cheers,
Mark

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users