On Feb 24, 2007, at 11:25 AM, Tom Duerbusch wrote:
VDISK is different. Actually, it isn't vdisk is different, it is memory is different.
..no, not really.
But once I give a user access to virtual storage (max guest machine size plus vdisk(s)), I can't throttle his usage. And in the very vast amount of cases, I wouldn't want to. But if/when that time comes, when vdisk starts getting pounded, in effect the working storage size of that guest, jumps to something you never seen before, or expected, and even when planned for, impacts the production systems (as they start getting paged out).
...
We don't have a "set maxressize=" parm in CP.
Except, of course, that you trivially *CAN* set MAXSTOR, and then system-wide set Userlim for VDISK to 0, and then specify the VDISK in the directory. Ta-da! I'm with Mark: If you're giving a guest so much VDISK (for swap or otherwise) that you can't afford to let him use it, the problem is in the directory, and the person who specified it. 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
