WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xend leaks/bugs/etc

Hollis Blanchard wrote:

On Mon, 2005-04-18 at 10:15 -0500, Anthony Liguori wrote:
Finally, the xend code seems to trust input it receives from domains
which is incompatible with the architectural goal of VM isolation.

This is a very big problem.  One very difficult issue to address is
how to deal with very hostile domains that may attempt DoS attacks by flooding their own console.

This isn't really a xend issue. I'm not sure this *can* be addressed,
and I believe other hypervisors have this problem as well.
I'm not sure I agree. Since Xen only provides shared-memory and event channels, the tools control how frequently they look at shared-memory (so a tool can throttle itself). The only possible DoS venue should be the event channels. The tools should simply be able to unbind from event channels that are considered hostile.

At some point, you have to acknowledge there will be *some* resource
sharing among otherwise isolated domains. Switching domains on a single
CPU will increase cache misses; domains doing lots of (valid and
allowed) IO will reduce shared bus bandwidth for other domains; etc...
There are certainly going to be things that you cannot prevent but that does not mean we shouldn't try to prevent everything we can prevent.

Regards,
Anthony Liguori

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