Check out the Virtualization Cookbooks on linuxvm.org/present: RHEL: http://www.linuxvm.org/present/misc/virt-cookbook-RH5.pdf
SLES: http://www.linuxvm.org/present/misc/virt-cookbook-S10.pdf Cloning is done from Linux (using flashcopy and/or ddr through the vmcp module/command). These use a 'dual boot' approach to clone a golden image to a new user ID. All of the clone config is kept on CMS disk. For a slightly different approach, see the RHEL 4 Cookbook at: http://www.redbooks.ibm.com/abstracts/sg247272.html This does cloning from Linux as well, but moves away from the 'dual boot' approach. From one ID, you can arbitrarily clone a second ID to a third. Also, the configs are kept in Linux instead of CMS. -Brad On Fri, 2008-07-18 at 11:36 -0400, Quay, Jonathan (IHG) wrote: > What's the current "best practices" cloning solution for z/Linux under > z/VM? We've used the one found in "Running z/VM to Host Linux - > Installation and Customization" class documentation (the CLONER and > CLONEDDR virtual machines). Is there one that's newer, better or better > supported? We have multiple CECs, z/Linux lpars, and both Suse and > Redhat, if that makes a difference. We don't anticipate creating > hundreds of clones, maybe 20 or so in the first wave. > > > > > ---------------------------------------------------------------------- > 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 -- Brad Hinson <[EMAIL PROTECTED]> Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 www.redhat.com/z ---------------------------------------------------------------------- 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
