From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Libvirt 8.0 don't work?
Date: Mon, 21 Feb 2022 08:34:54 +0100 [thread overview]
Message-ID: <20220221073454.-5QpcXDMTitMyAB2S7CcNJEVRsxDWOLNUfYaK90xlp0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35208@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Closed issue by Naia-love on void-packages repository
https://github.com/void-linux/void-packages/issues/35208
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
``Void 5.15.11_1 x86_64 AuthenticAMD notuptodate rrrrmmnDFFFFFFFFFF``
* package:
libvirt-8.0.0_1
### Expected behavior
To run after upgrading it
### Actual behavior
after upgrading it and restarting pc, libvirtd service start on crash, when trying to run ``libvirtd`` directly it give me this error:
```
❯ libvirtd
2022-01-23 19:49:57.635+0000: 12789: info : libvirt version: 8.0.0
2022-01-23 19:49:57.635+0000: 12789: info : hostname: home
2022-01-23 19:49:57.635+0000: 12789: error : virModuleLoadFile:53 : 内部エラー: Failed to load module '/usr/lib64/libvirt/connection-driver/libvirt_driver_network.so': /usr/lib/libvirt.so.0: version `LIBVIRT_PRIVATE_7.10.0' not found (required by /usr/lib64/libvirt/connection-driver/libvirt_driver_network.so)
```
which imply that said module didn't get updated to use libvirt 8? not idea how that can happen
### Steps to reproduce the behavior
I just upgrade libvirt from 7.10 to 8
(edit: I confirm that downgrading to libvirt 7.10 make it work again)
next prev parent reply other threads:[~2022-02-21 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 20:19 [ISSUE] " Naia-love
2022-01-24 18:35 ` paper42
2022-02-21 7:34 ` paper42 [this message]
2022-03-04 19:56 ` abenson
2022-03-04 19:57 ` Naia-love
2022-03-04 20:17 ` zenny
2022-03-04 21:09 ` zenny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220221073454.-5QpcXDMTitMyAB2S7CcNJEVRsxDWOLNUfYaK90xlp0@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).