Re: Migrate Linux to different LPAR
Linux/390 doesn't use grub, unfortunately. That would simplify a lot of things if it could be made to work. This won't be the first time I've said this to someone from CentOS, but I'll say it again. If you want access to real mainframe hardware, you have two choices: IBM's Linux Community system, or the OSDL. I have systems at both for development of Slack/390. Both groups (IBM and Marist College) are very nice and easy to work with. Both have an absolute minimum of system interruptions. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of R P Herrold Sent: Friday, January 12, 2007 12:45 PM To: LINUX-390@VM.MARIST.EDU Subject: Migrate Linux to different LPAR On Fri, 12 Jan 2007, Jones, Russell wrote: > We have recently installed CentOS Linux on our test Linux LPAR. We > would like to migrate it to our production LPAR without having to do a > new install. CentOS is intalled on a single dasd volume. We would like to > - change /etc/modprode.conf Almoost certainly a change in /boot/grub/grub.conf is needed as well; wish I could be of more help, but I lack the hardware > system in a different LPAR? I appreciate any suggestions. We have been speaking with a list member as to the plans for the CentOS-5 '390 product -- We are in a circumstance where (while we can build in a Hercules instance) we need access to some real hardware to make sure deployment matters work as expected. Earlier this week, in a CentOS planning conference call with developers from the UK, Belgium, the US, and .au, we were brainstorming solving this. Out of that process, and a chat with a member of this list, we ended up with this present need statement: > The ancient PCI standalones (2 would be better, if I could simulate a > channel adapter crossover - you mentioned *** as a knowledgable person > to contact, to know who might have abandoned hardware instances to > solicit for donation to the CentOS project), a warm body [ie, a tester > of a trial spin] for feedback on installs on the real McCoy, and > Hercules emulation are the ways to go -- Getting real access possibly > thru IBM, sounds like it would be a neat fix as well. This list has people using the prior CentOS products, and as the core CentOS developers have not had a real ability to test, the currency of our releases and updates has suffered. People interested in helping the project can contact me at my project email: [EMAIL PROTECTED], or my personal email: [EMAIL PROTECTED] if they are shy about speaking publicly about possibilities. -- Russ Herrold (centos developer) -- 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: Migrate Linux to different LPAR
On Jan 12, 2007, at 11:45 AM, R P Herrold wrote: On Fri, 12 Jan 2007, Jones, Russell wrote: We have recently installed CentOS Linux on our test Linux LPAR. We would like to migrate it to our production LPAR without having to do a new install. CentOS is intalled on a single dasd volume. We would like to - change /etc/modprode.conf Almoost certainly a change in /boot/grub/grub.conf is needed as well; wish I could be of more help, but I lack the hardware !!! Does Centos/390 use Grub? Really? 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
Migrate Linux to different LPAR
On Fri, 12 Jan 2007, Jones, Russell wrote: We have recently installed CentOS Linux on our test Linux LPAR. We would like to migrate it to our production LPAR without having to do a new install. CentOS is intalled on a single dasd volume. We would like to - change /etc/modprode.conf Almoost certainly a change in /boot/grub/grub.conf is needed as well; wish I could be of more help, but I lack the hardware system in a different LPAR? I appreciate any suggestions. We have been speaking with a list member as to the plans for the CentOS-5 '390 product -- We are in a circumstance where (while we can build in a Hercules instance) we need access to some real hardware to make sure deployment matters work as expected. Earlier this week, in a CentOS planning conference call with developers from the UK, Belgium, the US, and .au, we were brainstorming solving this. Out of that process, and a chat with a member of this list, we ended up with this present need statement: The ancient PCI standalones (2 would be better, if I could simulate a channel adapter crossover - you mentioned *** as a knowledgable person to contact, to know who might have abandoned hardware instances to solicit for donation to the CentOS project), a warm body [ie, a tester of a trial spin] for feedback on installs on the real McCoy, and Hercules emulation are the ways to go -- Getting real access possibly thru IBM, sounds like it would be a neat fix as well. This list has people using the prior CentOS products, and as the core CentOS developers have not had a real ability to test, the currency of our releases and updates has suffered. People interested in helping the project can contact me at my project email: [EMAIL PROTECTED], or my personal email: [EMAIL PROTECTED] if they are shy about speaking publicly about possibilities. -- Russ Herrold (centos developer) -- 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: Migrate Linux to different LPAR
I would say give it a try on the new LPAR. When you think about it, the only DASD volume that zipl _can_ write to is the current one, 322B. It cannot access 322E. One way to simplify this, and feel better about the end results, would be to make the 322E volume accessible to your current system, copy things over, chroot to it, and run mkinitrd and zipl from there. I do have a pending HOWTO on cloning Linux systems in LPARs, but I haven't had time to get it formatted properly. If what you've done so far didn't really work, I could send it to you. Contact me off-list if necessary. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Russell Sent: Friday, January 12, 2007 11:33 AM To: LINUX-390@VM.MARIST.EDU Subject: Migrate Linux to different LPAR We have recently installed CentOS Linux on our test Linux LPAR. We would like to migrate it to our production LPAR without having to do a new install. CentOS is intalled on a single dasd volume. We would like to simply copy the volume and IPL to the new volume on the new LPAR. The problem is that after we IPL on the new volume, Linux is still pointing to the file system on the old volume. This is the process that we followed to try to change the dasd volume that Linux uses. - change /etc/modprode.conf ochanged "options dasd_mod dasd=322B" to "options dasd_mod dasd=322C" - run mkinitrd to pick up the changes to modprobe.conf omkinitrd -v initrd-2.6.9-42.0.2.EL.img 2.6.9-42.0.2.EL othis showed the line "Loading module dasd_mod with options dasd=322C" so it seemed like changes were picked up. - run zipl command ozipl -V ocontents of zipl.conf looks like this: * [defaultboot] * default=linux * target=/boot/ * [linux] * image=/boot/vmlinuz-2.6.9-42.0.2.EL * ramdisk=/boot/initrd-2.6.9-42.0.2.EL.img * parameters="root=/dev/VolGroup00/LogVol00" Output from zipl contained the following messages: DASD device number..: 322b Preparing boot device: dasda (322b). Those messages lead me to believe that it is still pointing to the old dasd address. The plan was to make the dasd address changes, copy the volume, and then set the dasd address back to the original address on the old system, and IPL the new volume in the new LPAR. Is there something that I am missing? Is there and easier way to clone a linux system in a different LPAR? I appreciate any suggestions. Thanks, Russell Jones ANPAC System Programmer -- 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
Migrate Linux to different LPAR
We have recently installed CentOS Linux on our test Linux LPAR. We would like to migrate it to our production LPAR without having to do a new install. CentOS is intalled on a single dasd volume. We would like to simply copy the volume and IPL to the new volume on the new LPAR. The problem is that after we IPL on the new volume, Linux is still pointing to the file system on the old volume. This is the process that we followed to try to change the dasd volume that Linux uses. - change /etc/modprode.conf ochanged "options dasd_mod dasd=322B" to "options dasd_mod dasd=322C" - run mkinitrd to pick up the changes to modprobe.conf omkinitrd -v initrd-2.6.9-42.0.2.EL.img 2.6.9-42.0.2.EL othis showed the line "Loading module dasd_mod with options dasd=322C" so it seemed like changes were picked up. - run zipl command ozipl -V ocontents of zipl.conf looks like this: * [defaultboot] * default=linux * target=/boot/ * [linux] * image=/boot/vmlinuz-2.6.9-42.0.2.EL * ramdisk=/boot/initrd-2.6.9-42.0.2.EL.img * parameters="root=/dev/VolGroup00/LogVol00" Output from zipl contained the following messages: DASD device number..: 322b Preparing boot device: dasda (322b). Those messages lead me to believe that it is still pointing to the old dasd address. The plan was to make the dasd address changes, copy the volume, and then set the dasd address back to the original address on the old system, and IPL the new volume in the new LPAR. Is there something that I am missing? Is there and easier way to clone a linux system in a different LPAR? I appreciate any suggestions. Thanks, Russell Jones ANPAC System Programmer CONFIDENTIALITY/PRIVILEGE NOTICE: This transmission and any attachments are intended solely for the addressee. The information contained in this transmission is confidential in nature and protected from further use or disclosure under U.S. Pub. L. 106-102, 113 U.S. Stat. 1338 (1999), and may be subject to attorney-client or other legal privilege. Your use or disclosure of this information for any purpose other than that intended by its transmittal is strictly prohibited and may subject you to fines and/or penalties under federal and state law. If you are not the intended recipient of this transmission, please destroy all copies received and confirm destruction to the sender via return transmittal. -- 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
