On Tue, 12 Jan 2010 10:41:15 +0200 "Ciprian Dorin, Craciun"
<ciprian.crac...@gmail.com> wrote:

>    So I bet that the initial poster expected an (authoritative) answer
> that should have came in the form of an advice based on experience or
> at least something useful... (Not lmgtfy, which I'm sure he already
> did, but did not found a good enough answer (as in authoritative)...)

You are missing the point. Virtualization has been discussed to death
for *YEARS* and all of it is in the misc@ list archives.

Here's the short version of those years of discussion:

1.) Since you can't trust the skill of most developers to write a
perfectly secure operating systems, trusting them to write a perfectly
secure software emulation of hardware is insane.

2.) If systems and application software runs fine on real hardware, but
fails to run on emulated/virtualized hardware, then the problem is in
the virtualization software. --In other words, take questions and
complaints to the vendor of your virtualization software.

3.) Many of the benefits you gain by running a stable and secure
operating system like OpenBSD are lost when you run it as a "guest" on
top of some other insecure "host" operating system.

4.) Most Virtualization Software fails to emulate hardware perfectly.

5.) Most Virtualization Software expects the "host" operating system to
have specific features, and hence, it's not easily portable, or it is
not portable at all.

6.) Most Virtualization Software wants to use fancy hardware features
and/or have direct access to hardware. If your vitualization software
is by-passing the restrictions enforced by the "host" operating system,
then the "host" operating systems is not able to do it's job.


Virtualization can be very useful in certain situations, yet you not
only need to fully understand and accept the implications and risks of
virtualization, but *you* also need to test it in *your* environment to
determine if it meets *your* requirements. Anything less is irrelevant!

If you're too lazy to do the weeks or months of research work on your
own, then you really should not use virtualization. Unfortunately, most
people just believe the constant bullshit from the virtualization
vendors, or ask irrelevant questions on various mailing lists.


Lastly, Bret Lambert is one of the OpenBSD developers, so you can
consider his "lmgtfy" reply as "authoritative" --He's humorously telling
you to do your own work. There is no other way.


-- 
J.C. Roberts

Reply via email to