<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><soapbox><br><br>I haven't really seen a need for that kind of thing, so far. I see all kinds of things for "shared resources" but in the end, most of the things that I need require levels of hardware redundancy. Also, in Linuxland, you don't *really* need to separate things to that level. Why should I have multiple kernel images loaded into memory (multiple VMs on one server) when I can just use "namevirtualhost" for apache, etc. I don't really see the need for virtual machines. 'Course, I'm "old school" as I'm sure Pete's going to call me... It' just that I don't work in a Windows world where you have to put each service on a separate machine so it doesn't conflict and crash.<br><br>I have only had one person explain to me *one* circumstance when virtual
machines make sense. And that's Pete's situation where he buries a Windows VM on a Linux desktop. He can reload the VM in a very short period of time if it gets hosed by viruses, etc. Hardware has gotten so cheap that in corporate environments, it's cheaper to buy machines than to try to maintain VMs.<br><br></soapbox><br><br>I'm interested in watching this discussion unfold.<br><br>Cheers!<br><br>Bob<br><div> </div>--<br>"When once you have tasted flight, you will forever walk the earth with your eyes turned skyward, for there you have been, and there you will always long to return."<br> --Leonardo da Vinci<div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Brad Bartram
<brad.bartram@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> nflug@nflug.org<br><b><span style="font-weight: bold;">Sent:</span></b> Monday, December 15, 2008 1:41:25 PM<br><b><span style="font-weight: bold;">Subject:</span></b> [nflug] Virtualization<br></font><br>
I'm interested in this whole virtualization of servers and services trend that's been on going for quite a while. I've worked with it on workstations and in the traditional host - guest configurations to gain access to non-native applications - you know, user-level stuff. I'm interested in it on the server side of things though. I've read the marketing propaganda and seen the vendor white papers and all the trade news-vertisements, but I'm interested in hearing some real world opinions.<br>
<br>I know some of you have opinions on it. So what's the good, the bad, the shortcomings, and the strengths? Are there any things I should look out for or things I should consider in planning out hardware purchases and such?<br>
<br>Thanks<br><br>Brad<br>
</div></div></div><br>
</body></html>