Re: [PATCH 2/2] xen/virtio: Avoid use of the dom0 backend in dom0

On 6/21/23 19:58, Oleksandr Tyshchenko wrote: > On 21.06.23 16:12, Petr Pavlu wrote: >> When attempting to run Xen on a QEMU/KVM virtual machine with virtio >> devices (all x86_64), dom0 tries to establish a grant for itself which >> eventually results in a hang durin

[PATCH 1/2] xen/virtio: Fix NULL deref when a bridge of PCI root bus has no parent

4c9 ("xen/virtio: Handle PCI devices which Host controller is described in DT") Signed-off-by: Petr Pavlu --- drivers/xen/grant-dma-ops.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/xen/grant-dma-ops.c b/drivers/xen/grant-dma-ops.c index 9784a77fa3c9..76f6f26265a3 100644 -

[PATCH 2/2] xen/virtio: Avoid use of the dom0 backend in dom0

in ret_from_fork () at ../arch/x86/entry/entry_64.S:308 #24 0x in ?? () Fix the problem by preventing xen_grant_init_backend_domid() from setting dom0 as a backend when running in dom0. Fixes: 035e3a4321f7 ("xen/virtio: Optimize the setup of "xen-grant-dma" devi

[PATCH 0/2] Fix Linux dom0 boot on a QEMU/KVM virtual machine

Fix two problems that prevent booting Linux dom0 on a QEMU/KVM virtual machine, which is sometimes useful for testing purposes. Petr Pavlu (2): xen/virtio: Fix NULL deref when a bridge of PCI root bus has no parent xen/virtio: Avoid use of the dom0 backend in dom0 drivers/xen/grant-dma

[PATCH] xen/xenbus: Avoid a lockdep warning when adding a watch

nse_mutex is spurious. Avoid it and the warning by changing the ordering in xs_suspend(), first acquire xs_response_mutex and then xs_watch_rwsem. Reverse also the unlocking order in xs_suspend_cancel() for consistency, but keep xs_resume() as is because it needs to have xs_watch_rwsem unlocked only after