Re: IP change for a Linux guest
Note that the network management software differs by distro: RHEL uses NetworkManager (see Eric's answer below), SUSE uses wicked, and Ubuntu uses netplan - and beware: Some distros changed their tools over time: E.g. Ubuntu was formerly using NetworkManager at some point if I recall correctly. Each distro has a different user interface - so please consult your distro's manual, they usually have a good description of such tasks. Also, I'd recommend to setup a secondary interface and use that to perform the changes. With z/VM, it's really easy to setup a temporary IUCV connection between two guests (see small snippet below, needs to be performed on both sides - haven't tested it recently, but something along those lines). $ modprobe netiucv # Setup connection to guestB (peer) $ echo guestB>/sys/bus/iucv/drivers/netiucv/connection # Configure device $ ip addr add 192.168.2.1/16 dev iucv0 $ ip link set up dev iucv0 $ ip addr show iucv0 6: iucv0: mtu 9216 qdisc fq_codel state UNKNOWN group default qlen 50 link/slip inet 192.168.3.1/16 scope global iucv0 valid_lft forever preferred_lft forever Ciao, Stefan On 6/30/22 06:00, Eric Chevalier wrote: This is something I've done occasionally in our z/VM guests. All through an ssh session, no less! (Note that our Linux guests are running RHEL8.) In my case, I have a network connection called "enccw0.0.f804". I use the "nmtui" command to make any changes to the connection definition. Then I'll issue the command: nmcli conn down enccw0.0.f804 ; nmcli conn up enccw0.0.f804 The first nmcli command turns off the connection. The second nmcli brings the connection back up, picking up the changes I made with nmtui. Of course this will drop your connection to the original IP address, forcing you to re-establish an ssh connection to the new IP address. You have to stack the two nmcli commands as shown. Obviously, if you just use the first nmcli command you'll never be able to re-establish your ssh session. As a "back door": if I were to issue the first nmcli command without stacking the second, I could still get on to the Linux system by logging on to the guest using a 3270 session. Granted, Linux doesn't support 3270 sessions very well (at least not ours). Full screen applications like vim don't work very well on a 3270 session. But most command-line commands that read from stdin and write to stdout/stderr do work. So through my 3270 session I could issue the "nmcli conn up" command to re-enable ssh sessions. On 6/29/2022 10:15 PM, Peter wrote: Hello When an existing redhat Linux guest on zVM requires a IP change. What are files that I need to change to reflect with new IP address? For an existing Linux, how do I view it's console from a 3270 emulator ? Cause as of due to the IP change the Linux guest is not connectable via SSH. Could someone please guide me ? Regards Peter -- Eric Chevalier Phoenix Software International e...@phoenixsoftware.com Voice: (918) 491-6144 x410 Cell: (918) 629-6393 Fax: (918) 494-2701 This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsich
Re: Using SMC-D in my Linux SVMs
Hi Rob, Sorry for the late reply! Correct, with a z14 you can use SMC-Dv1 only. However, Clefos 7.9 is based (or identical to) RHEL 7.9 - which doesn't have SMC support at all! :O To our credit, we did try to backport SMC to RHEL 7.x, but the kernel was just too old, and the dependencies in the code were piling up way too fast. So if if you want to stick with ClefOS/RHEL, you'd need a 8.x release! As for the smc-tools release, I'd suggest to stick with whatever version your distro provides. This is because most of the new features that a new smc-tools release brings require kernel changes - which usually won't be there, or we would have provided a more recent smc-tools version in the distro. As for live guest relocation, as far as I know that plain won't work at all as long as there's a PCI function attached to the guest. So you'd have to detach the PCI function first, which would terminate any connection right away. Of course, once migrated, you could start over (attach a PCI function, create new connections, etc.), and that should work just fine. Best regards, Stefan Raspl On 12/16/21 20:56, Hamilton, Robert wrote: Thanks, Stefan! Just installed Clefos 7.9.2009, did some yum updates, and uname says 3.10.0-1160.36.2.el7.s390x. We are on a z14 ZR1, so I'm thinking only SMC-Dv1 for us. And it works well among my z/OS systems. I've found 5 or more releases of smc-tools out in the wild, the most recent appears to be 1.7.0, which you released two months ago. Can't quite figure out what or how to download, and the docs you recommended point to a 1.2.1-level release. Found I can't VMRELOCATE a Linux system that has a pcifunction attached. Does the SMC and/or IP know while a socket is open that it has lost the pcifunction and automatically revert to normal HiperSockets (or other IP) communication? And after the VMRELOCATE completes, if a pcifunction is attached, can it restart using SMC-D? R; Rob Hamilton Infrastructure Engineer Chemical Abstracts Service -Original Message- On 12/15/21 17:52, Hamilton, Robert wrote: I have a newly-created ClefOS server on my z/VM system. I have attached HiperSockets devices for each of my (5) HiperSockets networks. They are all configured, and I can talk to each of my z/OS systems over the appropriate HiperSockets networks. I want to ensure that my client can use SMC-D when talking with the z/OS applications on the same CPC. The z/OS systems already talk with each other over HiperSockets using SMC-D, so I already have PCIFs setup in the IODF, and can attach appropriate PCIFs to my new server. Then what? I see I don't have smc-tools on the system anywhere, so I need to get that and somehow make those available. I don't see my customer as wanting to use AF-SMC-type socket connections, so I'm guessing I need to run his application with smc-run...or...??? Presumably it's the same using SMC-D over OSAs, but I'll configure that bridge when I come to it. If you can tell me what I need next, or point me to the appropriate documentation, I'd be most very grateful. Hi Rob, Yes, you can use smc_run to enable existing (binary) TCP applications to use SMC-D. Which specific version of ClefOS are you on, and what are the levels of the Linux kernel and smc-tools? If you have SMC-Dv1, check http://www.vmworkshop.org/2019/present/linuxsmc.pdf, especially p21. If you already have SMC-Dv2, check the presentation at https://community.ibm.com/community/user/ibmz-and-linuxone/viewdocument/2021-07-15-boosting-tcp-networking?CommunityKey=c1293167-6d93-448e-8854-3068846d3dfe=librarydocuments. But, of course, I'll be glad to answer any questions, too! Ciao, Stefan -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Using SMC-D in my Linux SVMs
On 12/15/21 17:52, Hamilton, Robert wrote: I have a newly-created ClefOS server on my z/VM system. I have attached HiperSockets devices for each of my (5) HiperSockets networks. They are all configured, and I can talk to each of my z/OS systems over the appropriate HiperSockets networks. I want to ensure that my client can use SMC-D when talking with the z/OS applications on the same CPC. The z/OS systems already talk with each other over HiperSockets using SMC-D, so I already have PCIFs setup in the IODF, and can attach appropriate PCIFs to my new server. Then what? I see I don't have smc-tools on the system anywhere, so I need to get that and somehow make those available. I don't see my customer as wanting to use AF-SMC-type socket connections, so I'm guessing I need to run his application with smc-run...or...??? Presumably it's the same using SMC-D over OSAs, but I'll configure that bridge when I come to it. If you can tell me what I need next, or point me to the appropriate documentation, I'd be most very grateful. Hi Rob, Yes, you can use smc_run to enable existing (binary) TCP applications to use SMC-D. Which specific version of ClefOS are you on, and what are the levels of the Linux kernel and smc-tools? If you have SMC-Dv1, check http://www.vmworkshop.org/2019/present/linuxsmc.pdf, especially p21. If you already have SMC-Dv2, check the presentation at https://community.ibm.com/community/user/ibmz-and-linuxone/viewdocument/2021-07-15-boosting-tcp-networking?CommunityKey=c1293167-6d93-448e-8854-3068846d3dfe=librarydocuments. But, of course, I'll be glad to answer any questions, too! Ciao, Stefan -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Question About LGR and Hipersocket using RHEL 7.7
Hi Larry, On 4/8/21 6:11 PM, Davis, Larry (National VM Capability) wrote: We are seeing an Issue when Using Hipersockets connected to a DB2 system on z/OS When we perform a VMRELOCATE (LGR) to another member in the complex we lose the HS device and it goes offline The Relocate works fine the HS devices have the same EQID and we see the devices attached on the receiving system OSA 3A00 ATTACHED TO LXCGG01D 08A0 BY LXCGG01D OSA 3A01 ATTACHED TO LXCGG01D 08A1 BY LXCGG01D OSA 3A02 ATTACHED TO LXCGG01D 08A2 BY LXCGG01D Then we need to perform cio_ignore -r 0.0.08A0 cio_ignore -r 0.0.08A0 cio_ignore -r 0.0.08A0 I assume this is a typo and should be A0, A1 and A2, right? Then we have to restart the network devices For some reason during the LGR and/or reboot the devices are getting varied off and/or disabled. This is really a shot in the dark, but: Could it be a case where the device number from source and target system are different, and you have the target system's device IDs on the cio ignore list prior to the migration? I.e. what happens in case you run the cio_ignore commands prior to an LGM? Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
DPM Support for Secure Execution
Since I wouldn't know by what other means to reach the person that raised this question in the presentation 28397 - "Linux on IBM Z and LinuxONE: What's New" at Virtual SHARE yesterday: Yes, DPM does support Secure Execution. -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Looking for advice setting up SMC-D between RHEL and z/OS
For the benefit of others that might be interested in this topic: Turns out the issue was rooted in use of a LINK instead of an INTERFACE statement when defining the OSA in z/OS. Once converted to INTERFACE, things worked as expected. Otherwise, in case of any issues: You can find materials at https://linux-on-z.blogspot.com/p/smc-for-linux-on-ibm-z.html. In particular, check the FAQ at https://linux-on-z.blogspot.com/p/smc-faq.html, and the troubleshooting section at https://linux-on-z.blogspot.com/p/smc-troubleshooting.html. Here's an outline of what has to be done to get SMC-D up and running on Linux: # Hotplug ISM device if not yet visible via lspci command (see next step) # Alternative: Use echo 1 > /sys/bus/pci/slots/0080/power if smc_rnics is # not available $ smc_rnics -e 80 # Verify presence of ISM device # NOTE: No extra setup for VLAN usage required $ lspci 0001:00:00.0 Non-VGA unclassified device: IBM Internal Shared Memory (ISM) virtual PCI device # Run application using smc_run $ smc_run foo_socks # Verify that SMC is really used (see 'SMCD' in final column) $ smcss -a StateUID Inode Local AddressForeign Address Intf Mode ACTIVE 2 115762 10.101.4.8:60594 10.101.4.49:3220 SMCD ACTIVE 2 112844 10.101.4.8:60592 10.101.4.49:3220 SMCD ACTIVE 2 112605 10.101.4.8:60590 10.101.4.49:3220 SMCD Best regards, Stefan Raspl On 12/8/20 5:58 PM, Eric Chevalier wrote: My apologies for the poor formatting of my original message. Let's try again: [root@zlinux4 Temp]# hostname zlinux4.phx [root@zlinux4 Temp]# [root@zlinux4 Temp]# date Tue Dec 8 06:37:35 PST 2020 [root@zlinux4 Temp]# [root@zlinux4 Temp]# lspci 00:00.0 Non-VGA unclassified device: IBM Internal Shared Memory (ISM) virtual PCI device [root@zlinux4 Temp]# [root@zlinux4 Temp]# ls -ld /sys/bus/pci/slots/* drwxr-xr-x 2 root root 0 Dec 7 11:23 /sys/bus/pci/slots/1018 [root@zlinux4 Temp]# [root@zlinux4 Temp]# smc_rnics FID Power PCI_ID PCHID Type PPrt PNET_ID Net-Dev - 1018 1 :00:00.0 07e1 ISM n/a PNET1 n/a [root@zlinux4 Temp]# [root@zlinux4 Temp]# smc_rnics -e 1018 Error: FID 1018 is already enabled [root@zlinux4 Temp]# [root@zlinux4 Temp]# ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: encf804: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 02:00:00:00:00:09 brd ff:ff:ff:ff:ff:ff [root@zlinux4 Temp]# [root@zlinux4 Temp]# smc_pnet [root@zlinux4 Temp]# [root@zlinux4 Temp]# smc_pnet -a PNET1 -I encf804 [root@zlinux4 Temp]# [root@zlinux4 Temp]# smc_pnet PNET1 encf804 n/a 255 [root@zlinux4 Temp]# [root@zlinux4 Temp]# smc_pnet -a PNET1 -D :00:00.0 smc_pnet: Object exists [root@zlinux4 Temp]# [root@zlinux4 Temp]# smc_run sftp eric...@mvs60.phx eric...@mvs60.phx's password: Connected to eric...@mvs60.phx. sftp> quit [root@zlinux4 Temp]# smc_run -d sftp eric...@mvs60.phx libsmc-preload: map sock to AF_SMC eric...@mvs60.phx's password: Connected to eric...@mvs60.phx. sftp> cd Temp sftp> ls -l E* -rwxr-x--- ? 1050 0 429391872 Dec 1 13:14 EJES.V600.pax.Z sftp> get EJES.V600.pax.Z Fetching /u/ericadm/Temp/EJES.V600.pax.Z to EJES.V600.pax.Z /u/ericadm/Temp/EJES.V600.pax.Z 100% 410MB 29.9MB/s 00:13 sftp> sftp> quit [root@zlinux4 Temp]# -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: qclib and smc-tools
On 2020-09-16 18:15, Mark Post wrote: > On 9/16/20 7:23 AM, John Mertic wrote: >> Hey Neale! >> >> Can you point to where the sources are for this? I had only found >> https://www.ibm.com/developerworks/linux/linux390/, but that resource >> doesn't list these newer versions. > > The web page hasn't been updated just yet, since the packages were > *just* made available. Why they aren't maintained on github like some of > their other packages is unknown. The developerWorks webpage is defunct for a while by now - it's still available, but it cannot be updated anymore. To our credit, we *are* working on moving things to github, but that is easier said than done. It would be trivial on a technical basis, but there are administrative impediments that we have to work through. In the meantime, we announce new packages on https://linux-on-z.blogspot.com/. -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
New qclib release (follow-up to VM system name discussion)
qclib v2.2 is out! It introduces two new commands: * zname: Prints information about the IBM Z model generation * zhypinfo: Prints information about virtualization layers The latter stems from a request on this mailing list. For further details, check out our blog post at https://linux-on-z.blogspot.com/2020/09/new-release-qclib-v220.html Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: VM system name
Hi Ingo, On 2020-08-04 13:07, Ingo Adlung wrote: > This said, Stefan, would capacity group capping at the LPAR level show up > as 1.1? And how would you distinguish dedicated from shared capacity (at > any level)? Yes, LPAR groups are supported and would show up between CEC and LPAR - I just left them out to keep things somewhat simple. No distinction between dedicated and shared engines so far - the initial request was about the virtualization layers/names, I just threw this in as a goodie as I know there was at least one guy internally who thought we should have something like that. However, I'm somewhat reluctant to add too much info there - it just gets very complicated very fast (SMT-2 anybone?!), and I'm not asking for trouble. Again, if somebody wants to have exotic content, I'd refer to the json output or qclib proper. Ciao, Stefan > Linux on 390 Port wrote on 04/08/2020 11:54:37: > >> From: Stefan Raspl >> To: LINUX-390@VM.MARIST.EDU >> Date: 04/08/2020 11:54 >> Subject: [EXTERNAL] Re: [LINUX-390] VM system name >> Sent by: Linux on 390 Port >> >> Hi Conny, >> >> On 2020-08-04 10:32, Cornelia Huck wrote: >>> On Tue, 4 Aug 2020 09:33:38 +0200 >>> Stefan Raspl wrote: >>> >>>> Hi Tim, >>>> Thanks for your feedback, your thoughts are greatly appreciated! >>>> >>>> On 2020-08-04 07:56, Timothy Sipples wrote: >>>>> Would this readout make better sense? >>>>> >>>>> $ zhypinfo >>>>> NoLayer TypeName IFL CP >>>>> -- >>>>> 2.2 z/VM_Guest guest myguest2 0 >>>>> 2.1 z/VM_Resource_Pool poolpooltest 3 0 >>>>> 2.0 z/VMhypervisor myzvm 8 0 >>>>> 1 partition guest S38LP43 10 0 >>>>> 0 machine hostS38 34 10 >>>>> >>>>> Then you wouldn't need two columns of numbers. The levels are simply >>>>> embedded in the sequence numbers. Counting would be consistent with > the -l >>>>> and -L outputs, of course. Omitting the second column of numbers also >>>>> frees up more space for the text or even another column. >>>> >>>> Yeah, I'm all for keeping things short and sweet! Using that > float-notation >>>> would require folks to parse out the info (i.e. the '2' from the >> first 3 rows) >>>> once again, which I could imagine might make things a bit tedious. > Maybe we >>>> really don't need that first column to begin with, just print the >> 'level' column >>>> instead! >>> >>> Actually, looking at this, I found the '2.2' notation for a guest >>> confusing anyway... what would a guest inside a guest look like? >> >> Probably 3.x >> >> >>>>> Are the underscores necessary? Maybe "z/VM guest" instead? (Or are > they >>>>> for parsing?) >>>> >>>> Exactly: By eliminating spaces, someone processing the output can >> count fields >>>> instead of relying on columns starting at a certain offset - >> makes things more >>>> robust. >>>> >>>>> Or maybe you don't even need the "guest"/"resource pool" >>>>> additions in the Layer column when you've already got a Type column > and >>>>> decimalized sequence numbers. >>>> >>>> I see your point. But for environments like zCX, the nomenclatureis > not as >>>> obvious. Plus one can use the generic monikers along with the level > info to >>>> address/query output independent of the actual hypervisor in use. >>>> >>>>> And would it make sense to print the >>>>> hypervisor release level in the Layer column, e.g. "z/VM 7.2"? >>>> >>>> H, that would be nice! Problem is that z/VM is one of the few >> environments >>>> where we have that kind of info available - KVM or zCX don't :/ >>> >>> Where is that information coming from? Diag 318? >> >> It depends. qclib uses a number of sources for its data, including STHYI, > Diag >> 204, STSI et al. >> >> >>>>> I don't like unnecessary jargon, so I highly prefer "partition" and >>>>> "machine." I thought about "physical," but some
Re: VM system name
Hi Conny, On 2020-08-04 10:32, Cornelia Huck wrote: > On Tue, 4 Aug 2020 09:33:38 +0200 > Stefan Raspl wrote: > >> Hi Tim, >> Thanks for your feedback, your thoughts are greatly appreciated! >> >> On 2020-08-04 07:56, Timothy Sipples wrote: >>> Would this readout make better sense? >>> >>> $ zhypinfo >>> NoLayer TypeName IFL CP >>> -- >>> 2.2 z/VM_Guest guest myguest2 0 >>> 2.1 z/VM_Resource_Pool poolpooltest 3 0 >>> 2.0 z/VMhypervisor myzvm 8 0 >>> 1 partition guest S38LP43 10 0 >>> 0 machine hostS38 34 10 >>> >>> Then you wouldn't need two columns of numbers. The levels are simply >>> embedded in the sequence numbers. Counting would be consistent with the -l >>> and -L outputs, of course. Omitting the second column of numbers also >>> frees up more space for the text or even another column. >> >> Yeah, I'm all for keeping things short and sweet! Using that float-notation >> would require folks to parse out the info (i.e. the '2' from the first 3 >> rows) >> once again, which I could imagine might make things a bit tedious. Maybe we >> really don't need that first column to begin with, just print the 'level' >> column >> instead! > > Actually, looking at this, I found the '2.2' notation for a guest > confusing anyway... what would a guest inside a guest look like? Probably 3.x >>> Are the underscores necessary? Maybe "z/VM guest" instead? (Or are they >>> for parsing?) >> >> Exactly: By eliminating spaces, someone processing the output can count >> fields >> instead of relying on columns starting at a certain offset - makes things >> more >> robust. >> >>> Or maybe you don't even need the "guest"/"resource pool" >>> additions in the Layer column when you've already got a Type column and >>> decimalized sequence numbers. >> >> I see your point. But for environments like zCX, the nomenclature is not as >> obvious. Plus one can use the generic monikers along with the level info to >> address/query output independent of the actual hypervisor in use. >> >>> And would it make sense to print the >>> hypervisor release level in the Layer column, e.g. "z/VM 7.2"? >> >> H, that would be nice! Problem is that z/VM is one of the few >> environments >> where we have that kind of info available - KVM or zCX don't :/ > > Where is that information coming from? Diag 318? It depends. qclib uses a number of sources for its data, including STHYI, Diag 204, STSI et al. >>> I don't like unnecessary jargon, so I highly prefer "partition" and >>> "machine." I thought about "physical," but sometimes the machine/CEC/CPC >>> isn't physical (zPDT, QEMU). Or use "base" if you prefer. But, honestly, >>> we really don't need 58 questions per month about what a CEC is, which >>> seems inevitable, doesn't it? So let's avoid that. >> >> That 'CEC' comes from qclib which referred to it that way ever since. Yeah, I >> know, weak argument. I would argue that zPDT emulates a CEC, so it is still >> there, just virtual. And QEMU is just a component of KVM, so it would appear >> as >> a 'KVM hypervisor' alike 'z/VM hypervisor' in the example (with LPAR and CEC >> (...) beneath it). > > What would the output for QEMU/tcg look like? (Where does qclib get its > information from? If it is something like STSI that we emulate, we have > a chance of getting something reasonable.) In any case, there wouldn't > be any layers below 'hypervisor'.> (Not relevant for production systems at > all, but I like interfaces to > be consistent... do you have anything people can play with?) tcg hasn't been a focus of qclib at all so far. Try https://public.dhe.ibm.com/software/dw/linux390/ht_src/qclib-2.1.0.tgz and run 'make test', that should do. > > (...) > >>> If the machine is reporting back something beyond the known model >>> generations, then you could print ">z15" or "z15+" or "z16?" until >>> zhypinfo is updated. When zhypinfo is updated you then insert the model >>> generation without the question mark and update the question mark to be >>> "z17?" (for example). Loop, repeat. >> >> S
Re: VM system name
. Architect Executive > Digital Asset & Other Industry Solutions IBM Z & LinuxONE > - - - - - - - - - - > E-Mail: sipp...@sg.ibm.com > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send email > to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390data=02%7C01%7CBerry.vanSleeuwen%40atos.net%7Cf995c6394e9c4d45af5608d8384e7348%7C33440fc6b7c7412cbb730e70b0198d5a%7C0%7C1%7C637321256889665657sdata=FPZOXYm9oMfEdjoL8%2BHIaQ7rJcvC96nhA4EYxME5hY4%3Dreserved=0 > > This e-mail and the documents attached are confidential and intended solely > for the addressee; it may also be privileged. If you receive this e-mail in > error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, Atos’ liability cannot be triggered for > the message content. Although the sender endeavours to maintain a computer > virus-free network, the sender does not warrant that this transmission is > virus-free and will not be liable for any damages resulting from any virus > transmitted. On all offers and agreements under which Atos Nederland B.V. > supplies goods and/or services of whatever nature, the Terms of Delivery from > Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be > promptly submitted to you on your request. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send email > to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390data=02%7C01%7CBerry.vanSleeuwen%40atos.net%7Cf995c6394e9c4d45af5608d8384e7348%7C33440fc6b7c7412cbb730e70b0198d5a%7C0%7C1%7C637321256889665657sdata=FPZOXYm9oMfEdjoL8%2BHIaQ7rJcvC96nhA4EYxME5hY4%3Dreserved=0 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send email > to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390data=02%7C01%7CBerry.vanSleeuwen%40atos.net%7Cf995c6394e9c4d45af5608d8384e7348%7C33440fc6b7c7412cbb730e70b0198d5a%7C0%7C1%7C637321256889665657sdata=FPZOXYm9oMfEdjoL8%2BHIaQ7rJcvC96nhA4EYxME5hY4%3Dreserved=0 > > This e-mail and the documents attached are confidential and intended solely > for the addressee; it may also be privileged. If you receive this e-mail in > error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, Atos’ liability cannot be triggered for > the message content. Although the sender endeavours to maintain a computer > virus-free network, the sender does not warrant that this transmission is > virus-free and will not be liable for any damages resulting from any virus > transmitted. On all offers and agreements under which Atos Nederland B.V. > supplies goods and/or services of whatever nature, the Terms of Delivery from > Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be > promptly submitted to you on your request. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: VM system name
uestion mark to be > "z17?" (for example). Loop, repeat. Some of these suggestions could be easily mistaken as actual model names (e.g. "z15+" or "z16") while they are not - a very delicate matter. Plus, for various reasons, the unidentified ID might turn out not to be a later generation model, in which case we would give false info. So we should probably resort to "unknown", or maybe "UFC" (Unidentified Flying CEC) - just kidding. -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: VM system name
On 2020-07-18 20:58, Mark Post wrote:
> On 7/17/20 12:18 PM, Marcy Cortes wrote:
>> Late to the game, but I would probably make a .service file that did
>> something like
>>
>> ExecStart= echo $(/sbin/vmcp q userid | awk '{print $3}') > /etc/vmsysname
>>
>> and then anything could look at the file.
>>
>> An LGR'd guest would be wrong, but I don't think you use that.
>
> Would people find it helpful if a command is introduced to the
> s390-tools package that will return one or more of the following data
> points:
> 1. z/VM or KVM Guest name
> 2. z/VM Host name
> 3. KVM Host name
> 4. LPAR name
> 5. CEC name
OK, here's a shot at what this could look like:
$ zhypinfo --help
Usage: zhypinfo [OPTIONS]
-j/--json Export raw data in Json format
-l/--layers Print number of layers
-L/--levels Print number of virtualization levels
$ zhypinfo
NoLayer Lvl TypeName IFL CP
--
4 z/VM_Guest 1guest myguest2 0
3 z/VM_Resource_Pool 1poolpooltest 3 0
2 z/VM1hypervisor myzvm 8 0
1 LPAR0guest S38LP43 10 0
0 CEC 0hostS38 34 10
$ zhypinfo -l
5
$ zhypinfo -L
2
$ zhypinfo --json
... # dumps out _all_ info of qclib in json format
So this would be a rather simplistic approach, but hopefully addressing most
needs - bear with me:
- the format in the table should be comprehensible
- it should also be easy enough to parse in other scripts
- the fields 'Lvl' and 'Type' would help to make things addressable:
'No' won't help much with scripting as one cannot know e.g. whether there's a
z/VM resource pool present or not (which would shift the index accordingly).
However, since there is only one guest/hypervisor/pool/etc. in each
virtualization level, the combination of these two fields makes things
adressable.
- I was actually wondering if column 'No' should be dropped...
- the json export is the catchall: It would export _all_ data made available by
qclib, which is substantially more than printed in the table. There's tools
like 'jq' that allow to filter out any given piece of data from json, so it
would serve to fulfill any needs of folks who want to process the data and
stop short of programming against qclib proper.
- The CPU counts (IFL and CP) do not distinguish between shared and dedicated.
It is easy to get carried away with what data we provide. I'd refer folks with
exotic requests to the '--json' option, and only think about expanding the
format in case some piece of info is very popular/frequently requested.
All feedback appreciated!
Mit freundlichen Grüßen / Kind regards
Stefan Raspl
Linux on Z & Virtualization Development
---
IBM Deutschland
Schoenaicher Str. 220
71032 Boeblingen
Phone: +49-7031-16-2177
E-Mail: stefan.ra...@de.ibm.com
---
IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats:
Gregor Pillen
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB
243294
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: VM system name
Hi David, Thanks for your considerations, greatly appreciated! On 2020-07-30 02:28, David Boyes wrote: > On 7/22/20, 9:29 AM, "Linux on 390 Port on behalf of Stefan Raspl" > wrote: >> Would people find it helpful if a command is introduced to the >> s390-tools package that will return one or more of the following data >> points: >> 1. z/VM or KVM Guest name >> 2. z/VM Host name >> 3. KVM Host name >> 4. LPAR name >> 5. CEC name > > Some thoughts on this, in no particular order: > > 1. The output from qc_test you showed should require a --verbose option. Most > uses for this data will programmatic, so something like 1 line per level, > space delimited would be most useful. If you can parse it easily with classic > Bourne shell, you got it right. > > Example: > > ./qc_test without --verbose produces: > > 0 guest 5 1 GUEST43 off 0 0 undef undef 1 1 0 0 0 1 0 1 undef undef > 1 pool 4 3 pooltest 0 0 0 0 1 64467763 undef undef undef > 2 hyper 3 2 "MY_ZVM" undef "z/VM 6.3.0" 500 1 0 3 0 3 1 0 1 2 undef undef > 3 lpar > 4 cec . > . > etc on stdout. The --verbose version can show all the human friendly labels > and formatting. qc_test is not externalized so far and primarily intended as a debugging aid/demo for the actual library. I was sort of testing the waters to see if providing its format would have some merit - but it likely does not. However, I like your idea, and I believe we could provide a more elaborate output that could be used for scripting and further processing! Not so sure about the format, though - the one above is hard to read, and I would claim it might be prone to produce errors on all parties involved - e.g. whenever we add further fields. Something that correlates the values to a field name is preferable - maybe something like JSON could do the job here! > 2. Most uses of this will be most interested in the layer closest to them, eg > starting at the VM guest level and going outward (the reverse of how your > example is formatted). Yup, I agree. > 3. It might be useful to say "I'm not interested in data that is more than X > levels from me" to reduce processing, ie something like --maxlevel from me>. ./qc_test --maxlevel 2 from the example above would return data > from guest, pool and hypervisor, but drop anything beyond. One could always do that by post-processing the output. Also, this would need some semantics: We should likely count virtalization layers, not levels. Because e.g. z/VM can or can not have a Resource Pool defined. As one does not know in advance, it should not be counted. But then again, that makes it a bit more complicated. I'd likely push that out as a future item. > 4. An option to return only the number of virtualization levels present would > be helpful to set loops, eg ./qc_test --levels in your example returns 5 as > its only output. Something like that is already available in the underlying library, although it counts levels/layers, not _virtualization_ levels. Makes sense to keep it that way. > 5. a flag to test for multiple CPU types or not would be helpful (you can get > what they are from the whole output, just a 1/0 flag to indicate the presence > of a mixed LPAR), in a LPAR with both IFLs and standard engines ./qc_test > --mixed would return 1 so you need to go look at the full data to find out > the whole picture, or you could return the counts of processors of each type > after the 1/0 if you felt like it. There's a field like that available, but not in every layer. However, this is really easy to derive from the output, so not sure if I'd want to add it... > 6. (nit) in the verbose output, provide a way to provide a format string > option, eg: > > ./qc_test --verbose --format="30:8.3" > > qc_capability [S ] : 552.000 > qc_secondary_capability [S ] : 552.000 > qc_capacity_adjustment_indication [S ]: 100.000 > qc_capacity_change_reason [S ]: 0.000 Uh, yeah, well, another 'future' I would say. > I'd find a utility like that very useful indeed. Thanks for your response, I'm pretty sure I'll come up with something in the not too distant future! -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Au
Re: VM system name
On 2020-07-25 01:46, Alan Altmark wrote: > In some sense you are creating a UUID for the container. > > CPCname.LPAR.System_id.userid.system_id.userid > > Having to handle second level systems and LPAR only, too. > > Perhaps prefixed with nn, where nn tells you how many levels of VM. 01 > means native LPAR. You mean just like /proc/sysinfo does? Yeah, there's a though, but Mark suggested to have have support for paramters to select the output, e.g. '--lpar' to get the LPAR name - but that won't work easily or in a non-ugly name for 2nd level guests. I'll be looking some more into this...maybe we'll inlude 2nd level and cut off only after that - to be seen... -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: VM system name
On 2020-07-24 17:29, Mark Post wrote: > On 7/24/20 3:26 AM, Stefan Raspl wrote: >> Hi Mark, > > Hi, Stefan, > >> The problem with that is that you will get into trouble as soon as you >> consider >> 2nd-level installs where you have multiple guests and hypervisors to >> display/query. We'd need multiple switches to address the different levels of >> guests, and things get ugly pretty fast. Any ideas how to address that? > > I believe you're over-thinking this. Based on the origin of this thead > and the responses to it, I would argue that people aren't interested in > all that. They want to know: > - What's *my* name > - What's the name of the host system > - What LPAR am I running in > - What CPC am I running on > > That's why I said this: >>> I can't say for sure >>> if many people would be interested in finding out they're running 6 >>> layers of virtualization deep and what each of those is. If someone does >>> want that, they should speak up. > -snip- > >> I would argue that if you want to script, what you really want is a >> front-end in >> qclib that can be accessed by scripts. Yes, querying qclib is certainly more >> complicated than interacting with a command line tool like you layed out >> above, >> but unless we come up with a smart way for that tool's cmdline switches, it >> will >> likely not do what you need. > > I would say that the limited program I'm suggesting would do exactly > what people want. Remember, I proposed this as a way for people to not > have to write all sorts of REXX execs and bash scripts to figure out > this small set of information. There may be others out there that are > interested in much more than this, but so far they haven't said so (on > this mailing list anyway). Fair enough. So in case we detect 2nd or higher level guests, we could indiate so and limit output to e.g. CEC and LPAR only - is that how you would handle things? -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: VM system name
Hi Mark, On 2020-07-23 21:16, Mark Post wrote: > On 7/23/20 3:17 AM, Stefan Raspl wrote: >> I could imagine writing a simplistic tool >> that displays all virtualization levels down to the CEC, with the potential >> to >> extend it in the future. > > Hi, Stefan, > > I was thinking more in terms of command line switches that determine > what should be returned. For example: > cmdname --guest Would return the name of my running guest > cmdname --hostWould return the name of the z/VM or KVM host. > cmdname --lparWould return the name of the LPAR. > cmdname --cec Would return the name of the CEC. Or CPC, since I think > that's the current IBM name. The problem with that is that you will get into trouble as soon as you consider 2nd-level installs where you have multiple guests and hypervisors to display/query. We'd need multiple switches to address the different levels of guests, and things get ugly pretty fast. Any ideas how to address that? > And possibly, something like: > cmdname --all Which would return the names of all these things, possible > as "name=value" pairs. > There's already the systemd-detect-virt command to tell you what > hypervisor is in use, so that wouldn't be needed. I can't say for sure > if many people would be interested in finding out they're running 6 > layers of virtualization deep and what each of those is. If someone does > want that, they should speak up. > > I believe something like this would allow for easy scripting by system > administrators. Of course, others may have differing opinions. I would argue that if you want to script, what you really want is a front-end in qclib that can be accessed by scripts. Yes, querying qclib is certainly more complicated than interacting with a command line tool like you layed out above, but unless we come up with a smart way for that tool's cmdline switches, it will likely not do what you need. Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: VM system name
On 2020-07-22 19:27, Mark Post wrote: > On 7/22/20 9:28 AM, Stefan Raspl wrote: > >> qclib, which was linked to earlier in the thread, offers all the info. > > Indeed, which is what I would have based anything I wrote on. > > -snip- >> It seems like there's a use for most of the data provided by qc_test, >> everybody >> seems to find interest in some data. So I'm contemplating externalization of >> qc_test output in some shape or form - but is that really consumable? > > Not as is, today. > >> However, externalizing it is easier said than done, since some of the fields >> require a lot of explanation, especially in virtualized environments. >> So: Would the output below help, or should we rather have a separate tool >> with a >> more comprehensible format? > > The latter. Please let me know if you're going to proceed with this. If > so, I won't start working on the limited command I already talked about. Give me 1-2 weeks to sort out some details. This shouldn't be a lot of effort, but rather to get the format right. I could imagine writing a simplistic tool that displays all virtualization levels down to the CEC, with the potential to extend it in the future. -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Gregor Pillen Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: VM system name
qc_ifl_dispatch_limithard [ V]: 0
qc_ifl_capped_capacity [ V]: 0
qc_ziip_dispatch_type [ V]:
qc_ziip_dispatch_limithard [ V]:
qc_ziip_capped_capacity [ V]:
qc_has_multiple_cpu_types [ V]: 0
--
Mit freundlichen Grüßen / Kind regards
Stefan Raspl
Linux on Z & Virtualization Development
---
IBM Deutschland
Schoenaicher Str. 220
71032 Boeblingen
Phone: +49-7031-16-2177
E-Mail: stefan.ra...@de.ibm.com
---
IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats:
Gregor Pillen
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB
243294
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
IBM z15 DEFLATE Support
Want to try out support for the new DEFLATE support in IBM z15 and experience the performance boost first hand *right now*...? Check https://linux-on-z.blogspot.com/2019/10/howto-exploiting-hardware-compression.html -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Matthias Hartmann Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
IBM z15 KVM Support
For a first look at what our fine new hardware has in store for KVM, check out http://kvmonz.blogspot.com/2019/10/kvm-on-ibm-z15-features.html - more to come! Also, we *did* ramp up our effort with the Linux on Z blog significantly. So check out https://linux-on-z.blogspot.com/, and specifically our new subsection on containers at https://linux-on-z.blogspot.com/p/containers-on-ibm-z.html -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Matthias Hartmann Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Migration from z/VM to KVM
Hi Jim, We have no documentation dedicated to migrations from z/VM to KVM. Are there any particular issues that we could address in z/VM to keep the customer happy, or is the decision to move to KVM already a done deal? So, if you want to get started, it is important to verify that KVM provides all pieces required in the current z/VM based installation. There is a wide variety of solutions in the open source ecosystem to address customers' needs, but it is also easy to get lost in the selection - KVM in the Linux distributions is a starting point, but usually no integrated solution with all bells and whistles. You can find our official documentation on KVM at https://www.ibm.com/support/knowledgecenter/en/linuxonibm/liaaf/lnz_r_kvm_base.html. Specifically, check the "KVM Virtual Server Management" document. Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Matthias Hartmann Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 On 28.08.19 17:28, Jim Elliott wrote: > I have a customer considering a migration from z/VM to KVM (ClefOS) on > their LinuxONE machines. They are a university with no Z skills (we provide > those) so they are looking at simplifying their environment as they grow. > Is there documentation / tips anywhere on how to do such a migration? > > Jim Elliott > Senior Consultant - GlassHouse Systems Inc. > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Linux on Z Blog
We're ramping up our efforts for the Linux on Z blog, located at https://linux-on-z.blogspot.com/ We plan to comment on latest upstream contributions, Linux distro releases, and publish the odd article on specific features like containters/Docker, SMC, et al. Note: KVM will continue to run a separate blog at http://kvmonz.blogspot.com/ Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Matthias Hartmann Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
New Performance Whitepaper on SMC-D
A new whitepaper "Performance Evaluation of SMC-D with SAP Banking on IBM Z", highlighting the benefits of SMC-D technology in a z/OS and Linux on Z (using SLES 12 SP4) deployment, is out. Get it at http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102792 Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Matthias Hartmann Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
KVM on Z: QEMU v3.1 Released
QEMU v2.11 is out! See http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html for a list of highlights for KVM on z. Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Matthias Hartmann Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on Z - Knowledge Series: Use virt-install for KVM Guest Installations
Tired of fiddling with guest XML files and virtual DJing with ISO images? Then our latest entry in our Knowledge Series might come handy! Plus it also offers access to further Linux distributions on IBM Z! Read more on how virt-install can help at http://kvmonz.blogspot.com/2018/07/knowledge-use-virt-install-for-kvm.html Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Alpine Linux 3.8 rc2 on z/VM and KVM
On 13.06.2018 05:58, Tuan M. Hoang wrote: > Hello, > > The Alpine Linux Project has released the the 2nd release candidate for > its 3.8 stable series with support for z/VM and KVM. > > For the installation guide and more information, please visit : > https://wiki.alpinelinux.org/wiki/S390x. > > For running Alpine in Docker, please visit : > https://wiki.alpinelinux.org/wiki/S390x/Docker. > > If you have any questions or comments, please reply to this thread or > send an email to this list, or alpine-de...@lists.alpinelinux.org, or > reach out at IRC channels #alpine-linux or #alpine-devel at Freenode, or > use #alpinelinux on Twitter. Very cool! We have added a page to our blog, illustrating how to get started based on the ISO image: http://kvmonz.blogspot.com/p/getting-started-alpine-linux.html Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on Z - Knowledge Series: Managing KVM on IBM Z with oVirt
See kvmonz.blogspot.com/2018/05/knowledge-series-managing-kvm-on-ibm-z.html for a new entry in our "knowledge" series, providing step-by-step instructions on how to include IBM Z hosts in an oVirt data center. Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on Z - Getting Started: RHEL 7.5 Instructions added
Instructions for RHEL7.5 were added to our "Getting Started with KVM on Z" series. See the actual page at http://kvmonz.blogspot.com/2018/05/getting-started-rhel-75-instructions.html Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on Z: QEMU v2.12 released
See http://kvmonz.blogspot.co.uk/2018/05/qemu-v212-released.html for an update on what's new for IBM Z in QEMU v2.12. Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
RHEL 7.5 with support for KVM on z released
Red Hat Enterprise Linux 7.5 is out - see the following link for details regarding KVM on z support: http://kvmonz.blogspot.com/2018/04/rhel-75-with-support-for-kvm-on-z.html Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on Z: SLES12 SP3 Updates
SLES12SP3, released late last year, received a couple of mostly performance and security-related updates in support of IBM z14 and LinuxONE through the maintenance web updates. See http://kvmonz.blogspot.co.uk/2018/03/sles12-sp3-updates.html for further details. Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
RHEL 7.5 Beta supports KVM on Z
See http://kvmonz.blogspot.com/2018/02/rhel-75-beta-supports-kvm-on-z.html Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z & Virtualization Development --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on Z: QEMU 2.11 Released
QEMU v2.11 is out! See http://kvmonz.blogspot.de/2017/12/qemu-v211-released.html for a list of highlights for KVM on z. Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM & Linux on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on z Systems Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Kvm on Z: Ubuntu Cloud Images
Instructions on how to setup one of the Ubuntu Cloud Images were added to the "Getting Started with KVM on Z" series. See the entry page at http://kvmonz.blogspot.com/p/getting-started-with-kvm-on-z.html Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM & Linux on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on z Systems Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on Z: Getting Started with Ubuntu
Instructions for Ubuntu 16.04 to 17.10 were added to the "Getting Started with KVM on Z" series. See the entry page at http://kvmonz.blogspot.de/p/getting-started-with-kvm-on-z.html Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM & Linux on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on z Systems Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on Z: Getting started
There's a new series of articles coming up providing step-by-step instructions on how to run KVM on Z. See http://kvmonz.blogspot.de/p/getting-started-with-kvm-on-z.html for an overview, and http://kvmonz.blogspot.de/p/getting-started.html for a first article covering SLES12 SP3. Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM & Linux on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on z Systems Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on z14 features
KVM on z will naturally support the forthcoming z14 machine. See http://kvmonz.blogspot.co.uk/2017/07/kvm-on-z-z14-features.html for a detailed list of features that will exploit the latest addition to the IBM Z family. Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM & Linux on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on z Systems Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on z Knowledge Series: Disk Performance Hints & Tips
See http://kvmonz.blogspot.com/p/knowledge.html for the second entry in our "knowledge" series about disk performance hints & tips with KVM on z. The first entry providing guidance on configuration is available at http://kvmonz.blogspot.co.uk/p/blog-page_7.html Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on System z Dev & Service --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM for IBM z Systems v1.1.2 released today
KVM for IBM z Systems v1.1.2 is released today - see http://kvmonz.blogspot.com/2016/10/kvm-for-ibm-z-systems-v112-released.html for a list of highlights from a pure KVM perspective. Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on System z Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Linux kernel 4.8 released
Linux kernel 4.8 is out, see http://kvmonz.blogspot.co.uk/2016/10/linux-kernel-48-release.html for a list of highlights in respect to KVM on z. Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on System z Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on z: QEMU v2.7 released
QEMU v2.7 is out! See kvmonz.blogspot.com/2016/09/qemu-v27-released.html for a list of highlights for KVM on z. Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on System z Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: 2016-06-10 Linux on z Systems - qclib 1.2.0 package drop on developerWorks
On 06/10/2016 10:32 AM, Gerhard Hiller wrote: > Please refer to > http://www.ibm.com/developerworks/linux/linux390/whatsnew.html > for qclib 1.2.0 package (qclib for 'Query Capacity library') > * end of message See http://kvmonz.blogspot.de/2016/06/qclib-v120-released.html for details on new features in support of KVM on z. -- Mit freundlichen Grüßen / Kind regards Stefan Raspl KVM on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on System z Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
KVM on z Blog
I started blogging about the KVM on z development activities at http://kvmonz.blogspot.co.uk/. So if you want to be up to date on what is happening in the open source communities with relevance to KVM on z (which is certainly a good indication of what features to expect in future Linux distro releases), then this might be of interest to you. Kind regards, Stefan Raspl KVM on z Systems IBM Systems & Technology Group, Systems Software Development / SW Linux on System z Dev & Service --- IBM Deutschland Schoenaicher Str. 220 71032 Boeblingen Phone: +49-7031-16-2177 E-Mail: stefan.ra...@de.ibm.com --- IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
