February 28, 2007
Shakes Fist at VMWare
Hypothesis: It seems VMWare virtual machines, when left running in the background while interacted with all day through http/ftp and ssh, have a tendency to fragment over time to the extent that disk reads take too long for VMWare to read, causing it to yield the gruesome
“Warning: the system was unable to load a page of memory; this can be caused by network problems or a failing hard disk drive.”
Instead of working on Teamforge this evening, I found myself freeing up 13GB of hard disk space (I had a total of 2GB free before. Those of you with the math skillz now know the deplorable size of my hard drive) defragmenting the disk. Hopefully I’m right and the virtual machine will resume normal operating normally after this is finished.
I suppose this is a good night to chill and read a bit from Programming Ruby: The Pragmatic Programmers’ Guide by Dave Thomas, Chad Fowler, and Andy Hunt.
Conclusion: Defragmenting the disk did not help. I suspect this is due to the fact that the virtual machine’s files could not be defragmented…. I assume they were in use by some process. Deleting 564d09c5-814d-c273-dc07-0b603299df80.vmem and 564d09c5-814d-c273-dc07-0b603299df80.vmem.lck however, however, fixed the problem. Something weird is definitely going on with my computer today though :-/

By email























