On 07/12/2021 11:28, Ján Tomko wrote:
On a Monday in 2021, lejeczek wrote:
Hi guys.
Have you seen something like this below?
...
internal error: The string resource has invalid
characters in its value
internal error: The provided value contains invalid
characters: Solarstorm SFN5162F SFP+ Server Adapter
This error message was only present in libvirt v7.9.0.
Since v7.10.0
libvirt should ignore non-printable characters.
https://bugzilla.redhat.com/show_bug.cgi?id=2022589
Jano
Would that "bug" be a reason why my libvirtd fails?
I have libvirtd.service started and see that in the logs,
then suffices I do:
-> $ virsh list --all
(having no VMs started)
I next thing in the logs is:
...
internal error: The provided value contains invalid
characters: Solarstorm SFN5162F SFP+ Server Adapter
internal error: The string resource has invalid characters
in its value
Stopping Virtualization daemon...
libvirtd.service: Deactivated successfully.
Stopped Virtualization daemon.
I'm on Centos 9 with libvirt-daemon-7.9.0-1.el9.x86_64.
With .service failed I still can start a VM.
-> $ systemctl status -l libvirtd.service
○ libvirtd.service - Virtualization daemon
Loaded: loaded
(/usr/lib/systemd/system/libvirtd.service; disabled; vendor
preset: dis>
Active: inactive (dead) since Mon 2021-12-13 09:32:04
GMT; 5min ago
TriggeredBy: ○ libvirtd-tcp.socket
● libvirtd-ro.socket
● libvirtd-admin.socket
● libvirtd.socket
○ libvirtd-tls.socket
Is it that these versions and/or Centos 9 have introduced
new (different defaults) ways to use/mange 'libvirtd', with
.socket and no .service?
many thanks, L
