search for: getdomainmemory

Hi Ewan, I''m almost ready to integrate some PPC-specific stuff into xend, and I was wondering if you had a plan for how that should work. First example: the device tree data structure we talked about a few weeks ago. We will need to pass the config data to PPC code, probably in XendDomainInfo.initDomain(), and then pass the resulting data structure into libxc''s xc_linux_load()

...e to >>> missing balloon support on xen/ia64 as you said, both domU and >domVTI >>> failed due to this change. >> >> The first patch that you work around seems okay to me. That is, it >> seems correct that we make initial reservation exclude >> ''getDomainMemory headroom''. Shouldn''t ia64 reserve extra memory >as it >> needs it, as x86 does, rather than up front? >> >> The second bit of your workaround, which applies to >getDomainMemory: >> I''ll wait and see if Charles has anything to say, but otherw...

I''ve put together two patches. The first introduces a new dom0_op, set_max_vcpus, which with an associated variable and a check in the VCPUOP handler fixes [1]bug 288. Also included is a new VCPUOP, VCPUOP_create, which handles all of the vcpu creation tasks and leaves initialization and unpausing to VCPUOP_initialize. The separation allows for build-time allocation of vcpus which