VMWare on strike
Weird problem at work today ! After 297 days of fine uptime the VMWare instance on one machine crashed without any apparent reason. It got ,,funny'' after tickets started pouring in and VMWare gave me this answer while trying to restart the image.
After a quick research on the net I found several possible solutions working on Debian GNU/Linux. Some of them pointed out that low disk space was the reason others wrong permissions.
Disk space was fine on my machine and permissions ? Come'on why should VMWare change that on the fly ? After a image backup and a chmod u+s vmware-vmx everything worked fine again.
Weird Software^W !
Unable to change virtual machine power state: Failed to connect to peer process.
After a quick research on the net I found several possible solutions working on Debian GNU/Linux. Some of them pointed out that low disk space was the reason others wrong permissions.
Disk space was fine on my machine and permissions ? Come'on why should VMWare change that on the fly ? After a image backup and a chmod u+s vmware-vmx everything worked fine again.
Weird Software^W !
2 comments
Comments
-
what the ... flying ... okay, that is the most weird thing i've ever heard, but okay, it could be that it's doing a script in which the first statement is doing something which requires disk space and the following statement would fix permissions... and once the first fails, ... the second would never get in place ?
-
Something like that... well it works and the customers are happy :)