Last weekend I updated two KVM hosts (x86_64) running Alpine 3.11.6 to 3.12.0.
Since upgrading libvirt service (libvirtd) is not starting correctly.
Two processes of libvirtd are spawned and interaction with libvirt (ie: virsh or remotely over TLS) doesn't work. If you run a virsh command, the command will just hang for a long time until I press ctrl+c to stop it.
If I manually kill one of the libvirtd processes, libvirt seems to start working again. I can execute virsh commands without any issues, same with remote access.
I found this other issue that may be related but I'm not really sure: 11361
The problem is not only happening at startup, I'm still investigating but even while libvirt is already running, after sometime a second process is spawned (don't know why yet) and libvirt stops working again. I need to connect to the KVM host, kill the new libvirtd process that was spawned, and operation resumes as usual.
Any ideas?
Thanks.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
This is the challenge at the moment, replicating the issue.
Tomorrow I will raise libvirt logging level to info or debug to try to catch the problem or at least to get some hints of what can be causing it and report back my findings (if any).
I don’t have any spare server to test it unless I mix libvirt from edge with the rest of packages from 3.12.
Correct me if I’m wrong but since I’m running from RAM (and lbu) I should be able to enable edge, upgrade libvirt, test, comment edge repos and just reboot to be back in the original situation. Right?
lIBVIRTD Status is crashed in alpine 3.14. I manually start stop many times and install the latest libvirtd version 9.4.0. Start stop wont start the service. Can someone help me out.
Starting virtlogd ...
Error relocating /usr/sbin/virtlogd: virIdentityGetProcessID: symbol not found
Error relocating /usr/sbin/virtlogd: virNetServerClientSetQuietEOF: symbol not found
Error relocating /usr/sbin/virtlogd: virIdentityGetGroupName: symbol not found
Error relocating /usr/sbin/virtlogd: virNetServerAddServiceUNIX: symbol not found
Error relocating /usr/sbin/virtlogd: virIdentityGetUserName: symbol not found
Error relocating /usr/sbin/virtlogd: virNetServerUpdateTlsFiles: symbol not found
Error relocating /usr/sbin/virtlogd: virSystemdGetActivation: symbol not found
Error relocating /usr/sbin/virtlogd: virTypedParamListAddInt: symbol not found
Error relocating /usr/sbin/virtlogd: virTypedParamListAddBoolean: symbol not found
Error relocating /usr/sbin/virtlogd: virDaemonForkIntoBackground: symbol not found
Error relocating /usr/sbin/virtlogd: virSystemdActivationComplete: symbol not found
Error relocating /usr/sbin/virtlogd: virFileActivateDirOverrideForProg: symbol not found
Error relocating /usr/sbin/virtlogd: virTypedParamListFree: symbol not found
Error relocating /usr/sbin/virtlogd: virPipe: symbol not found
Error relocating /usr/sbin/virtlogd: virTypedParamListAddString: symbol not found
Error relocating /usr/sbin/virtlogd: virTypedParamListAddUInt: symbol not found
Error relocating /usr/sbin/virtlogd: virSystemdActivationFree: symbol not found
Error relocating /usr/sbin/virtlogd: virDaemonUnixSocketPaths: symbol not found
Error relocating /usr/sbin/virtlogd: virTypedParamListStealParams: symbol not found
Error relocating /usr/sbin/virtlogd: virDaemonSetupLogging: symbol not found
start-stop-daemon: failed to start `/usr/sbin/virtlogd'
Failed to start virtlogd [ !! ]
ERROR: virtlogd failed to start
ERROR: cannot start libvirtd as virtlogd would not start
Any chance libvirt 6.4.0 can be backported to 3.12?
Libvirt 6.3 seems to be really broken and for me is causing a lot of issues (VM management, Vm backups, etc).
If 6.4 will not be backported to 3.12 then I will have to rollback to Alpine 3.11.6 while I wait for Alpine 3.12.1 since I can't risk to mix main and edge and cause other problems on the KVM hosts.
I experienced this issue today after upgrading my KVM box from 3.11 to 3.12. I checked its libvirt version, and the new 6.5.0 was installed during the upgrade.
The only non-standard factors I can think of is that it's an AMD Ryzen 1700 with IOMMU and NPT enabled (kernel cmdline: amd_iommu=on iommu=pt kvm_amd.npt=1) because I use it for PCI passthrough with a SAS controller.
However, this issue occurred even before starting the VM with the PCI device.
Unfortunately it's a fairly critical machine, so I had to boot it into its old Debian installation and didn't even get to try 3.12 without the IOMMU/NPT kernel options.
Will look into it and debug further as soon as I get the opportunity.
Does anybody else affected by this issue use AMD hardware and/or IOMMU?
I'm getting it on fresh installs of Alpine 3.12 on a Ryzen 2700X and 3700X, no IOMMU or any special params. I'm also getting on Intel Sandy Bridge (i5-2400).