Hi
It seems that a
restored vm lost those pages ballooned down. For migration, destination
does not have those pages which ballooned down on source.
Right, that's the correct behaviour isn't it? Pages freed on source VM do
not magically reappear on destination VM?
Yes, so this method can not fix this problem.
But if i balloon down those pages every time(not driver first load), i
tested save/restore/migration for several times, and all work fine. But
the domu will waste lots of memory in this situation.
Yes, that's weird. Do you know what condition causes guest memory allocation
failure on xc_domain_restore? Is it due to hitting the guest maxmem limit in
Xen? If so, is maxmem the same value across multiple iterations of
save/restore or migration?
Sorry, i have no idea about it. Maybe I need to print more log in
for(;;) in xc_domain_restore to see what is the difference between
without and with balooning down pages.
Thanks
Annie.
|