Tom:
I believe you meant they do "not" have z/VM? If you are just looking at
this to run VTAPE you don't need a hypervisor. Run the Linux image in an
LPAR. My interpretation is that they don't have an IFL either so "native"
Linux would be easier to start with. If they decide to buy an IFL in the
Others might be more specific about z/VM advantages over KVM ... but you
certainly lose your knowledge of z/VM to manage and control guests and need
to use a KVM based model for that.. whether that is an issue or not is
about your comfort level with both solutions on z. (and probably others
you
You can also just stick it into the /etc/init.d/boot.local
script, like this... works for us.
# Activate zVM CP interfaces
modprobe vmcp # Load CP communications driver
modprobe vmur # Load unit record driver, which depends on vmcp
/sbin/chccwdev -e 000c# Set "/dev/vmrdr-0.0.000c"
I don't have any SLES 11 to check, but I'm pretty sure there is a
/etc/modprode.d or /etc/modprobe.conf that it goes into
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to
This has probably been discussed quite a bit but I wanted to ask for some
real user feedback.
I have a customer that is interested a POC of z/VSE zLINUX VTAPE.
Unfortunately they do now have z/VM so the zLINUX would have to be in an
LPAR. So the question is 'do I gain/lose anything using KVM as
I'm just the messenger...
Forwarded Message
Subject:IBM Alumni Directory
Date: Tue, 30 Jun 2020 15:59:22 + (UTC)
From: Bob McGrath
To: i...@agentsadvanceinc.com
Spending time updating the online IBM Alumni Directory while trying to
shelter in place.
On 6/30/20 1:44 PM, marcy cortes wrote:
> The correct way would be to use /etc/mod probe.d/ for SUSE
True, but I didn't have time to play around and make sure I had the
correct syntax needed.
Mark Post
--
For LINUX-390
On 6/30/20 1:43 PM, Frank Wolfe wrote:
> Great thank you! Couldn't I just add modprobe vmcp into
> /etc/init.d/boot.local also?
Since SLES11 doesn't have any hint of systemd installed, Jerry's
suggestion would be a non-starter. So, yes, boot.local, after.local, or
a separate script would work.
The correct way would be to use /etc/mod probe.d/ for SUSE
On Tue, Jun 30, 2020 at 10:24 AM Edgington, Jerry <
jerry.edging...@westernsouthernlife.com> wrote:
> Here is an example for Redhat.
>
> [root@u060rh7gld system]# more vmcpdetach.target
> [Unit]
> Description= Detach z/VM mdisk
>
Great thank you! Couldn't I just add modprobe vmcp into
/etc/init.d/boot.local also?
On Tue, Jun 30, 2020 at 1:24 PM Edgington, Jerry <
jerry.edging...@westernsouthernlife.com> wrote:
> Here is an example for Redhat.
>
> [root@u060rh7gld system]# more vmcpdetach.target
> [Unit]
> Description=
Here is an example for Redhat.
[root@u060rh7gld system]# more vmcpdetach.target
[Unit]
Description= Detach z/VM mdisk
Requires=local-fs.target
After=local-fs.target
[Install]
WantedBy=multi-user.target
[root@u060rh7gld system]# more vmcpdetach.service
[Unit]
Description=Detach z/VM Mdisk
On 6/30/20 12:46 PM, Frank Wolfe wrote:
> Hi,
>
> I need the modprobe vmcp module to be loaded on boot which it is not on
> SLES11. Can anyone please tell me how to enable this?
Probably the most straightforward way would be to create a script in
/etc/rc.d/ to issue a modprobe command for it, and
Hi,
I need the modprobe vmcp module to be loaded on boot which it is not on
SLES11. Can anyone please tell me how to enable this?
Regards,
Frank
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to
13 matches
Mail list logo
