Brian, I suggest you don't define another 2gb Linux guest else VM might run out of page slots and then crash. Ignoring performance issues, your 2 mod3's of 4.6gb of pages + 8gb C + 0.5gb X = 13.1gb and another 2gb Linux guest (14gb of Linux pages) will force CP to page the excess to your spool dasd which might not have enough free slots, in which case VM crashes.
-------------------------------------------------------- This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -----Original Message----- From: The IBM z/VM Operating System on behalf of Hamilton, Brian Sent: Sat 3/1/2008 3:55 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Need help preparing a presentation explaining how zVM manages storage....zVM 5.2 Trying to put together a high level presentation explaining how VM manages its storage. The presentation is being given to our user community. Some background info, 1 VM lpar defined with approx. 8gb of central storage and 512mb of expanded storage, 1 IFL processor. 2 full 3390 mod3's have been defined for paging. 6 linux instances running all of which are defined at 2gb. As of today there are no performance issues (knock on wood). Some of the questions being asked thus the reason for the presentation, - you only have 8gb of central and 512mb of expanded storage however you have 6 linux instances running each defined at 2gb...how is VM managing that, especially when you only have 8gb of central? - how and when does the 512mb of expanded storage come into play? - how and when does the paging volumes come into play? - big question how many more linux instances can be built at 2gb each? Thanks
