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

cpi.service sets values in KVM guest and fails #120

Closed
sharkcz opened this issue Jul 26, 2021 · 2 comments
Closed

cpi.service sets values in KVM guest and fails #120

sharkcz opened this issue Jul 26, 2021 · 2 comments

Comments

@sharkcz
Copy link
Contributor

sharkcz commented Jul 26, 2021

Seems the condition the service (https://github.com/ibm-s390-linux/s390-tools/blob/master/systemd/cpi.service.in#L14) it true even in a KVM guest, but the CPI interface isn't (fully) implemented (?) there and setting the values fail.

[root@localhost ~]# journalctl -u cpi
Jul 26 09:28:01 localhost.localdomain systemd[1]: Starting Apply Control Program Identification (CPI)...
Jul 26 09:28:01 localhost.localdomain cpictl[628]: /lib/s390-tools/cpictl: line 112: echo: write error: Operation not supported
Jul 26 09:28:01 localhost.localdomain systemd[1]: cpi.service: Succeeded.
Jul 26 09:28:01 localhost.localdomain systemd[1]: Finished Apply Control Program Identification (CPI).

Related: https://bugzilla.redhat.com/show_bug.cgi?id=1985745

@sharkcz
Copy link
Contributor Author

sharkcz commented Nov 19, 2021

ping :-)

@ghost
Copy link

ghost commented Jan 3, 2022

I would probably be best to suppress the error message in cpictl (cpi_commit), e.g.
echo 1 > "$CPI_SET" 2> /dev/null
As we will likely implement the CPI interface for KVM in the future, it's OK to enable the service in KVM guests.

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

No branches or pull requests

1 participant