Logging the guest off/on will create the virtual machine according to it's current user directory definition which includes those new minidisks. Just rebooting Linux within its current machine doesn't add new devices to the machine. Since you said you wanted to do it dynamically, while the guest is running, the #CP LINK command is the way to do it for minidisks. Example: to connect new MDISK 806 to the virtual machine, from the guest's 3270 console enter this z/VM CP command #CP LINK * 806 806 MR '*' is shorthand for the guest's VM userid. good luck
-----Original Message----- From: Linux on 390 Port on behalf of Martin, Terry R. (CMS/CTR) (CTR) Sent: Sat 5/31/2008 11:13 PM To: [email protected] Subject: Re: Presenting Additional ECKD devices to Linux Guest Dynamically Hi John, Thanks for the info. After adding the DASD to the user DIRECTORY I then re-booted the Linux guest but still could not see the new DASD. I would have thought that by re-booting the guest it have seen the new DASD. Do you need to actually log off of the guest and back on before the new DASD is seen by the guest! I am doing this for the first time on both z/VM and z/Linux so if these questions seem elementary while I am trying to sort this all out, I apologize! Thanks Again, Terry -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Saturday, May 31, 2008 8:24 PM To: [email protected] Subject: Re: Presenting Additional ECKD devices to Linux Guest Dynamically Terry, After adding MDISKs to the linux guest's User directory entry and doing the DIRECTXA the running guest can't see or use the new MDISKs until you do CP LINK commands to the MDISKs from the guest's 3270 console or via secuser or the other ways. #CP Q V DASD from the guest's console will display the disks currently in the virtual machine's configuration, #CP LINK * newvdev newvdev will link the guest to its new MDISK, then do the #CP Q V DASD to verify success. Your remarks about ATTACH-ing a disk to the guest and surprise at finding it unformatted sounds like the disk should have been instead ATTACHed to SYSTEM and then the guest LINK-d to its new MDISK. -------------------------------------------------------- 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 on behalf of Martin, Terry R. (CMS/CTR) (CTR) Sent: Sat 5/31/2008 3:32 PM To: [email protected] Subject: Presenting Additional ECKD devices to Linux Guest Dynamically Hi I am running z/VM 5.3 with a RedHat 4.6 z/Linux (Kernel level 2.6.9-67) guest. I need to give this guest some more ECKD DASD. I want to do this dynamically. As far as I knew to accomplish this I should only need to add the devices to the User Directory bring that new Directory online (DIRECTXA USER). At this point on the Linux side they need to do some things to see the new device. Now I did the above steps once to add three ECKD devices and on the Linux side they were able to see them, everything looked look. However there was a need to add one more ECKD DASD to the Linux guest. I went through the same exact steps and this time they could not see the device. Is there anything else that I need to do on the z/VM side to make this work? I have made sure that the devices are formatted and that they are attached to SYSTEM. I will mention one thing. I was able to ATTACH the REAL DEVICE ADDRESS as VDEV 806(In my case). Once I did that the Linux folks were able to see the ECKD device. However they showed up on the Linux side as un-formatted. This is not the way it is suppose to work. I should need to ATTACH them. I even added the new devices to the CONF file that the RedHaT Kick Start reads and did a Kick Start. The devices still did not show up. Any suggestions would be appreciated. I am going to also post this on the z/ Hi I am running z/VM 5.3 with a RedHat 4.6 z/Linux (Kernel level 2.6.9-67) guest. I need to give this guest some more ECKD DASD. I want to do this dynamically. As far as I knew to accomplish this I should only need to add the devices to the User Directory bring that new Directory online (DIRECTXA USER). At this point on the Linux side they need to do some things to see the new device. Now I did the above steps once to add three ECKD devices and on the Linux side they were able to see them, everything looked look. However there was a need to add one more ECKD DASD to the Linux guest. I went through the same exact steps and this time they could not see the device. Is there anything else that I need to do on the z/VM side to make this work? I have made sure that the devices are formatted and that they are attached to SYSTEM. I will mention one thing. I was able to ATTACH the REAL DEVICE ADDRESS as VDEV 806(In my case). Once I did that the Linux folks were able to see the ECKD device. However they showed up on the Linux side as un-formatted. This is not the way it is suppose to work. I should need to ATTACH them. I even added the new devices to the CONF file that the RedHaT Kick Start reads and did a Kick Start. The devices still did not show up. Any suggestions would be appreciated. I am going to also post this on the z/VM list! Thanks, Terry ---------------------------------------------------------------------- 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
