![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
VMWare kills chickens. Think of the chickens.
I'm convinced there's a whole bunch of dead chickens in bizarre voodoo rituals coming out of the VMWare factory.
We just upgraded our VMWare ESX cluster from 3.0.1 to 3.5 and added two new machines. All while I was able to remain logged in with a home directory on virtual machine hosted on there. I am reminded of the time I was able to upgrade the RAM in both of existing servers, the while remaining logged in to virtual machines running on there.
To make this clear: You have two machines. You turn one of them off (with warning..) and the servers running on it migrate to the second one. You upgrade that machine, turn it back on, migrate the virtual servers back, turn off the other one, do the upgrade, turn it back on, and hey presto, you've kept your virtual machines running despite turning off both of the servers they were running on. This is very cool stuff :)
We just upgraded our VMWare ESX cluster from 3.0.1 to 3.5 and added two new machines. All while I was able to remain logged in with a home directory on virtual machine hosted on there. I am reminded of the time I was able to upgrade the RAM in both of existing servers, the while remaining logged in to virtual machines running on there.
To make this clear: You have two machines. You turn one of them off (with warning..) and the servers running on it migrate to the second one. You upgrade that machine, turn it back on, migrate the virtual servers back, turn off the other one, do the upgrade, turn it back on, and hey presto, you've kept your virtual machines running despite turning off both of the servers they were running on. This is very cool stuff :)