This bug was fixed in the package libvirt - 1.3.1-1ubuntu9
---
libvirt (1.3.1-1ubuntu9) xenial; urgency=medium
* Remove the tasks limit on libvirt-bin service (LP: #1567381)
This should be un-done when it is properly fixed in the code so
that virtual machines are started in
@james-page - that is the problem cpaelzer is working on right? What
should be done with this bug? Is there another bug which this can be
dup'ed to, or should we we turn this into a bug to track his
dpdk/qemu/libvirt work?
--
You received this bug notification because you are a member of
FWIW I'm testing on Xenial with the latest libvirt packages for Ubuntu;
the generated apparmor profile .files file for my instances correctly
grants access to /var/run/openvswitch/:
"/run/openvswitch/vhu8b11d723-35" rw,
/dev/vhost-net rw,
Remaining problem is that with the default libvirt
Hi,
Could someone who can reproduce this problem try adding:
/var/run/** r,
to the file /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper
and see whether that solves the problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
Title:
qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled
To
Quoting James Page (james.p...@ubuntu.com):
> 2) vhost-user device access
>
> The configuration for the vhost-user device created in OVS will also be
> blocked by apparmor:
>
> -chardev socket,id=charnet0,path=/var/run/openvswitch/vhu5392206b-dc
> -netdev
For anyone experiencing this problem - any DENIED or COMPLAIN messages
from syslog/kern.log would be highly useful to help generate an update
to the apparmor provide for libvirt-qemu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Two observations after discussing with Hui on IRC:
1) Hugepage filesystem
Right now, the apparmor profile only allows access to:
# for access to hugepages
owner "/run/hugepages/kvm/libvirt/qemu/**" rw,
if the hugepage FS is mounted elsewhere, any hugepage access will be
blocked by
Took a look at /var/run/openvswitch:
-rw-r--r-- 1 root root 6 Dec 9 12:09 ovsdb-server.pid
srwx-- 1 root root 0 Dec 9 12:09 db.sock
srwx-- 1 root root 0 Dec 9 12:09 ovsdb-server.20518.ctl
-rw-r--r-- 1 root root 6 Dec 9 12:09 ovs-vswitchd.pid
srwx-- 1 root root 0 Dec 9 12:09
Linking to bug 1524737 - systemd behaves a bit differently with regards
to hugepages so we might want to update libvirt's apparmor rules to deal
with that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I just tried to reproduce this locally using your xml file, but all
seemed fine. So it doesn't seem like there are any problematic
filenames.
Ideally, we could stop nova from cleaning up at the failure point, and
then at failure for existance of
/usr/bin/kvm-spice
and contents of
** Description changed:
- This bug is seperate from bug
- https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532 to focus
- on the error.
+ [ENV]
+ Ubuntu 15.04
+ Linux 3.19.0-30-generic
+ libvirtd (libvirt) 1.2.12
+ QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5expubuntu9.7)
+
@Serge
"this happens to you always, or only occasionally? Always on the same host?"
- Yes, it always happen, not just me, it happened to any people who is using
Ubuntu to deploy OVS-DPDK enabled vms, it's kind of critical.
Discuss email
@sean You are correct, I am uploading the fresh libvirt xml file and
part of the nova-compute related logs.
** Attachment added: "instance_spawn_failed_log"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1513367/+attachment/4531275/+files/instance_spawn_failed_log
--
You received
xianghui if you look int he nova compute log it will contain a full copy
of the libvirt xml that it tried to boot the vm with.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
Title:
@Chuck
There is no libvirt xml file because the vm is spawned failed finally,
and the content in the bug description is the accurate error report from
nova-compute node, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you attach your libvirt xml file for the domain and your nova-
compute-logs please?
Thanks
chuck
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
Title:
qemu-system-x86_64/kvm-spice
** Tags added: dpdk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
Title:
qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled
To manage notifications about this bug go to:
Hi Chuck,
could you request whatever openstack config info we'd need to reproduce
this?
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Chuck Short (zulcss)
--
You received this bug notification because you are a
@Serge
Hello, is the logs uploaded enough for you? let me know if you need
more, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
Title:
qemu-system-x86_64/kvm-spice failed to boot a
All the outputs ar euploaded into 1513367-20151107.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
Title:
qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled
To
** Attachment added: "1513367-20151107.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1513367/+attachment/4514742/+files/1513367-20151107.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Serge
AFter use the qemu-system-x86_64 with strace, the error as below:
2015-11-06 15:55:12.681 ERROR nova.compute.manager
[req-b2e4d8e4-70d2-40b7-814c-409ae1720729 None None] Error updating resources
for node panghua-CS24-TY: internal error: Child process (LC_ALL=C
Can you show which libvirt version you are using?
Can you show the results of:
ls -l /etc/apparmor.d/libvirt
ls -l /proc /proc/self /proc/self/attr
And then the following manual test:
cd /tmp
cat > testprofile << EOF
profile i_cant_be_trusted_anymore {
/etc/ld.so.cache
Is that really the only strace output you saw?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
Title:
qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled
To manage
** Attachment added: "1513367.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1513367/+attachment/4513272/+files/1513367.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513367
I believe the 'no such file or directory' is what qemu is reporting
about some device which openstack is trying to hand it.
Can you confirm that
/dev/hugepages/libvirt/qemu
exists (ls -l /dev/hugepages/libvirt)?
Try the following on your compute node to get strace output:
mv
Actually it seems reasonably likely that your problem is with:
-smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack
Nova,version=12.0.0,serial=e87d7510-5766-e35e-8016-ebeb55d7deff,uuid=3dceb341
-643d-492a-8a47-8154da341c02,family=Virtual Machine
because the smbios has spaces in the
28 matches
Mail list logo
