Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Z vm fixes #916

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Z vm fixes #916

wants to merge 4 commits into from

Conversation

azouhr
Copy link
Contributor

@azouhr azouhr commented Feb 8, 2023

This is the changes, that I currently use to operate the z/VM worker on OBS. In order to simplify the debugging and logging of the worker, I also added a function ".log" that allows to specify a certain log level and to print out the affected file and function within that file.

.log 5 "This is a notice"

The severity levels are used from https://en.wikipedia.org/wiki/Syslog#Severity_level
The default severity level is set to 4, to keep the default output clean.

Feel free to do changes if needed.

Berthold Gunreben and others added 4 commits February 8, 2023 13:27
Each log message created with .log will contain a severity, the
originating file and the function where the log had been called. The
function is called with:
.log <severity> <message>
where severity is defined in
https://en.wikipedia.org/wiki/Syslog#Severity_level
In z/VM, the system representation of the SWAP device is just a four
digit hex number. However, the build script expects a partition within
a disk instead. This change rewrites the device number into a block
device when needed.
The IUCV console connection is not always responding fast enough,
therefore loop until the connection works.

This change also removes the creation of a specific initrd, since the
default has all needed modules available.
@adrianschroeter
Copy link
Member

This way of logging is conflicting with our current idea of debug logging, we do not want to increase or decrease all kinds of logs, but we want to enable logging for specific areas. We want to enable logging by a specified area (eg. zvm, kvm or all vm handling) and enable debug logging only for these kind of operations.

Could you adapt your zvm worker fixes just to check for BUILD_VERBOSE_VM=true for example?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants