[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.
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
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
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:
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
** 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
--- 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
