12 messages in org.freebsd.freebsd-currentRe: My FreeBSD-current/Xen install notes| From | Sent On | Attachments |
|---|---|---|
| Saifi Khan | May 18, 2009 7:37 pm | |
| Adrian Chadd | May 18, 2009 8:52 pm | |
| Saifi Khan | May 18, 2009 9:25 pm | |
| Ivan Voras | May 19, 2009 1:44 am | |
| Adrian Chadd | May 19, 2009 6:30 am | |
| Saifi Khan | May 19, 2009 9:25 am | |
| Adrian Chadd | May 19, 2009 5:29 pm | |
| Peter Jeremy | May 21, 2009 2:51 pm | |
| Michael David Crawford | May 22, 2009 4:21 am | |
| Julian Stecklina | May 22, 2009 5:57 am | |
| Kip Macy | May 22, 2009 12:45 pm | |
| Julian Stecklina | May 22, 2009 6:23 pm |
| Subject: | Re: My FreeBSD-current/Xen install notes | |
|---|---|---|
| From: | Adrian Chadd (adr...@freebsd.org) | |
| Date: | May 19, 2009 5:29:46 pm | |
| List: | org.freebsd.freebsd-current | |
2009/5/20 Saifi Khan <saif...@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
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...@freebsd.org"