From: noarchwastaken <noarchwastaken@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] libvirt-7.5.0_1: [Regression] Unable to start any virtual machines created prior to the update
Date: Sun, 11 Jul 2021 11:43:25 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31904@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
New issue by noarchwastaken on void-packages repository
https://github.com/void-linux/void-packages/issues/31904
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.12.14_1 x86_64 GenuineIntel uptodate rFFFFFFFFFF
* package:
libvirt-7.5.0_1
Was working fine in libvirt-7.4.0_1
### Expected behavior
`virsh start <domain>` should start the corresponding virtual machine.
### Actual behavior
```
$ doas virsh start voidlinux
error: Failed to start domain 'voidlinux'
error: internal error: cannot load AppArmor profile 'libvirt-aa58ea57-f6d7-48b1-b727-de97f4c508af'
```
### Steps to reproduce the behavior
1. Enable AppArmor
2. Create a VM using libvirt<=7.4.0_1
3. Update libvirt to 7.5.0_1, reboot to reload apparmor profiles
4. Try to launch the VM again
next reply other threads:[~2021-07-11 9:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 9:43 noarchwastaken [this message]
2021-07-22 5:52 ` libvirt-7.5.0_1: [Regression] Unable to create or start VMs noarchwastaken
2021-07-22 5:52 ` noarchwastaken
2021-07-22 5:57 ` noarchwastaken
2021-07-22 5:58 ` noarchwastaken
2021-07-22 5:58 ` noarchwastaken
2021-07-22 9:54 ` paper42
2021-07-24 13:03 ` noarchwastaken
2021-07-24 13:05 ` noarchwastaken
2021-07-24 18:23 ` FollieHiyuki
2021-08-18 23:02 ` sernkut
2021-08-19 10:51 ` sernkut
2022-04-07 13:40 ` noarchwastaken
2022-07-07 2:13 ` github-actions
2022-07-07 23:02 ` noarchwastaken
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-31904@inbox.vuxu.org \
--to=noarchwastaken@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).