Date: Wed, 20 May 2009 08:30:09 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Saifi Khan <saifi.khan@twincling.org> Cc: freebsd-xen@freebsd.org, freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: My FreeBSD-current/Xen install notes Message-ID: <d763ac660905191730n2d6313edhac6c866de20f137d@mail.gmail.com> In-Reply-To: <Pine.LNX.4.64.0905192149580.6589@localhost> References: <d763ac660905180553x5c7b3c5bq61acab3d28810a24@mail.gmail.com> <Pine.LNX.4.64.0905190807290.887@localhost> <d763ac660905182052t294e588bu593f1d660aef8b52@mail.gmail.com> <Pine.LNX.4.64.0905190944510.1090@localhost> <d763ac660905190631p2ff604b0gaa12ee3026b91ebc@mail.gmail.com> <Pine.LNX.4.64.0905192149580.6589@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/5/20 Saifi Khan <saifi.khan@twincling.org>: > Could you please share 'your insight' on the > 'set of virtualization problems' that Xen solves ? Xen lets you run multiple versions of modified OSes on the same box. Each OS for the most part can treat its small pool of resources as its own. It hides the underlying hardware from the virtual domain (although its apparently quite popular to break out bits of hardware to appear in the virtual domain.) The Xen paravirtualisation stuff in -theory- should be more lightweight than full hardware virtualisation and it should perform better. In practice? That's very much workload dependant. Xen also lets you write "other" OSes without needing to care about the hardware. One of my friends bootstrapped a toy OS of his inside Xen. He can then run it on any and all Xen boxes, unmodified, regardless of the underlying hardware. That really hasn't been exploited to its full potential though. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d763ac660905191730n2d6313edhac6c866de20f137d>