Again, more thoughts
Look, guys, in reading everyone's thoughts above, I am going to be the one to point out the obvious that I posted above. No solution is final, no infrastructure implementation has a perfect solution.
You have to take into account the factors of your environment that will affect virtualiztion (note, you can plug any current industry buzz word here, cloud, mobility, etc, etc) from TCO, to operations support, to implementation time, to physical limitations of some hardware, to virtual appliance needs and uses, to DR and Business Continuity plans, etc.
As was mentioned above, many of the threads here seem to about why you CAN'T virtualize. Make a list of what you CAN, compare it what you can't, and then, to be real fun? Find a way to make the can'ts a can! There are no limitations to what we as IT persons can design, can find, and can make happen.
You might remember the big push in the early 2000's was to virtualize to save money! (Note, this also was the mantra of Linux installation) Well, the big companies got wind of this too, they need to make their money, so they will always find a way to squeeze costs out of licenses, that's what they are expected to do! So, you'r job as the IT admin, manager, architect, consultant, is to work to find a solution that may cost more in one area, but save more in another; whether that be licensing costs, long term depreciation, operational costs (more or less support engineers); etc.
The discussion thread was supposed to be around Virtualizing Everything (except in four scenarios).... show how you CAN do it and what the benefit is!
