[Xen-devel] Re: [PATCH] [Flask] Fix to default policy to get simple VM running

["George S. Coker, II" <gscoker@xxxxxxxxxxxxxx>]

I've been looking into this issue as a result of your earlier post and I
have only been able to reproduce your error when manipulating the memory
reservations for a domU.  The sample flask policy is a basic policy that
only supports pv guests, so its not surprising that you've uncovered a
limitation of this policy.  Nonetheless, your patch should go in.

It's a little unclear how many guests you are running or what resources are
committed against the domUs.  How many domUs are you trying to supporting?
Do you only get the error with more than a few domUs?

On 10/7/08 3:03 PM, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

> This fix gets to the default Flask/XSM policy gets a simple guest VM
> (Ramdisk only, no VIF) running.
> 
> Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>
> 

-- 
George S. Coker, II <gscoker@xxxxxxxxxxxxxx>



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