[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] dom0/pvh: Dom0 PVH with PCI passthrough support status

On Mon, Nov 05, 2018 at 12:57 PM, Wei Liu wrote:
On Mon, Nov 05, 2018 at 11:58:09AM +0200, Alexandru Vasile wrote:
(XEN) event_channel.c:319:d0v1 EVTCHNOP failure: domain 1, error -22
(XEN) event_channel.c:319:d0v3 EVTCHNOP failure: domain 1, error -22
Do you perhaps have more than one xenstored / xenconsoled running?

The processes listed by 'ps -aux | grep xen' immediately after dom0 boots are oxenstored, xenconsoled and xenwatchdogd.

I did start 'xencommons ' from my install folder due to xl showing the name of Dom0 as '(null)' and also because of a difference in output error from xl when creating a HVM DomU with passthrough (the output is captured in files xl_output_clean[0] and xl_output_xencommons[1]).

(XEN) Assertion 'fdom != p2m->domain' failed at p2m.c:504
You can work around this with:

From 9437054299c1d360eb4fedd065d51965e560fc0c Mon Sep 17 00:00:00 2001
From: Wei Liu <wei.liu2@xxxxxxxxxx>
Date: Fri, 2 Nov 2018 14:55:04 +0000

 xen/arch/x86/mm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xen/arch/x86/mm.c b/xen/arch/x86/mm.c
index f043e43ac7..9c154783e4 100644
--- a/xen/arch/x86/mm.c
+++ b/xen/arch/x86/mm.c
@@ -4443,7 +4443,7 @@ int arch_acquire_resource(struct domain *d, unsigned int type,
     switch ( type )
-#ifdef CONFIG_HVM
+#if 0
     case XENMEM_resource_ioreq_server:
         ioservid_t ioservid = id;
-- 2.11.0

Thank you, after applying this patch dom0 no longer freezes or reboots, therefore I was able to capture all the error messages from the 'xl create' command [0] [1].

Another problem that I discovered while investigating pci passthrough is that Dom0 randomly freezes. I encountered this problem multiple times, but on two occasions I was able to capture the output form the serial console: the problem will reset dom0 after 5 seconds [2] or will cause the system to never reset [3].

I later applied the patch from [4] as seeing this is a recurrent problem, but I could not reproduce the bug even when stressing the system.

Thanks, Alex.

[0] see 'xl_output_clean' from attached files - the output of xl create HVM Dom0 before manually starting xencommon

[1] see 'xl_output_xencommons' from attached files - the output of xl create HVM Dom0 after manually starting xencommon

[2] see 'dom0_freeze' form attached files - reset after freeze

[3] see 'dom0_freeze_loop' form attached files - a reset is not performed after freeze

[4] https://lists.xenproject.org/archives/html/xen-devel/2016-01/msg02753.html

Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.

Attachment: dom0_freeze
Description: Text document

Attachment: dom0_freeze_loop
Description: Text document

Attachment: xl_output_clean
Description: Text document

Attachment: xl_output_xencommons
Description: Text document

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.