RE: Installing RHEL4 to a VM guest
"Post, Mark K" <[email protected]> Mon, 29 Jan 2007 16:44:37 -0500
| Newsgroups | gmane.linux.redhat.s390 |
|---|---|
| Message-ID | <D0A97E1964C1CC47A13B259A4560C443725D56@usahm210.amer.corp.eds.com> |
This is a multi-part message in MIME format. --===============0892001797== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C743EE.AD6DB6D2" This is a multi-part message in MIME format. ------_=_NextPart_001_01C743EE.AD6DB6D2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Well, you're almost right. You don't need to "be" a server, but you must "have" a server for the first three methods. The fact that you're using a Linux workstation tells me that you have a potential server sitting on your desk. If you can get from your VM system to your workstation on port 80 or 21/20, you're all set. =20 If that's not possible, then to get your installation files on DASD, you'll need to: 1. IPL a starter kernel, parmfile and initrd 2. See if you can run dasdfmt, fdasd, and mke2fs from the installer 3. Mount the new file system 4. Copy all the files from the CDs to the file system you just created. =20 Now, the Red Hat installer isn't going to let you do any of that unless you can establish network connectivity to your Linux workstation. If you could do that, you wouldn't be using this method in the first place. So, I recommend downloading one of my Slack/390 installation kernels and initrds, and using that to do the setup I listed above. After that, you should be able to start the Red Hat installation process. =20 =20 Mark Post ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, January 18, 2007 6:15 PM To: [email protected] Subject: Installing RHEL4 to a VM guest =09 =09 Hi, =20 I've got to say that this is not a trivial task. =20 I've managed to get the IPL the kernel in a VM guest and can telnet into the installation program from a linux workstation but I can only get so far as selecting an installation type. =20 My choices are NFS, FTP, HTTP, or DASD. =20 I've got the .iso images on CDs but my problem is now how to get them onto the vm guest (now running the install program). =20 As far as I can tell from the available documentation (I will not expound on my frustration at this point) I must BE a server for the first three methods and I'm not. That leaves DASD as an install method and from what I can tell (gurgle) I must somehow move the .iso files to the VM guest. Where to put them and how to get them, however, remains a mystery. =20 So, my question is: how do I move the .iso files to VM and are .iso files OK or do they somehow have to be extractetd into the RPMS, etc. in order for this to work. Where do I put them? How does dasdb1 and dasdc1 play into this? Is there ANY documentation suited to a mainframer anywhere out there? =20 wow! ------_=_NextPart_001_01C743EE.AD6DB6D2 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2>Well, you're almost right. You don't need to "be" a = server, but you=20 must "have" a server for the first three methods. The fact that = you're=20 using a Linux workstation tells me that you have a potential server = sitting on=20 your desk. If you can get from your VM system to your workstation = on port=20 80 or 21/20, you're all set.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2>If that's not possible, then to get your installation files on = DASD,=20 you'll need to:</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2>1. IPL a starter kernel, parmfile and = initrd</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2>2. See if you can run dasdfmt, fdasd, and mke2fs from the=20 installer</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2>3. Mount the new file system</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2>4. Copy all the files from the CDs to the file system you just=20 created.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2>Now, the Red Hat installer isn't going to let you do any of = that unless=20 you can establish network connectivity to your Linux workstation. = If you=20 could do that, you wouldn't be using this method in the first = place. So, I=20 recommend downloading one of my Slack/390 installation kernels and = initrds, and=20 using that to do the setup I listed above. After that, you should = be able=20 to start the Red Hat installation process.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D295023921-29012007><FONT = face=3DArial=20 size=3D2>Mark Post</FONT></SPAN></DIV><BR> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> = [email protected]=20 [mailto:[email protected]] <B>On Behalf Of=20 </B>[email protected]<BR><B>Sent:</B> Thursday, January 18, = 2007 6:15=20 PM<BR><B>To:</B> [email protected]<BR><B>Subject:</B> = Installing=20 RHEL4 to a VM guest<BR></FONT><BR></DIV> <DIV></DIV> <DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I've got to say that this is not a = trivial=20 task.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I've managed to get the IPL the = kernel in a VM=20 guest and can telnet into the installation program from a linux = workstation=20 but I can only get so far as selecting an installation = type.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>My choices are NFS, FTP, HTTP, or=20 DASD.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I've got the .iso images on CDs but = my problem is=20 now how to get them onto the vm guest (now running the install=20 program).</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>As far as I can tell from the = available=20 documentation (I will not expound on my frustration at this point) I = must BE a=20 server for the first three methods and I'm not. That leaves DASD as an = install=20 method and from what I can tell (gurgle) I must somehow move the .iso = files to=20 the VM guest. Where to put them and how to get them, however, remains = a=20 mystery.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>So, my question is: how do I move the = .iso files=20 to VM and are .iso files OK or do they somehow have to be extractetd = into the=20 RPMS, etc. in order for this to work. Where do I put them? How does = dasdb1 and=20 dasdc1 play into this? Is there ANY documentation suited to a = mainframer=20 anywhere out there?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial = size=3D2>wow!</FONT></DIV></BLOCKQUOTE></BODY></HTML> ------_=_NextPart_001_01C743EE.AD6DB6D2-- --===============0892001797== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Redhat-s390-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/redhat-s390-list --===============0892001797==--