Ask Slashdot: What Type of Asset Would You Not Virtualize?
An anonymous reader writes "With IT and Data Center consolidation seemingly happening everywhere our small shop is about to receive a corporate mandate to follow suit and preferably accomplish this via virtualization. I've had success with virtualizing low load web servers and other assets but the larger project does intimidate me a little. So I'm wondering: Are there server types, applications and/or assets that I should be hesitant virtualizing today? Are there drawbacks that get glossed over in the rush to consolidate all assets?"
Virtualize management.
Have gnu, will travel.
Assets not to virtualize:
1) Women
2) Beer
3) Profit
"Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
Also, don't put the VM "control station" on the VM. You would think I wouldn't have to say this, but you would be wrong.
I would not virtualize the servers that are running the virtual machines.
'cause if you knock it offline by accident, your easiest tool with which to bring it back online is gone?
Kind of like how it's a bad idea to mess with a host's eth0 settings if you're currently logged in via ssh through eth0.
DRM: Terminator crops for your mind!
Virtual sex is just not the same.
Windows is a hostile environment, it has no interfaces for host partitioning, and can not be reduced to anything usable running under any other system. Independed from that, by the virtue of its immense suckage, it belongs under virtualization even if there is nothing else on the same host.
But I am sure, people who run Windows do not care about performance. Or security. Or reliability. Or having usable package management.
Contrary to the popular belief, there indeed is no God.