On Mar 27, 2008, at 7:52 AM, RPN01 wrote:
I'll start with the second part first, and even with a rant, at that: VMWare doesn't work for Linux. If you put a Linux system on a heavily used VMWare box, VMWare can't complete the Linux I/O quickly enough, Linux detects the timeout, and places the filesystem in a read-only state. There is no solution if you want to stay within your standard Linux distribution. VMWare does have a disk driver that is supposed to work, but the only change is that they greatly increased the disk I/O timeout, and installing it means headaches when you later want to apply maintenance to your Linux system.
If this is happening, you have too many virtual machine images, and likely too little memory, on your VMware host. Essentially, oversubscribing I/O bandwidth *or* real memory (note: very different from z/VM there) is a bad idea on most VMware machines. It's not that VMware doesn't work for Linux, as much as it is, VMware (and x86 boxes) cannot scale to the kind of density those of us in the z/VM world expect as a matter of course. Adam ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
