search for: domain_max_vcpus

...if hvm and timer_mode is not None: xc.hvm_set_param(self.domid, HVM_PARAM_TIMER_MODE, - long(self.info["platform"].get("timer_mode"))) + long(timer_mode)) # Set maximum number of vcpus in domain xc.domain_max_vcpus(self.domid, int(self.info['VCPUs_max']))

Hi all, I am having confusion regarding the way a newly created domain is allocated vcpu. Initially during dom0 creation alloc_vcpu is called to create vcpu structs for all the available cpu''s and assigned to dom0. But its not the case for domU creation. 1. So how will dom0 relinquish/share vcpu to/with a newly created domU. Does this happen as part of the shared_info page mapping??

Here is the latest version of the patches to package the ocaml libraries. Changes since last time: * rename the packages from libxen-4.1-ocaml* to libxen-ocaml* - we wont be looking to install multiple concurrent versions of the same package, so the version doesn't need to be in the package name * Removed superfluous GENCONTROL definitions - dh_ocaml does what we need * Removed

This is an update to the patches sent out on 25th October. I expect, as before, that some of the larger patches won't get to the list so they are also available here: https://github.com/jonludlam/pkg-xen/commits/for-debian6. Changes since last mail: * I have split out the unrelated change to include 2 extra header files in libxen-dev * I have removed some instances of brace expansion

The following set of patches package up the ocaml libraries that are part of the standard xen build. The patches are also currently available at: https://github.com/jonludlam/pkg-xen/commits/for-debian There are some things to note: 1. The 5 patches imported from xen-unstable are not, and will not go into the xen-4.1-stable series. However, the patches were created at the request of the