From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] libvirt broken in musl due to lack of utmpx implementation in musl
Date: Wed, 25 Sep 2019 20:17:01 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14721@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]
New issue by ktm5j on void-packages repository
https://github.com/void-linux/void-packages/issues/14721
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.2.15_1 x86_64-musl GenuineIntel uptodate rF
*output of ``xuname`` (part of xtools)*
* package: libvirt - 5.7.0-r0 (assuming all versions?
*affected package(s) including the version*
### Expected behavior
After installing libvirt and configuring services, I should be able to connect to the host using virt-manager/virsh/etc and use normally
### Actual behavior
libvirt starts properly, and I can connect using virt-manager/virsh.. however once I try to create a VM I am given this error message:
```
[root@ruby ~ ]# virsh create /tmp/vm.xml
error: Failed to create domain from /tmp/vm.xml
error: internal error: child reported (status=125): Unable to get host boot time: No data available
```
### Steps to reproduce the behavior
Install libvirt under musl and try using it
I have tracked the error down to an issue with musl's lack of utmpx implementation. The error message is generated by [this if statement in libvirt](https://github.com/libvirt/libvirt/blob/3ebde403c76ee046c53ebf7b80dff7eb11e94748/src/security/security_util.c#L117)
The function is calling [virHostGetBootTime() from src/util/virhostuptime.c](https://github.com/libvirt/libvirt/blob/3ebde403c76ee046c53ebf7b80dff7eb11e94748/src/util/virhostuptime.c#L36) where the error occurs. This function is calling `getutxid()` from `utmpx.h` however the musl implementation of utmpx simply returns NULL for this and many other functions.
Has libvirt ever worked under musl? Is this happening now because of a change that was made in libvirt? Sorry if this is the wrong place to file this issue, but I would really like to get this working if possible
Thanks
next reply other threads:[~2019-09-25 18:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 18:17 voidlinux-github [this message]
2019-09-25 18:39 ` voidlinux-github
2019-10-10 20:06 ` voidlinux-github
2019-10-11 17:08 ` voidlinux-github
2019-10-11 19:46 ` voidlinux-github
2019-10-11 20:15 ` voidlinux-github
2019-10-11 20:20 ` voidlinux-github
2019-10-11 20:21 ` voidlinux-github
2019-10-11 20:39 ` voidlinux-github
2019-10-11 20:40 ` voidlinux-github
2019-10-12 7:44 ` voidlinux-github
2019-10-12 7:45 ` [ISSUE] [CLOSED] " voidlinux-github
2019-10-12 12:27 ` voidlinux-github
2019-10-14 6:36 ` voidlinux-github
2019-10-14 7:20 ` voidlinux-github
2019-10-14 8:32 ` voidlinux-github
2019-10-14 14:55 ` voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14721@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).