>>> On Sat, Feb 24, 2007 at 12:25 PM, in message <[EMAIL PROTECTED]>, Tom Duerbusch <[EMAIL PROTECTED]> wrote: > VDISK is different. Actually, it isn't vdisk is different, it is memory > is different.
Actually, it's not. It's a shared resource, and the systems programmer has complete control over it. > CP lets me throttle every other shared resource. > I can SET SHARE to throttle or cap CPU. > I can throttle or cap I/O rates for a particular user. > But once I give a user access to virtual storage (max guest machine > size plus vdisk(s)), I can't throttle his usage. That's like saying "once I turn quickdsp on for a guest, I can't control it." You control it by controlling access to it in the first place, not by handing it out and praying the guest doesn't actually use it. For Linux guests in particular, you had better assume that it will use all the virtual storage you define for it in the CP directory, because it will. The CP directory is where you control their usage of the resource. Not after the fact when things go haywire. You do the same for VDISK. You control it at the point of allocation, not at the point of use. If the systems programmer is handing out too many resources for the system to be able to handle it properly, that's not the fault of the guests that are running. That onus rests on the systems programmer and management, if they haven't provided the tools to do the job right. The bottom line is, the smooth running of the system is the responsibility of the systems programmer. If they're not doing the job right, bad things will happen, regardless of the resource being discussed. Mark Post ---------------------------------------------------------------------- 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
