Re: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Thanks Christian... I'll try your suggestion.. # modprobe vmcp # sleep 1 # vmcp your command I really appreciate your help. susan -- Date:Thu, 5 Jul 2007 17:10:35 +0200 From:Christian Borntraeger <[EMAIL PROTECTED]> Subject: Re: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device Hi Susan, > While at SLES9, would you recommend hcp be used instead of vmcp at least > during boot? The Basevol/Guestvol script uses hcp, but since it sounded > like vmcp was preferred over hcp, I changed the script to invoke vmcp > instead. I would recommend vmcp, but I am biased here. Use whatever works best for y= ou.=20 > I see udev in the boot process before the vmcp is issued (Basevol/Guestvol > script). However, it is within 4 seconds. If it can take up to 10 seconds, > it sounds like the timing of this not consistent enough at SLES9. The delay is not about start of udev --> use of vmcp, its about vmcp module= =20 loaded --> use of vmcp.=20 I have never seen the 10 second delay on SLES9 under z/VM (The 10 second de= lay=20 is RHEL4 specific and you have to trigger a bug). In fact, I am quite sure= =20 that udev will create the device node in milliseconds in almost every case = if=20 you run under z/VM and dont attach hundreds of devices.=20 So if=20 # modprobe vmcp # sleep 1 # vmcp your command does not work, something is probably going seriously wrong. If you dont want to rely on udev you can always use a pre-defined device no= de=20 in your ram disk. You just have to know the sequence of your kernel modules= ,=20 that create a misc device with dynamic minor. Dynamic minors are assigned a= s=20 63,62,61... and modules that use dynamic minors are for example=20 device_mapper, dasd_eer, zfcp_hbaapi. =2D-=20 IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Gesch=E4ftsf=FChrung: Herbert Kircher=20 Sitz der Gesellschaft: B=F6blingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
>>> On Thu, Jul 5, 2007 at 9:45 AM, in message <[EMAIL PROTECTED]>, Susan Zimmerman <[EMAIL PROTECTED]> wrote: > Hi Christian. Not him, but anyway... > While at SLES9, would you recommend hcp be used instead of vmcp at least > during boot? The Basevol/Guestvol script uses hcp, but since it sounded > like vmcp was preferred over hcp, I changed the script to invoke vmcp > instead. Depending on who you talk to you'll get various opinions about whether cpint or vmcp is "preferred." Both of them depend on a kernel module to create a device node in /dev, so you're likely to have the same issue in either case. > I see udev in the boot process before the vmcp is issued (Basevol/Guestvol > script). However, it is within 4 seconds. If it can take up to 10 seconds, > it sounds like the timing of this not consistent enough at SLES9. A simple "sleep 10" command in your script would likely solve that. Mark Post -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Hi Susan, > While at SLES9, would you recommend hcp be used instead of vmcp at least > during boot? The Basevol/Guestvol script uses hcp, but since it sounded > like vmcp was preferred over hcp, I changed the script to invoke vmcp > instead. I would recommend vmcp, but I am biased here. Use whatever works best for you. > I see udev in the boot process before the vmcp is issued (Basevol/Guestvol > script). However, it is within 4 seconds. If it can take up to 10 seconds, > it sounds like the timing of this not consistent enough at SLES9. The delay is not about start of udev --> use of vmcp, its about vmcp module loaded --> use of vmcp. I have never seen the 10 second delay on SLES9 under z/VM (The 10 second delay is RHEL4 specific and you have to trigger a bug). In fact, I am quite sure that udev will create the device node in milliseconds in almost every case if you run under z/VM and dont attach hundreds of devices. So if # modprobe vmcp # sleep 1 # vmcp your command does not work, something is probably going seriously wrong. If you dont want to rely on udev you can always use a pre-defined device node in your ram disk. You just have to know the sequence of your kernel modules, that create a misc device with dynamic minor. Dynamic minors are assigned as 63,62,61... and modules that use dynamic minors are for example device_mapper, dasd_eer, zfcp_hbaapi. -- IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Herbert Kircher Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Hi Christian. While at SLES9, would you recommend hcp be used instead of vmcp at least during boot? The Basevol/Guestvol script uses hcp, but since it sounded like vmcp was preferred over hcp, I changed the script to invoke vmcp instead. I see udev in the boot process before the vmcp is issued (Basevol/Guestvol script). However, it is within 4 seconds. If it can take up to 10 seconds, it sounds like the timing of this not consistent enough at SLES9. 09:24:45 VFS: Mounted root (ext2 filesystem). Starting udev Creating devices 09:24:46 Loading kernel/drivers/s390/char/vmcp.ko z/VM CP interface loaded . . . 09:24:49 "" Basevol/Guestvol script begins... ."" Welcome to the Linux disk model userid!"" All directories will be in R/W mode."" Basevol/Guestvol script ends."" "" thanks again for your help. susan -- Date:Tue, 3 Jul 2007 09:30:58 +0200 From: Christian Borntraeger <[EMAIL PROTECTED]> Subject: Re: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device Am Montag, 2. Juli 2007 schrieb Susan Zimmerman: > Hi Mark. >=20 > I noticed /sys/class/misc/vmcp was 10 63 >=20 > OSA-LNX1:~ # cat /sys/class/misc/vmcp/dev > 10:63 >=20 > So I deleted /dev/vmcp and manually created the node >=20 > as 10 63 >=20 > and now it works just fine. >=20 > Thanks for your help. Yes, vmcp registers a misc device with dynamic minor number. Therefore it i= s=20 normally not a good idea to have a permanent device node for vmcp, unless y= ou=20 know the load sequence of all your misc devices. Instead udev should be use= d.=20 I know that this is getting trickier on an initrd.=20 There is a problem assigned with udev: device node creation takes time. So= =20 after modprobe , it can take some time to create a device node.=20 (usually milliseconds, but it can take longer) Udev has improved a lot on SLES10 and RHEL5. On these systems you can=20 use "udevsettle" to be sure that udev has finished all its work that was=20 scheduled until now: # modprobe vmcp # udevsettle # vmcp my fancy command will always work as long as the kernel module was able to load. Furthermore= ,=20 both systems use a tmpfs filesystem as /dev so your device folder is=20 re-initialized during boot without stale device nodes.=20 Things are much trickier on SLES9 and RHEL4. Both use an older udev version= =20 without udevsettle. SLES9 does not use tmpfs. SLES9 also does not use udev for devices, which=20 exist during boot, unless you enable the boot.udev init script.=20 RHEL4 uses udev for all devices, but has another issue. There is a race in = the=20 network hotplug scripts (I forgot the bugzilla number). In these script,=20 hotplug is temporarily disabled and udev can loose events. If udev misses a= n=20 event it will wait up to 10 seconds until it continues. Thats why on=20 RHEL4 "modprobe vmcp -> /dev/vmcp appears" will often take 10 seconds. =2D-=20 IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Gesch=E4ftsf=FChrung: Herbert Kircher=20 Sitz der Gesellschaft: B=F6blingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Am Montag, 2. Juli 2007 schrieb Susan Zimmerman: > Hi Mark. > > I noticed /sys/class/misc/vmcp was 10 63 > > OSA-LNX1:~ # cat /sys/class/misc/vmcp/dev > 10:63 > > So I deleted /dev/vmcp and manually created the node > > as 10 63 > > and now it works just fine. > > Thanks for your help. Yes, vmcp registers a misc device with dynamic minor number. Therefore it is normally not a good idea to have a permanent device node for vmcp, unless you know the load sequence of all your misc devices. Instead udev should be used. I know that this is getting trickier on an initrd. There is a problem assigned with udev: device node creation takes time. So after modprobe , it can take some time to create a device node. (usually milliseconds, but it can take longer) Udev has improved a lot on SLES10 and RHEL5. On these systems you can use "udevsettle" to be sure that udev has finished all its work that was scheduled until now: # modprobe vmcp # udevsettle # vmcp my fancy command will always work as long as the kernel module was able to load. Furthermore, both systems use a tmpfs filesystem as /dev so your device folder is re-initialized during boot without stale device nodes. Things are much trickier on SLES9 and RHEL4. Both use an older udev version without udevsettle. SLES9 does not use tmpfs. SLES9 also does not use udev for devices, which exist during boot, unless you enable the boot.udev init script. RHEL4 uses udev for all devices, but has another issue. There is a race in the network hotplug scripts (I forgot the bugzilla number). In these script, hotplug is temporarily disabled and udev can loose events. If udev misses an event it will wait up to 10 seconds until it continues. Thats why on RHEL4 "modprobe vmcp -> /dev/vmcp appears" will often take 10 seconds. -- IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Herbert Kircher Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
>>> On Mon, Jul 2, 2007 at 3:27 PM, in message <[EMAIL PROTECTED]>, "Hall, Ken (GTI)" <[EMAIL PROTECTED]> wrote: > Udev should handle this automatically. Like I said in the previous > note, however, it can take up to 10 seconds for the device node to > appear. When dealing with real hardware, this could very well be the case. I have my doubts that is what is operating here, with a completely internal-to-Linux device node. > Race conditions of this type appear to be common during > rc.sysinit, and also affect fcp devices, particularly when you use them > in combination with LVM and/or multipath. Red Hat supposedly has a fix > either available or coming soon. I'm not aware of any such reports for SLES, but that doesn't mean a lot, since I'm not on the receiving end of any problem reports. Mark Post -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Udev should handle this automatically. Like I said in the previous note, however, it can take up to 10 seconds for the device node to appear. Race conditions of this type appear to be common during rc.sysinit, and also affect fcp devices, particularly when you use them in combination with LVM and/or multipath. Red Hat supposedly has a fix either available or coming soon. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, July 02, 2007 2:54 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] vmcp during boot results in Error: Could not open device /dev/vmcp: No such device >>> On Mon, Jul 2, 2007 at 2:32 PM, in message <[EMAIL PROTECTED] rg>, Susan Zimmerman <[EMAIL PROTECTED]> wrote: > Hi Mark. > > I noticed /sys/class/misc/vmcp was 10 63 > > OSA-LNX1:~ # cat /sys/class/misc/vmcp/dev > 10:63 > > So I deleted /dev/vmcp and manually created the node > > as 10 63 > > and now it works just fine. In addition to what Adam said about making sure to rebuild your initrd and re-run zipl, be careful of what you've done here. On one of my test systems, the device node is 10:61, so it can vary from system to system. If you rmmod the vmcp module, the device node _should_ go away. When you modprobe it again, it should appear dynamically. Mark Post -- 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 This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
>>> On Mon, Jul 2, 2007 at 2:32 PM, in message <[EMAIL PROTECTED]>, Susan Zimmerman <[EMAIL PROTECTED]> wrote: > Hi Mark. > > I noticed /sys/class/misc/vmcp was 10 63 > > OSA-LNX1:~ # cat /sys/class/misc/vmcp/dev > 10:63 > > So I deleted /dev/vmcp and manually created the node > > as 10 63 > > and now it works just fine. In addition to what Adam said about making sure to rebuild your initrd and re-run zipl, be careful of what you've done here. On one of my test systems, the device node is 10:61, so it can vary from system to system. If you rmmod the vmcp module, the device node _should_ go away. When you modprobe it again, it should appear dynamically. Mark Post -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
On Jul 2, 2007, at 12:43 PM, Susan Zimmerman wrote: Hi Mark. I moved vmcp to the INITRD_MODULES but it still results in the same message. You then need to rebuild initrd with mkinitrd and rerun zipl in order to start with the new initrd. 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Hi Mark. I noticed /sys/class/misc/vmcp was 10 63 OSA-LNX1:~ # cat /sys/class/misc/vmcp/dev 10:63 So I deleted /dev/vmcp and manually created the node as 10 63 and now it works just fine. Thanks for your help. Susan _ Hi Mark. I moved vmcp to the INITRD_MODULES but it still results in the same message. during boot: Starting udev Creating devices Loading kernel/drivers/s390/char/vmcp.ko z/VM CP interface loaded . . . Error: Could not open device /dev/vmcp: No such device +++ RC=3 +++ my settings now are: INITRD_MODULES="vmcp" ## Type:string ## ServiceRestart: boot.loadmodules # # This variable contains the list of modules to be loaded # once the main filesystem is active # MODULES_LOADED_ON_BOOT="" >From what I can tell, the device exists... OSA-LNX1:/ # ls -l /dev/vmc* crw--- 1 root root 10, 62 Jun 29 13:06 /dev/vmcp OSA-LNX1:/ # Thanks again for any and all help! Susan -- Date:Fri, 29 Jun 2007 14:34:23 -0600 From:Mark Post <[EMAIL PROTECTED]> Subject: Re: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device >>> On Fri, Jun 29, 2007 at 4:31 PM, in message = , Susan Zimmerman <[EMAIL PROTECTED]> wrote:=20 > Hi Listers. >=20 > I am trying to issue a vmcp command within a boot script and receive the > following message during boot: >=20 > Error: Could not open device /dev/vmcp: No such device > +++ RC=3D3 +++ >=20 > Once the system is booted, I can see the device... >=20 > Any ideas on how to make this device permanent? Which distribution are you running? On SLES, you can add vmcp to the list = of modules that need to be in the initrd by editing /etc/sysconfig/kernel INITRD_MODULES=3D"vmcp" Mark Post -- -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
There's a delay between the time the module gets loaded and udev notices and creates the device node. This has bit us on other devices (tape, fcp) as well. We've had some discussions with Red Hat about it, and there's supposed to be some kind of fix in RHEL 4.5 or 5.0. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Susan Zimmerman Sent: Monday, July 02, 2007 1:43 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] vmcp during boot results in Error: Could not open device /dev/vmcp: No such device Hi Mark. I moved vmcp to the INITRD_MODULES but it still results in the same message. during boot: Starting udev Creating devices Loading kernel/drivers/s390/char/vmcp.ko z/VM CP interface loaded . . . Error: Could not open device /dev/vmcp: No such device +++ RC=3 +++ my settings now are: INITRD_MODULES="vmcp" ## Type:string ## ServiceRestart: boot.loadmodules # # This variable contains the list of modules to be loaded # once the main filesystem is active # MODULES_LOADED_ON_BOOT="" >From what I can tell, the device exists... OSA-LNX1:/ # ls -l /dev/vmc* crw--- 1 root root 10, 62 Jun 29 13:06 /dev/vmcp OSA-LNX1:/ # Thanks again for any and all help! Susan -- Date:Fri, 29 Jun 2007 14:34:23 -0600 From:Mark Post <[EMAIL PROTECTED]> Subject: Re: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device >>> On Fri, Jun 29, 2007 at 4:31 PM, in message = , Susan Zimmerman <[EMAIL PROTECTED]> wrote:=20 > Hi Listers. >=20 > I am trying to issue a vmcp command within a boot script and receive the > following message during boot: >=20 > Error: Could not open device /dev/vmcp: No such device > +++ RC=3D3 +++ >=20 > Once the system is booted, I can see the device... >=20 > Any ideas on how to make this device permanent? Which distribution are you running? On SLES, you can add vmcp to the list = of modules that need to be in the initrd by editing /etc/sysconfig/kernel INITRD_MODULES=3D"vmcp" Mark Post -- -- 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 This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Hi Mark. I moved vmcp to the INITRD_MODULES but it still results in the same message. during boot: Starting udev Creating devices Loading kernel/drivers/s390/char/vmcp.ko z/VM CP interface loaded . . . Error: Could not open device /dev/vmcp: No such device +++ RC=3 +++ my settings now are: INITRD_MODULES="vmcp" ## Type:string ## ServiceRestart: boot.loadmodules # # This variable contains the list of modules to be loaded # once the main filesystem is active # MODULES_LOADED_ON_BOOT="" >From what I can tell, the device exists... OSA-LNX1:/ # ls -l /dev/vmc* crw--- 1 root root 10, 62 Jun 29 13:06 /dev/vmcp OSA-LNX1:/ # Thanks again for any and all help! Susan -- Date:Fri, 29 Jun 2007 14:34:23 -0600 From:Mark Post <[EMAIL PROTECTED]> Subject: Re: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device >>> On Fri, Jun 29, 2007 at 4:31 PM, in message = , Susan Zimmerman <[EMAIL PROTECTED]> wrote:=20 > Hi Listers. >=20 > I am trying to issue a vmcp command within a boot script and receive the > following message during boot: >=20 > Error: Could not open device /dev/vmcp: No such device > +++ RC=3D3 +++ >=20 > Once the system is booted, I can see the device... >=20 > Any ideas on how to make this device permanent? Which distribution are you running? On SLES, you can add vmcp to the list = of modules that need to be in the initrd by editing /etc/sysconfig/kernel INITRD_MODULES=3D"vmcp" Mark Post -- -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Hi Mark. We're running SLES9. Perhaps you found my problem... I have it coded on the MODULES_LOADED_ON_BOOT parameter. I'll put it on the INITRD_MODULES instead and see if that resolves my issue. Thank you very much! Susan -- Date:Fri, 29 Jun 2007 14:34:23 -0600 From:Mark Post <[EMAIL PROTECTED]> Subject: Re: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device >>> On Fri, Jun 29, 2007 at 4:31 PM, in message = , Susan Zimmerman <[EMAIL PROTECTED]> wrote:=20 > Hi Listers. >=20 > I am trying to issue a vmcp command within a boot script and receive the > following message during boot: >=20 > Error: Could not open device /dev/vmcp: No such device > +++ RC=3D3 +++ >=20 > Once the system is booted, I can see the device... >=20 > Any ideas on how to make this device permanent? Which distribution are you running? On SLES, you can add vmcp to the list = of modules that need to be in the initrd by editing /etc/sysconfig/kernel INITRD_MODULES=3D"vmcp" Mark Post -- -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
On Fri, 2007-06-29 at 14:34 -0600, Mark Post wrote: > >>> On Fri, Jun 29, 2007 at 4:31 PM, in message > <[EMAIL PROTECTED]>, > Susan Zimmerman <[EMAIL PROTECTED]> wrote: > > Hi Listers. > > > > I am trying to issue a vmcp command within a boot script and receive the > > following message during boot: > > > > Error: Could not open device /dev/vmcp: No such device > > +++ RC=3 +++ > > > > Once the system is booted, I can see the device... > > > > Any ideas on how to make this device permanent? > > Which distribution are you running? On SLES, you can add vmcp to the list of > modules that need to be in the initrd by editing /etc/sysconfig/kernel > INITRD_MODULES="vmcp" > > Mark Post > In RHEL, you can modprobe vmcp in /etc/rc.local, or you can do this directly in your startup script. Early versions of RHEL 4 have a delay between loading the module and the device node showing up in /dev, so you can do something like the attached clone script from the RHEL 4 Redbook (see the function wait_for_device). RHEL 4.5 and beyond shouldn't have this delay. -Brad > -- > 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 clone Description: application/shellscript
Re: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
>>> On Fri, Jun 29, 2007 at 4:31 PM, in message <[EMAIL PROTECTED]>, Susan Zimmerman <[EMAIL PROTECTED]> wrote: > Hi Listers. > > I am trying to issue a vmcp command within a boot script and receive the > following message during boot: > > Error: Could not open device /dev/vmcp: No such device > +++ RC=3 +++ > > Once the system is booted, I can see the device... > > Any ideas on how to make this device permanent? Which distribution are you running? On SLES, you can add vmcp to the list of modules that need to be in the initrd by editing /etc/sysconfig/kernel INITRD_MODULES="vmcp" Mark Post -- 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
vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Hi Listers. I am trying to issue a vmcp command within a boot script and receive the following message during boot: Error: Could not open device /dev/vmcp: No such device +++ RC=3 +++ Once the system is booted, I can see the device... Any ideas on how to make this device permanent? Thanks in advance for any help. Susan -- 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
