[Bug 1680386] Re: virt-aa-helper to learn about VF devspec paths
[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/1680386 Title: virt-aa-helper to learn about VF devspec paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1680386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680386] Re: virt-aa-helper to learn about VF devspec paths
Due to the fallback code present and working neither IBM (for ppc64) nor anyone else found the time/need to work on this. While clearing old cases let us reflect that properly by marking it as incomplete. ** Changed in: libvirt (Ubuntu) Status: New => Incomplete ** Changed in: libvirt (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680386 Title: virt-aa-helper to learn about VF devspec paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1680386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680386] Re: virt-aa-helper to learn about VF devspec paths
There are two ways to allow qemu to access something. 1. globally through the abstraction in /etc7apparmor.d/abstractions/libvirt-qemu That is for paths ALL qemu/geusts are supposed to use like /dev/kvm 2. per guest files generated based on the XML description in /etc/apparmor.d/libvirt/libvirt-.files If you need paths like /sys/bus/pci/devices/0009:03:00.0/devspec to be accessible you should consider if you can derive the path from the XML and then let virt-aa-helper write a rule for it so that the guest can do so. Finally later in the guest lifecycle further rules will be added via the labeling calls in the security code. E.g. if you add a device libvirt calls a set label function and this will add the new ruls (like for hotplug). For the latter see virAppArmorSecurityDriver in src/security/security_apparmor.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680386 Title: virt-aa-helper to learn about VF devspec paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1680386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680386] Re: virt-aa-helper to learn about VF devspec paths
thanks, will you also look at the related changes to virt-aa-helper in lbivirt once accepted? In any way ping me once it got into qemu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680386 Title: virt-aa-helper to learn about VF devspec paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1680386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680386] Re: virt-aa-helper to learn about VF devspec paths
Hi,
in this cae guest message are not important.
Also I already said that it is non fatal - so yes it works, still it is wrong.
Either fix or remove the code whatever is more appropriate.
Please check the code that I referred to in qemu.
hw/ppc/spapr_pci.c:775
774 /* Construct and read from host device tree the loc-code */
775 path = g_strdup_printf("/proc/device-tree%s/ibm,loc-code", buf);
776 g_free(buf);
I'm rather convinced there should be an extra "/" in there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680386
Title:
virt-aa-helper to learn about VF devspec paths
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1680386/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680386] Re: virt-aa-helper to learn about VF devspec paths
** Tags removed: targetmilestone-inin1704 ** Tags added: targetmilestone-inin1710 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680386 Title: virt-aa-helper to learn about VF devspec paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1680386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680386] Re: virt-aa-helper to learn about VF devspec paths
--- Comment From lagar...@br.ibm.com 2017-04-13 21:09 EDT--- Please, reverse mirror LP1680386 (virt-aa-helper to learn about VF devspec paths). ** Tags added: architecture-ppc64le bugnameltc-153459 severity-high targetmilestone-inin1704 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680386 Title: virt-aa-helper to learn about VF devspec paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1680386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
