*** This bug is a duplicate of bug 1707400 ***
https://bugs.launchpad.net/bugs/1707400
** This bug is no longer a duplicate of bug 1594902
Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit
** This bug has been marked a duplicate of bug 1707400
libvirt-bin doesn't
*** This bug is a duplicate of bug 1594902 ***
https://bugs.launchpad.net/bugs/1594902
** This bug has been marked a duplicate of bug 1594902
Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit
--
You received this bug notification because you are a member of Ubuntu
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/138646
@lathiat,
when I take a 14.04 system,
grep netlink /etc/apparmor.d/usr.sbin.libvirtd
returns nothing; then do-release-upgrade -d, agree to the reboot, and
grep netlink /etc/apparmor.d/usr.sbin.libvirtd
returns
network netlink,
Is it possible that you did not reboot after the release upgra
Hi,
I've opened another bug/issue report, including patch, for the issue of
"libvirt-bin not start",
please see #1571209 for detail,
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1571209
it seems to the problem I've ran into, I'm wondering if it could fix your
problem,
please give help
also hit this issue with a clean setup, but not sure how to reproduce,
since I've setup multiple server with the same "script",
but only one server hit the problem, and problem still after applying the
workaround mention in #34
here's how I setup the services,
1. apt-get install qemu-kvm
2. apt-
Because this bug report has quite a bit of information and history has
taught me that not keeping information from different reporters separate
can greatly complicate matters.
Since I'm asking for apport-uploaded information, it would be best that
it not be mixed with information from another syst
Also note that there are already several different directions into which
this bug has been taken. A crucial question is whether step 3 in
@mahmoh's recipe is really needed:
3) /etc/default/libvirt-bin: ' libvirtd_opts="-d -l" '
If not then there are different bugs at work.
--
You received th
@Serge why a new bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd from creating a socket
To manage notifications about this bug go to:
https://bu
Thomas,
would you mind filing a new bug using apport? In particular I'd like to
see any local changes to your /etc/libvirt/libvirtd.conf and
/etc/default/libvirt-bin and see the upgrade log if possible. If you
can reproduce at will in clean vms by taking particular steps, that
would be great. B
The bug is STILL present and breaks libvirt-bin upon upgrade from 14.04
to 16.04
Performing the steps from comment 34 worked around the breakage.
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465/comments/34
** Changed in: libvirt (Ubuntu)
Status: Expired => Confirmed
** Tags
I had this issue today after upgrading from trusty->wily (yes I know not
technically supported). Notably I was running the lts-wily kernel on
trusty, and I had a cached profile.
So I am wondering if this combination results in the cache needing
regeneration but not being triggered for regeneratio
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/138646
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd from creating a socket
To mana
@mahmoh - ping (question in comment #30).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd from creating a socket
To manage notifications about this
Problemas con mi kvm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd from creating a socket
To manage notifications about this bug go to:
https://bug
Thanks @mahmoh,
that's interesting. Perhaps we should add a comment in the shipped
/etc/default/libvirt-bin?
Why had you added the -l? Is there a published recipe you were
following, and should that be updated?
** Changed in: libvirt (Ubuntu)
Status: Expired => Confirmed
--
You recei
Hi Serge,
I hit this problem on a stock install of 14.04, only installed MAAS and
libvirt-bin + dist-upgrade. When I ran your debug commands (@22)
libvirt-bin failed to crash but when I start the process it still fails,
here's the only log output I see below:
/var/log/libvirt/libvirtd.log:
Sep 1
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/138646
Quoting Ray Wang (ray.w...@canonical.com):
> this is bug is reproducible.
>
> Install 14.04
> dist-upgrade
to 14.10?
> install libvirtd-bin
>
> I also hit this bug..
I'm still unable to reproduce. To be sure, are you running upstart
and a mostly stock Ubuntu system?
--
You received this bug
this is bug is reproducible.
Install 14.04
dist-upgrade
install libvirtd-bin
I also hit this bug..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd f
** Attachment added: "DENIED.log"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465/+attachment/4412678/+files/DENIED.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
I can reproduce the bug. Attaching the requested information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd from creating a socket
To manage notifi
** Attachment added: "libvirt.debug"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465/+attachment/4412677/+files/libvirt.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
T
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd from creating a socket
To mana
I cannot reproduce this following the above recipe.
Please add the information requested in comment #19,
set log_level=1 in /etc/libvirt/libvirtd.log
stop libvirt-bin
rm /var/log/libvirt/libvirtd.log
run "sudo /usr/sbin/libvirtd 2>&1 | tee libvirt.debug" until it (I assume)
breaks.
Attach libvir
I upgraded from 14.04 to 14.10 installed libvirt and got the same error:
>From syslog I have pre aa-audit and then with aa-audit it seems to aa-
audit clears the bug with audit removed it continues to work.
Post audit log:
Apr 14 20:19:50 dnshost11 kernel: [ 1284.666816] audit_printk_skb: 36 cal
This is very reproducible
- install 14.04
- do-release-upgrade
- restart
- apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils
- /etc/init.d/libvirt-bin start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
@nbensa,
I'm sorry, Idon't know what aa-audir is.
@tchen,
have you been able to verify whether behavior changed at all (per
comment #18)? If you are still having this issue in uptodate 15.04,
please
set log_level=1 in /etc/libvirt/libvirtd.log
stop libvirt-bin
rm /var/log/libvirt/libvirtd.log
Having the same issue. Can't create the libvirt.sock when trying to
start up libvirt.
By using "aa-audit /usr/sbin/libvirtd", I get a lot of chatter in dmesg:
[67418.135152] audit: type=1400 audit(1426857324.439:5864):
apparmor="AUDIT" operation="file_perm" profile="/usr/sbin/libvirtd"
name="/run
After 'aa-audir -r /usr/sbin/libvirtd' and a reboot, libvirtd works as
expected (and with no chat in dmesg).
Anyway, I still offer my help in debugging this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Hello. I'm having the same problem. I just upgraded to 14.10 (from
14.04).
'service libvirt-bin start' fails to start (althrough it gives a pid).
/var/log/libvirt/libvirtd.log
2015-03-10 03:22:13.546+: 10223: info : libvirt version: 1.2.8, package:
1.2.8-0ubuntu11.4
2015-03-10 03:22:13.546
Thanks - as you have no more issues i'll mark the bug 'invalid' meaning
cannot currently be reproduced. If it happens again please re-open the
bug.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is my libvirtd apparmor profile, however I have no issues any more
at this time.
** Attachment added: "usr.sbin.libvirtd"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465/+attachment/4328837/+files/usr.sbin.libvirtd
--
You received this bug notification because you are a m
Same problem here: I have upgraded vom 14.04 to 14.10.
Putting apparmor in audit mode
aa-audit /usr/sbin/libvirtd
enables me to start libvirt. I use Upstart:
$ ps -eaf|grep [u]pstart
root 541 1 0 18:57 ?00:00:00 upstart-udev-bridge --daemon
root 1155 1 0 18:57 ?
@Jeff and @Smartypants,
are you both running systemd in 14.10, as the original bug reported was?
Or are you running upstart?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor pr
I had the same issue upgrading from 14.04 to 14.10. Purged/reinstallled
libvirt-bin as in Message3, but with no effect. Installed apparmor-
utils, and put libvirt into audit mode per first message, and libvirt
works again. Thanks Christian for the workaround.
error from /var/log/libvirt/libvir
After aa-audit
[49992.022321] audit: type=1400 audit(1420285233.962:152): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/sbin/libvirtd"
pid=25593 comm="apparmor_parser"
[50004.285006] audit: type=1400 audit(1420285246.230:153): apparmor="AUDIT"
operation="open" pr
I can reproduce this bug
** Changed in: libvirt (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd from cre
Now I have my virbr0 interface and libvirt-bin starts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd from creating a socket
To manage notifications
[49578.653469] audit: type=1400 audit(1420284820.446:128): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/sbin/libvirtd"
pid=24625 comm="apparmor_parser"
[49578.677733] audit: type=1400 audit(1420284820.470:129): apparmor="STATUS"
operation="profile_replace" profil
Thanks you for the information - that's quite frustrating. It seems quite
clear (between this bug and some others) that there is a hard-to-trigger
bug in the libvirt apparmor policy, but I've not yet spotted any obvious
trigger.
I'm marking this bug invalid meaning "cannot be reproduced", but if
I did not have libvirt-bin installed before the upgrade, I installed it
afterwards.
I renamed /etc/apparmor.d/usr.sbin.libvirtd , purged libvirt-bin and
reinstalled it.
to my surprise the diff between /etc/apparmor.d/usr.sbin.libvirtd and the
renamed file is zero.
For some reason I am no long
Thanks for reporting this bug. The default libvirt profile does provide
'network netlink', so I'm not sure why you are having this problem.
Could you please attach the /etc/apparmor.d/usr.sbin.libvirtd from a
fresly updated host that is having this issue?
** Changed in: libvirt (Ubuntu)
Impor
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents libvirtd from creating a socket
To manage noti
45 matches
Mail list logo
