Re: z/Linux cloning
this process may still work for you: http://www.redbooks.ibm.com/abstracts/redp3871.html -- Jay Brenneman -- 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
Re: z/Linux cloning
Is anyone doing cloning of FCP LUNs under SLES10 SP2, not minidisks? We're looking at how we might clone our systems which are all using FCP for all of the LUNs. The virtualizaiton cookbooks all refer to using DDR and minidisks. We figure if we can work out a good way to copy the partitions from golden image LUN to clone image LUN, we can work through the rest of the script to make the necessary alterations to the guest. We're trying to stay away from subsystem provided flashcopy type functions due to licensing costs. Craig Collins State of WI -- 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
Re: z/Linux cloning
We do FCP cloning, but since we have 2 sites with separate SAN disks it's not practical to have 'gold image' LUNs - we'd have to keep 2 copies in sync- one at each site. So, since our TSM backup network is common 2 both sites I clone FCP linux servers by doing TSM bare metal restores of the gold image server. I call it YACT - Yet Another Cloning Technique 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: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Craig Collins Sent: Thursday, August 28, 2008 11:26 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning Is anyone doing cloning of FCP LUNs under SLES10 SP2, not minidisks? We're looking at how we might clone our systems which are all using FCP for all of the LUNs. The virtualizaiton cookbooks all refer to using DDR and minidisks. We figure if we can work out a good way to copy the partitions from golden image LUN to clone image LUN, we can work through the rest of the script to make the necessary alterations to the guest. We're trying to stay away from subsystem provided flashcopy type functions due to licensing costs. Craig Collins State of WI -- 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 -- 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
Re: z/Linux cloning
On Aug 28, 2008, at 8:25 AM, Craig Collins wrote: Is anyone doing cloning of FCP LUNs under SLES10 SP2, not minidisks? We're looking at how we might clone our systems which are all using FCP for all of the LUNs. The virtualizaiton cookbooks all refer to using DDR and minidisks. We figure if we can work out a good way to copy the partitions from golden image LUN to clone image LUN, we can work through the rest of the script to make the necessary alterations to the guest. We're trying to stay away from subsystem provided flashcopy type functions due to licensing costs. Well, doing it in the SAN hardware is certainly the fastest and cleanest waybut if you don't want to do that for cost reasons, then you just need to define identically-sized LUNs and have them both online to the target system. Make sure no one has the golden image mounted, and then use dd if=/dev/source-fcp-disk of=/dev/target-fcp- disk bs=4M. (The block size isn't critical, but things will go faster if it's pretty large; tune it so it's a multiple of the actual data transfer size the SAN and FCP adapters support). That would be using Linux, of course. You could use DDR, I suppose, if you use FBA emulation so that the FCP disks look like FBA to the z/ VM system but that may not be acceptable from a performance standpoint. Instead of actually running it on the target system you'd probably want a cloner guest that had the authority to attach all the LUNs r/w, and grab them, image them, and then release them so the actual target system could pick them up once the copy was done. 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
Re: z/Linux cloning
Robert, Did you get my earlier email to you specifically about my interest in this process? Thanks, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Friday, July 18, 2008 1:09 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning We have a cloning process that is down to a single zVM command to create a new image, and we can create new images in about 8 minutes time from zVM command to being able to log into the new image. The master images occupy disk space, but are not running at any time. Since the disk copies are done from zVM via Flashcopy, the cloning process is independent of filesystem choice and works with LVM managed disks. As far as I know, we're the only ones using the process at the moment. If there's an interest, I can share it with you. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 7/18/08 10:36 AM, Quay, Jonathan (IHG) [EMAIL PROTECTED] 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 -- 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 -- 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
Re: z/Linux cloning
I also received a few requests for information about the process we follow here. For those who wrote, I would like to let you know I'm working on compiling it into a format useful for sharing and will follow up with news once it's ready. We've had a number of activities keeping us busy lately. ok r. -Original Message- From: Evans, Kevin R [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 11:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning Robert, Did you get my earlier email to you specifically about my interest in this process? Thanks, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Friday, July 18, 2008 1:09 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning We have a cloning process that is down to a single zVM command to create a new image, and we can create new images in about 8 minutes time from zVM command to being able to log into the new image. The master images occupy disk space, but are not running at any time. Since the disk copies are done from zVM via Flashcopy, the cloning process is independent of filesystem choice and works with LVM managed disks. As far as I know, we're the only ones using the process at the moment. If there's an interest, I can share it with you. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 7/18/08 10:36 AM, Quay, Jonathan (IHG) [EMAIL PROTECTED] 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 -- 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 -- 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 -- 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
Re: z/Linux cloning
I would be interested in either of these approaches. I did reply to Robert Nix offlist, but haven't heard back...so assume that he is not in the office currently. We are relatively new users to zVM and Linux (RHEL). Thanks, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stricklin, Raymond J Sent: Tuesday, July 22, 2008 6:44 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning Our cloning process sounds similar to yours. I have an EXEC which takes care of poking VM:Secure correctly, FLASHCOPYing the necessary MDISKs, and then updating our internal recordkeeping. One command, about two seconds, then another thirty or so to IPL (assuming DNS is updated ahead of time). It's fairly well customized to our site requirements, but the basic building blocks could be easily adapted to other sites. I also suspect now that SLES10 SP2 includes support for the VMUR driver, even though I haven't yet looked closely at the options, we'll be able to get even more fancy with our automation. I can also share details with any interested parties. Some of the drawbacks of doing it from Linux (instead of from CMS) are that FLASHCOPY needs privilege class B, and you're more likely to aggravate LVM. ok r. -Original Message- From: RPN01 [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2008 10:09 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning We have a cloning process that is down to a single zVM command to create a new image, and we can create new images in about 8 minutes time from zVM command to being able to log into the new image. The master images occupy disk space, but are not running at any time. Since the disk copies are done from zVM via Flashcopy, the cloning process is independent of filesystem choice and works with LVM managed disks. As far as I know, we're the only ones using the process at the moment. If there's an interest, I can share it with you. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 7/18/08 10:36 AM, Quay, Jonathan (IHG) [EMAIL PROTECTED] 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 -- 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 -- 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 -- 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
Re: z/Linux cloning
Same here. Been wanting to use Flash. Using FDR,etc. Gerard -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Wednesday, July 23, 2008 5:12 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning I would be interested in either of these approaches. I did reply to Robert Nix offlist, but haven't heard back...so assume that he is not in the office currently. We are relatively new users to zVM and Linux (RHEL). Thanks, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stricklin, Raymond J Sent: Tuesday, July 22, 2008 6:44 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning Our cloning process sounds similar to yours. I have an EXEC which takes care of poking VM:Secure correctly, FLASHCOPYing the necessary MDISKs, and then updating our internal recordkeeping. One command, about two seconds, then another thirty or so to IPL (assuming DNS is updated ahead of time). It's fairly well customized to our site requirements, but the basic building blocks could be easily adapted to other sites. I also suspect now that SLES10 SP2 includes support for the VMUR driver, even though I haven't yet looked closely at the options, we'll be able to get even more fancy with our automation. I can also share details with any interested parties. Some of the drawbacks of doing it from Linux (instead of from CMS) are that FLASHCOPY needs privilege class B, and you're more likely to aggravate LVM. ok r. -Original Message- From: RPN01 [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2008 10:09 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning We have a cloning process that is down to a single zVM command to create a new image, and we can create new images in about 8 minutes time from zVM command to being able to log into the new image. The master images occupy disk space, but are not running at any time. Since the disk copies are done from zVM via Flashcopy, the cloning process is independent of filesystem choice and works with LVM managed disks. As far as I know, we're the only ones using the process at the moment. If there's an interest, I can share it with you. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 7/18/08 10:36 AM, Quay, Jonathan (IHG) [EMAIL PROTECTED] 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 -- 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 -- 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 -- 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 -- 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
Re: z/Linux cloning
Our cloning process sounds similar to yours. I have an EXEC which takes care of poking VM:Secure correctly, FLASHCOPYing the necessary MDISKs, and then updating our internal recordkeeping. One command, about two seconds, then another thirty or so to IPL (assuming DNS is updated ahead of time). It's fairly well customized to our site requirements, but the basic building blocks could be easily adapted to other sites. I also suspect now that SLES10 SP2 includes support for the VMUR driver, even though I haven't yet looked closely at the options, we'll be able to get even more fancy with our automation. I can also share details with any interested parties. Some of the drawbacks of doing it from Linux (instead of from CMS) are that FLASHCOPY needs privilege class B, and you're more likely to aggravate LVM. ok r. -Original Message- From: RPN01 [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2008 10:09 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: z/Linux cloning We have a cloning process that is down to a single zVM command to create a new image, and we can create new images in about 8 minutes time from zVM command to being able to log into the new image. The master images occupy disk space, but are not running at any time. Since the disk copies are done from zVM via Flashcopy, the cloning process is independent of filesystem choice and works with LVM managed disks. As far as I know, we're the only ones using the process at the moment. If there's an interest, I can share it with you. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 7/18/08 10:36 AM, Quay, Jonathan (IHG) [EMAIL PROTECTED] 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 -- 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 -- 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
Re: z/Linux cloning
On Tuesday, 07/22/2008 at 06:46 EDT, Stricklin, Raymond J [EMAIL PROTECTED] wrote: Some of the drawbacks of doing it from Linux (instead of from CMS) are that FLASHCOPY needs privilege class B, and you're more likely to aggravate LVM. You can move class B FLASHCOPY to any privclass you want. Alan Altmark z/VM Development IBM Endicott -- 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
Re: z/Linux cloning
Jonathan, What's the current best practices cloning solution for z/Linux under z/VM? What Brad said. (I started replying before Brad did, but now the entire weekend is almost burned - better late than never I guess.) I started to write - a Linux shell script is included with, and hopefully well described in, z/VM and Linux on IBM System z: The Virtualization Cookbook for SLES10 (and also for RHEL 5). See linuxvm.org/present There's a tar file named virt-cookbook-S10.tgz (-RH5.tgz) - the link is right below the link to the PDF. Disclaimer: The code is not supported and has been only lightly tested - but it has had a few bug fixes and *seems to be* relatively stable. It does it's work from the Linux side. The VM guys like to do their work on the VM side, while the Linux/UNIX guys feel more at home on Linux - so if you're a Linux/UNIX guy, you'll be more at home with this model. Currently clone.sh copies a shut down (golden) image of Linux from a different minidisk on the virtual machine on which it running to a target user ID whose disk is linked read/write (MR). It reads the network info from a parameter file that has to be in CMS format on a read-only 191 disk. The script actually reads *two* parameter files: the source and target. It first tries to copy the golden image with FLASHCOPY and if that fails, it drops back to dasdfmt and dd. After the disk is copied the root file system is temporarily mounted and the configuration files with the networking info (under /etc) are modified. SSH keys are regenerated and key-based authentication is set up. Then the user ID is XAUTOLOGged and if all goes well, the new clone is on the network within a minute. We are hoping to modify the process so: (A) there are two disks copied not one (100 and 101) (B) logical volumes are used (though the script doesn't need to know this as the disks are copied at the minidisk, not the file system level) (C) there is a source user ID, rather than requiring that the golden Linux image exist on the system that is running the clone script (this allows for multiple golden images) Hope this helps. Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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
z/Linux cloning
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
Re: z/Linux cloning
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
Re: z/Linux cloning
We have a cloning process that is down to a single zVM command to create a new image, and we can create new images in about 8 minutes time from zVM command to being able to log into the new image. The master images occupy disk space, but are not running at any time. Since the disk copies are done from zVM via Flashcopy, the cloning process is independent of filesystem choice and works with LVM managed disks. As far as I know, we're the only ones using the process at the moment. If there's an interest, I can share it with you. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 7/18/08 10:36 AM, Quay, Jonathan (IHG) [EMAIL PROTECTED] 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 -- 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
