Re: Presenting Additional ECKD devices to Linux Guest Dynamically
On Sat, 31 May 2008 23:56:57 -0400, Martin, Terry R. (CMS/CTR) (CTR) <[EMAIL PROTECTED]> wrote: >If the guest is re-booted will the LINKED DASD is be there after the >re-boot or would I need to re-LINK? > The LINK survives a reboot. (IPL command.) (So does ATTACH.) It does not survive a LOGOFF. So it is best to both update the directory and do the LINK or ATTACH. If you use MDISK or LINK in the directory, you would use LINK. If you use DEDICATE in the directory, you would use ATTACH. >Does it matter whether I issue the LINK via the MAINT user or does it >have to be done from the guest itself? A link must be issued from the guest. There are ways to do this from some other privileged userid via SET SECUSER. This was discussed on this list very recently. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
No problem Cal. I appreciate the response! Terry -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Cal Fisher Sent: Sunday, June 01, 2008 8:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Presenting Additional ECKD devices to Linux Guest Dynamically Sorry about that. Guess I got carried away. :-) Cal Fisher My tour in the Navy The MVMUA website -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Sunday, June 01, 2008 1:19 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Presenting Additional ECKD devices to Linux Guest Dynamically >>> On Sun, Jun 1, 2008 at 12:19 AM, in message <[EMAIL PROTECTED]>, Cal Fisher <[EMAIL PROTECTED]> wrote: -snip- > Not sure about RedHat but > on SuSE the command would be chccwdev -e 0.0.addr Then configure the device > with dasd_configure 0.0.addr 1 0 Just FYI, but doing the chccwdev and dasd_configure would be redundant. Do one or the other, but not both. If you want to bring a volume online _and_ use DIAG I/O, then dasd_configure would be more convenient, but other than that, there's no real benefit to either one for dealing with disks. Mark Post
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
Sorry about that. Guess I got carried away. :-) Cal Fisher My tour in the Navy The MVMUA website -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Sunday, June 01, 2008 1:19 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Presenting Additional ECKD devices to Linux Guest Dynamically >>> On Sun, Jun 1, 2008 at 12:19 AM, in message <[EMAIL PROTECTED]>, Cal Fisher <[EMAIL PROTECTED]> wrote: -snip- > Not sure about RedHat but > on SuSE the command would be chccwdev -e 0.0.addr Then configure the device > with dasd_configure 0.0.addr 1 0 Just FYI, but doing the chccwdev and dasd_configure would be redundant. Do one or the other, but not both. If you want to bring a volume online _and_ use DIAG I/O, then dasd_configure would be more convenient, but other than that, there's no real benefit to either one for dealing with disks. Mark Post
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
Hi Ivica, I think I have it now! Thanks to you and all else who helped me with this. I really appreciate it. Thanks Again, Terry From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ivica Brodaric Sent: Sunday, June 01, 2008 4:47 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Presenting Additional ECKD devices to Linux Guest Dynamically There is another way of making things permanent - through PROFILE EXEC, but I suggest you stick with the directory for these commands. Also, if you are new to VM, I suggest you stick with minidisks - they are so much more convenient that you have to have a good reason to use dedicated DASD. When you attach a real DASD to a user, then only that user can use it and it doesn't appear in DIRMAP listing, so you'll have to remember that that disk belongs to a Linux guest. There are however some performance benefits in using dedicated DASD (no cylinder address translation plus I/O assist), but if you have fast DASDs with lots of cache in the controller, which is common these days, you won't see the difference, especially if you use minidisk caching on top of that. Dedicating DASD can still make sense for a large production z/OS or z/VSE guests where you want to extract the last drop of performance, but for Linux guests, IMHO, there's not much point unless you have a huge (multi-disk) database or something like that. If you want to give a Linux guest a whole-DASD worth of space, I suggest you attach it to SYSTEM, define the cylinder 0 as a minidisk belonging to $ALLOC$ user (to avoid accidental overwriting of DASD volume label) and the rest of the DASD as a minidisk belonging to the Linux guest. To attach the DASD to SYSTEM at VM IPL time, the DASD volume label has to be included in user volume list in SYSTEM CONFIG. Cheers, Ivica
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
>>> On Sun, Jun 1, 2008 at 12:19 AM, in message <[EMAIL PROTECTED]>, Cal Fisher <[EMAIL PROTECTED]> wrote: -snip- > Not sure about RedHat but > on SuSE the command would be chccwdev -e 0.0.addr Then configure the device > with dasd_configure 0.0.addr 1 0 Just FYI, but doing the chccwdev and dasd_configure would be redundant. Do one or the other, but not both. If you want to bring a volume online _and_ use DIAG I/O, then dasd_configure would be more convenient, but other than that, there's no real benefit to either one for dealing with disks. Mark Post
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
There is another way of making things permanent - through PROFILE EXEC, but I suggest you stick with the directory for these commands. Also, if you are new to VM, I suggest you stick with minidisks - they are so much more convenient that you have to have a good reason to use dedicated DASD. When you attach a real DASD to a user, then only that user can use it and it doesn't appear in DIRMAP listing, so you'll have to remember that that disk belongs to a Linux guest. There are however some performance benefits in using dedicated DASD (no cylinder address translation plus I/O assist), but if you have fast DASDs with lots of cache in the controller, which is common these days, you won't see the difference, especially if you use minidisk caching on top of that. Dedicating DASD can still make sense for a large production z/OS or z/VSE guests where you want to extract the last drop of performance, but for Linux guests, IMHO, there's not much point unless you have a huge (multi-disk) database or something like that. If you want to give a Linux guest a whole-DASD worth of space, I suggest you attach it to SYSTEM, define the cylinder 0 as a minidisk belonging to $ALLOC$ user (to avoid accidental overwriting of DASD volume label) and the rest of the DASD as a minidisk belonging to the Linux guest. To attach the DASD to SYSTEM at VM IPL time, the DASD volume label has to be included in user volume list in SYSTEM CONFIG. Cheers, Ivica
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
You cannot LINK real DASD but you can ATTACH real DASD as a virtual address to your Linux guest. You can run LINK command from your guest and ATTACH command from any authorised user (normally a user with a privilege class B; MAINT normally has that authorisation). Both LINK and ATTACH commands will survive Linux re-boot but not LOGOFF of your guest virtual machine. To make things permanent, you have to add a LINK directory control statement (to make LINK command permanent) and DEDICATE directory control statement (to make ATTACH command permanent) to the user directory entry for that guest and then compile the directory and bring it online using a method implemented on your site (DIRECTXA, DIRMAINT, VM:Secure, ...). Be mindful of the order of operands for DEDICATE - it's "DEDICATE vdev rdev", i.e. the reverse of what you specify for ATTACH. Ivica On Sun, Jun 1, 2008 at 1:56 PM, Martin, Terry R. (CMS/CTR) (CTR) < [EMAIL PROTECTED]> wrote: > Hi Alan, > > Thanks for the info. One other question. Can I LINK the real DASD device > address AS a virtual address? LINK * 513D 800. I asked this because up > to this point I have presented the DASD to the Linux guest via the USER > DIRECTORY entry as VIRTUAL addresses so I would like to stay consistent > when I LINK them dynamically while the guest is active. > > If the guest is re-booted will the LINKED DASD is be there after the > re-boot or would I need to re-LINK? > > Does it matter whether I issue the LINK via the MAINT user or does it > have to be done from the guest itself? > > This is my first attempt at z/VM and z/Linux so if the questions sound > elementary until I sort this all out, I apologize. > > Thanks, Terry > > -Original Message- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Alan Ackerman > Sent: Saturday, May 31, 2008 10:00 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Presenting Additional ECKD devices to Linux Guest > Dynamically > > On Sat, 31 May 2008 15:29:56 -0400, Martin, Terry R. (CMS/CTR) (CTR) > <[EMAIL PROTECTED]> wrote: > > >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. > > Updating the directory for a virtual machine has no effect on the > virtual= > machine, until the virtual > machine is next logged on. For a virtual machine that is already logged > o= > n, you will have to log off > and log back on again. > > If you want the virtual machine to stay logged on, you can either ATTACH > = > the device to the virtual > machine, or ATTACH it to SYSTEM and then LINK to it from the virtual > mach= > ine. > > Alan Ackerman > Alan (dot) Ackerman (at) Bank of America (dot) com >
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
can't LINK the real dasd address as a virtual address; you can LINK to MDISKs (try HELP CP LINK); see my 2nd linux-390 reply to your post; RE-LINK isn't needed after re-boot; Can't do the guest's LINK from userid MAINT unless you use secuser/SCIF or other methods, for starters enter the LINK command from the guest's VM console using #CP LINK ... The #CP is needed so so z/VM's CP sees and acts on the command and not linux; think of #CP as an escape sequence. good luck 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: The IBM z/VM Operating System on behalf of Martin, Terry R. (CMS/CTR) (CTR) Sent: Sat 5/31/2008 11:56 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Presenting Additional ECKD devices to Linux Guest Dynamically Hi Alan, Thanks for the info. One other question. Can I LINK the real DASD device address AS a virtual address? LINK * 513D 800. I asked this because up to this point I have presented the DASD to the Linux guest via the USER DIRECTORY entry as VIRTUAL addresses so I would like to stay consistent when I LINK them dynamically while the guest is active. If the guest is re-booted will the LINKED DASD is be there after the re-boot or would I need to re-LINK? Does it matter whether I issue the LINK via the MAINT user or does it have to be done from the guest itself? This is my first attempt at z/VM and z/Linux so if the questions sound elementary until I sort this all out, I apologize. Thanks, Terry -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Ackerman Sent: Saturday, May 31, 2008 10:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Presenting Additional ECKD devices to Linux Guest Dynamically On Sat, 31 May 2008 15:29:56 -0400, Martin, Terry R. (CMS/CTR) (CTR) <[EMAIL PROTECTED]> wrote: >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. Updating the directory for a virtual machine has no effect on the virtual= machine, until the virtual machine is next logged on. For a virtual machine that is already logged o= n, you will have to log off and log back on again. If you want the virtual machine to stay logged on, you can either ATTACH = the device to the virtual machine, or ATTACH it to SYSTEM and then LINK to it from the virtual mach= ine. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
Adding the device to the directory and issuing the DIRECTXA does not get the device online to a running server. If you defined the device as a minidisk you need to logon to the vm userid of the server and issue #cp link * addr addr addr is what you defined the device as. If the device was defined as a special you would issue Attach rdev to userid as vdev Rdev is the real device addressw and vdev is the address on the linux server. Then you have to bring the device online to linux. Not sure about RedHat but on SuSE the command would be chccwdev -e 0.0.addr Then configure the device with dasd_configure 0.0.addr 1 0 Cal Fisher My tour in the Navy The MVMUA website -Original Message- <[EMAIL PROTECTED]> wrote: >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.
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
Hi Alan, Thanks for the info. One other question. Can I LINK the real DASD device address AS a virtual address? LINK * 513D 800. I asked this because up to this point I have presented the DASD to the Linux guest via the USER DIRECTORY entry as VIRTUAL addresses so I would like to stay consistent when I LINK them dynamically while the guest is active. If the guest is re-booted will the LINKED DASD is be there after the re-boot or would I need to re-LINK? Does it matter whether I issue the LINK via the MAINT user or does it have to be done from the guest itself? This is my first attempt at z/VM and z/Linux so if the questions sound elementary until I sort this all out, I apologize. Thanks, Terry -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Ackerman Sent: Saturday, May 31, 2008 10:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Presenting Additional ECKD devices to Linux Guest Dynamically On Sat, 31 May 2008 15:29:56 -0400, Martin, Terry R. (CMS/CTR) (CTR) <[EMAIL PROTECTED]> wrote: >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. Updating the directory for a virtual machine has no effect on the virtual= machine, until the virtual machine is next logged on. For a virtual machine that is already logged o= n, you will have to log off and log back on again. If you want the virtual machine to stay logged on, you can either ATTACH = the device to the virtual machine, or ATTACH it to SYSTEM and then LINK to it from the virtual mach= ine. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
Re: Presenting Additional ECKD devices to Linux Guest Dynamically
On Sat, 31 May 2008 15:29:56 -0400, Martin, Terry R. (CMS/CTR) (CTR) <[EMAIL PROTECTED]> wrote: >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. Updating the directory for a virtual machine has no effect on the virtual machine, until the virtual machine is next logged on. For a virtual machine that is already logged o n, you will have to log off and log back on again. If you want the virtual machine to stay logged on, you can either ATTACH the device to the virtual machine, or ATTACH it to SYSTEM and then LINK to it from the virtual mach ine. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
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 Linux list! Thanks, Terry
