You (Florian Manschwetus) wrote:
> Am 26.07.2010 05:35, schrieb Edward Martinez:
> > I'm not very fond about xen  virtualization because,  if the  hypervisor  
> > has bugs  it might  bring the entire stack down( host OS along with the 
> > guest) where as if virtualization was being done through something like 
> > virtualbox and if their were any  any bugs.  most likely it  would only 
> > affect the guest OS and  not   the host OS. but i think virtualization 
> > itself  is   a can of problems because,  the  unit  will be running mutiple 
> > kernels at the  same time and i think that   increases the risk of having 
> > many, many  bugs where security might become an issue.
> > 
> > Regards
> > eam1
> 
> In case of an opensolaris dom0 it won't, you can always boot the dom0
> without the hypervisor.
> 
> Florian

And, please, don't forget: A BUG in the BIOS also can bring down the WHOLE
system, as well as a BUG or FAULT in any part of the underlying HADRWARE.

So, in order to minimize that problem, "thin" hypervisors have been designed,
like Xen. Idea is: Less code, less faults. Compare VMware vs. Xen, and you'll
understand, what I'm talking about... In VMware, there's way more code (as it
is a thick hypervisor), so the probability of an error happeing inside thatr
code is higher then with Xen... Then we have PVM and HVM modes. In PVM mode,
there's even less code from the hyperviso in use, as the guest OS can access
the udnerlying hardware in parts directly, whereas in HVM mode, all access to
the underlying hardware is abstracted by the hypervisor. Again: Higer
probability for errors in software-layers happening...

     Matthias
-- 
Matthias Pfützner | Tel.: +49 700 PFUETZNER      | Solange ich nicht dabei-
Lichtenbergstr.73 | mailto:[email protected] | sein muß, können sie sogar
D-64289 Darmstadt | AIM: pfuetz, ICQ: 300967487  | auf mich einschlagen.
Germany      | http://www.pfuetzner.de/matthias/ | Heiner Geißler
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to