I’m sorry. A great deal of email on my Mac disappeared last summer and recently
reappeared. I’ m going back and trying to respond to old emails. I don’t know
what happened. I installed the beta version on MacOSX Big Sur last summer and
I’m guessing that caused email to disappear and when Apple
On 10/3/20 8:10 PM, Alan Ackerman wrote:
> I think it's rude of you to post a question to a public forum and then tell
> me I have no say because I'm retired.
It's been over two months, Alan. Have you been holding on to this that
whole time?
I participate in this mailing list for a variety of
I said:
Yes! I spent a fair amount of time writing EXECs to figure these things out
when I worked for Bank of America. I put the results on a web page that listed
all our VM systems. I’m retired so I don’t need it any more.
Mark said:
OK, that's one (sorry, but retirees who won't use the
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
> 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
n 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, Cornel
> 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 fee
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?
>>>
>>> $
10:14
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: VM system name
>
> Caution! External email. Do not open attachments or click links, unless this
> email comes from a known sender and you know the content is safe.
>
> What about a JSON output option?
>
>
> Ori
:14
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VM system name
Caution! External email. Do not open attachments or click links, unless this
email comes from a known sender and you know the content is safe.
What about a JSON output option?
Original message
From: "van Sle
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
What about a JSON output option?
Original message
From: "van Sleeuwen, Berry"
Date: 8/4/20 18:04 (GMT+10:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] VM system name
I think the underscore would be required. If the output is processed by some
script i
Forum 3000 5657 EW Eindhoven
-Original Message-
From: Linux on 390 Port On Behalf Of Timothy Sipples
Sent: Tuesday, 4 August 2020 07:57
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VM system name
Caution! External email. Do not open attachments or click links, unless this
email comes from
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
>
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
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
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
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.
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
>
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.
Regards,
Alan Altmark
IBM
> On Jul
On 7/24/20 5:33 PM, Stefan Raspl wrote:
> 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?
I might need a diagram to make sure I understand what you're saying, but
it sounds
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
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
Mark Post wrote:
>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 --host Would return the name of the z/VM or KVM host.
>cmdname --lpar
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
+whatever ( and we are on SuSE 15 as a bonus)
OK, that's one (sorry, but retirees who won't use the tool don't help the
business case). Anyone else?
Mark Post
--
For LINUX-390 subscribe / signoff / archive access
> people would be interested in finding out they're running 6 layers of
virtualization deep
Like having a partition with zVM, with a zVM second level, with a Linux
inside, running KVM, with a Linux on the KVM running a Docker container,
and a JVM inside the container, trying to benchmark Bcrypt
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
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
On 7/22/20 4:44 PM, Alan Ackerman wrote:
> As far as I know they are running Red Hat.
>
> Why does that matter?
Because I work for SUSE, and any tools I write would be distributed by
SUSE in the s390-tools package. I doubt very much Red Hat would pick it
up for their distribution. But, you never
As far as I know they are running Red Hat.
Why does that matter?
Alan Ackerman
alan.ackerma...@gmail.com
On Jul 20, 2020, at 12:16 PM, Mark Post wrote:
On 7/20/20 1:09 PM, Stewart, Lee wrote:
> +1
OK, that's one (sorry, but retirees who won't use the tool don't help
the business case).
On 7/22/20 4:37 PM, Alan Ackerman wrote:
> Humpf! I think my opinion still counts. I may never use it, but I think Bank
> of America probably will.
Are they running SUSE Linux Enterprise Server?
Mark Post
--
For LINUX-390
Humpf! I think my opinion still counts. I may never use it, but I think Bank of
America probably will.
Alan Ackerman
alan.ackerma...@gmail.com
On Jul 20, 2020, at 12:16 PM, Mark Post wrote:
On 7/20/20 1:09 PM, Stewart, Lee wrote:
> +1
OK, that's one (sorry, but retirees who won't use the
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
On 2020-07-18 22:12, Alan Ackerman wrote:
> Yes! I spent a fair amount of time writing EXECs to figure these things out
> when I worked for Bank of America. I put the results on a web page that
> listed all our VM systems. I’m retired so I don’t need it any more.
>
> Sent from my iPhone
>
>
f Stewart, Lee
Sent: Monday, July 20, 2020 5:57 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [EXT] Re: VM system name
[Actual Sender is owner-linux-...@vm.marist.edu]
I wish I was a retiree.
And +1 each from the other guys doing zLinux here...
Lee Stewa
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VM system name
On 7/20/20 1:09 PM, Stewart, Lee wrote:
> +1
OK, that's one (sorry, but retirees who won't use the tool don't help the
business case). Anyone else?
Mark Post
--
For LINUX-
+2
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
Sent: Monday, July 20, 2020 12:16 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] VM system name
On 7/20/20 1:09 PM, Stewart, Lee wrote:
> +1
OK, that's one (sorry, but retirees who won't use the tool do
-Original Message-
From: Linux on 390 Port On Behalf Of Stewart, Lee
Sent: Monday, July 20, 2020 5:57 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [EXT] Re: VM system name
[Actual Sender is owner-linux-...@vm.marist.edu]
I wish I was a retiree.
And +1 each from the other guys doing zLinux here
Subject: [EXT] Re: VM system name
[Actual Sender is owner-linux-...@vm.marist.edu]
I wish I was a retiree.
And +1 each from the other guys doing zLinux here...
Lee Stewart ● VM System Support ● Visa ● Phone: 6(750)4601 - +1-303-389-4601 ●
lstew...@visa.com
-Original Message-
From
+1
Lee Stewart ● VM System Support ● Visa ● Phone: 6(750)4601 - +1-303-389-4601 ●
lstew...@visa.com
-Original Message-
From: Linux on 390 Port On Behalf Of Alan Ackerman
Sent: Saturday, July 18, 2020 2:13 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VM system name
Yes! I spent a fair
On 7/20/20 1:09 PM, Stewart, Lee wrote:
> +1
OK, that's one (sorry, but retirees who won't use the tool don't help
the business case). Anyone else?
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
Yes! I spent a fair amount of time writing EXECs to figure these things out
when I worked for Bank of America. I put the results on a web page that listed
all our VM systems. I’m retired so I don’t need it any more.
Sent from my iPhone
On Jul 18, 2020, at 11:59 AM, Mark Post wrote:
On
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
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.
Marcy
On Wednesday, 07/08/2020 at 04:47 GMT, Ronald van der Laan
wrote:
> STore HYpervisor Information returns system name and ssi name of the top
3
> levels of hypervisors.
Indeed, but arch/s390/kernel/sysinfo.c doesn't use it. That's where the
information you see in /proc/sysinfo comes from.
y Software Inc.
Main: (650) 964-8867
Main: (877) 964-8867
r...@velocitysoftware.com <mailto:r...@velocitysoftware.com>
> On Jul 8, 2020, at 11:23 AM, Tully, Phil (CORP)
wrote:
>
> Rich,
> That is the virtual machine name, not the VM system name.
Rich,
That is the virtual machine name, not the VM system name.
Regards, Phil Tully
Chief Architect-z/VM & z/Linux
phil.tu...@adp.com
cell: 973-202-7427
1-800 377-0237,,5252697#
On 7/8/20, 12:16 PM, "Linux on 390 Port on behalf of Rich Smrcina"
wrote:
WARNING: Do n
When I look at /proc/sysinfo, I can see the LPAR name but I don’t see the VM
system name. Is there a place that the VM system name would be shown from
linux?
LPAR Number: 2
LPAR Characteristics: Shared
LPAR Name:PLB2
LPAR Adjustment: 390
LPAR CPUs Total: 32
LPAR
00 Name.
>>
>> Rich Smrcina
>> Sr. Systems Engineer
>>
>> Velocity Software Inc.
>> Main: (650) 964-8867
>> Main: (877) 964-8867
>> r...@velocitysoftware.com <mailto:r...@velocitysoftware.com>
>>
>>
>> > On Jul 8, 2020, at
When I look at /proc/sysinfo, I can see the LPAR name but I don’t see
> the VM system name. Is there a place that the VM system name would be
> shown from linux?
> >
> > LPAR Number: 2
> > LPAR Characteristics: Shared
> > LPAR Name:PLB2
> > L
R name but I don’t see
> the VM
> > system name. Is there a place that the VM system name would be shown
> from
> > linux?
> >
> > LPAR Number: 2
> > LPAR Characteristics: Shared
> > LPAR Name:PLB2
> > LPAR Adjustment: 390
&
On Wednesday, 07/08/2020 at 04:12 GMT, "Tully, Phil (CORP)"
wrote:
> When I look at /proc/sysinfo, I can see the LPAR name but I don’t see
the VM
> system name. Is there a place that the VM system name would be shown
from
> linux?
>
> LPAR Number: 2
>
lto:r...@velocitysoftware.com>
> <mailto:r...@velocitysoftware.com <mailto:r...@velocitysoftware.com>>
>
>
>> On Jul 8, 2020, at 11:12 AM, Tully, Phil (CORP) wrote:
>>
>> When I look at /proc/sysinfo, I can see the LPAR name but I don’t
LPAR name but I don’t see the VM
> system name. Is there a place that the VM system name would be shown from
> linux?
>
> LPAR Number: 2
> LPAR Characteristics: Shared
> LPAR Name:PLB2
> LPAR Adjustment: 390
> LPAR CPUs Total: 32
> LP
55 matches
Mail list logo
