[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Re: [PATCH] Xen Guest Kexec
Ok, one of the more intresting issues is p2m map and ballooning, I'm not
sure yet how to address that best.
One problem are the "holes" in guest physical memory created by
ballooning. The other one is the time gap between loading and booting
the kexec kernel (and the p2m table which may change inbetween).
My first attempt to address that issue by avoiding it
(features="auto_translated_physmap" ;) resulted in this:
kernel BUG at drivers/xen/balloon/balloon.c:216!
For now I have a few questions:
* Which events can change the p2m map? I think for domU that is only
ballooning, right? For dom0 additionally the backend drivers (when
mapping foreign pages). Anything else?
* Is there some way to rebuild the p2m map from scratch using
* Is there some easy way to "compress" the memory, i.e. move all pages
to the start of (guest physical) memory?
* Are unpriviledged domains allowed to do Dom0 ops for DOM_SELF?
getdomaininfo for example? Or hypercall_init?
Gerd 'just married' Hoffmann <kraxel@xxxxxxx>
I'm the hacker formerly known as Gerd Knorr.
Xen-devel mailing list