| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH][XM-TEST] Test that tries to create a 16MB domain
EM> Regarding the failure, perhaps a check or a warning would be a
EM> good idea, but I'm wary of blocking out at certain memory limits.
EM> If someone wrote a tiny OS (say the OS equivalent of Hello World)
EM> then surely it would work in less than 16MB, so why should we put
EM> such a limit?
I completely agree with you. The --force flag would be one way around
this. We could also add it to the xend configuration as an adjustable
limit. Another option might be to have the limit determined by the
builder that is used, right?
switch (type) {
case linux: limit = 24;
case fatos: limit = 128;
default: limit = 0;
}
Something like that? I'm not sure off hand if this info is available
after build time for protecting mem-set, but we could make the limit a
property of the domain to solve that easily.
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home