From: Iurii Mykhalskyi <iurii.mykhals...@globallogic.com> Looks like that from 4.6 version, Xen didn't allow irq forwarding into DomU domains - in our setup we forward list of them, so we need to changed the policy.
Signed-off-by: Iurii Mykhalskyi <iurii.mykhals...@globallogic.com> --- tools/flask/policy/policy/modules/xen/xen.te | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/flask/policy/policy/modules/xen/xen.te b/tools/flask/policy/policy/modules/xen/xen.te index 5e94ee3..b3eaa15 100644 --- a/tools/flask/policy/policy/modules/xen/xen.te +++ b/tools/flask/policy/policy/modules/xen/xen.te @@ -116,6 +116,7 @@ admin_device(dom0_t, device_t) admin_device(dom0_t, irq_t) admin_device(dom0_t, ioport_t) admin_device(dom0_t, iomem_t) +admin_device(domU_t, irq_t); domain_comms(dom0_t, dom0_t) -- 2.8.2 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel