no, thanks, actually since this fix patches virt-aa-helper itself, just creating a new vm after the upgrade should have sufficed. No reboot should have been needed. However trying to start a pre-existing vm that previously failed would not work, as the policy needs to be re-generated.
Looking at your error message, the filename doesn't seem to match what we expect in the patch. The patch uses "domain-$(domain-name)", whereas the log says it was trying to use var/lib/libvirt/qemu/channel/target/centos7.0.org.qemu.guest_agent.0.
Still perplexing that it did work for me. Perhaps adding "/var/lib/libvirt/qemu/channel/target/${domain-name}**" to the whitelist in the same place in the same patch would fix everyone and still be safe.
Hi,
no, thanks, actually since this fix patches virt-aa-helper itself, just creating a new vm after the upgrade should have sufficed. No reboot should have been needed. However trying to start a pre-existing vm that previously failed would not work, as the policy needs to be re-generated.
Looking at your error message, the filename doesn't seem to match what we expect in the patch. The patch uses "domain- $(domain- name)", whereas the log says it was trying to use var/lib/ libvirt/ qemu/channel/ target/ centos7. 0.org.qemu. guest_agent. 0.
Still perplexing that it did work for me. Perhaps adding "/var/lib/ libvirt/ qemu/channel/ target/ ${domain- name}** " to the whitelist in the same place in the same patch would fix everyone and still be safe.