This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] I cannot get any message from domU by console / pv_ops d

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] I cannot get any message from domU by console / pv_ops domU kernel crashes with xen_create_contiguous_region failed
From: Michael D Labriola <mlabriol@xxxxxxxx>
Date: Tue, 22 Dec 2009 11:44:23 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, ?????? <peb1611@xxxxxxxxx>, Ian.Campbell@xxxxxxxxxx, xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Dec 2009 08:44:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091222154010.GB5181@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> Maybe Xen 3.4.2 logic is much different than 4.0 when it comes to 
> exchanging MFNs
> and Ian's is right. Under 4.0 it I've no trouble exchanging the MFNs
> even without
> any PCI devices being passed in.
> Can you try this patch to help narrow down the problem:
> diff --git a/arch/x86/xen/pci-swiotlb.c b/arch/x86/xen/pci-swiotlb.c
> index ecdbfe2..37fd0e3 100644
> --- a/arch/x86/xen/pci-swiotlb.c
> +++ b/arch/x86/xen/pci-swiotlb.c
> @@ -960,7 +960,7 @@ xen_swiotlb_fixup(void *buf, size_t size, 
> unsigned long nslabs)
>              dma_bits);
>        } while (rc && dma_bits++ < max_dma_bits);
>        if (rc)
> -         panic(KERN_ERR "xen_create_contiguous_region failed\n");
> +         panic(KERN_ERR "xen_create_contiguous_region failed: rc: 
%d\n", rc);
>        i += slabs;
>     } while(i < nslabs);
> And also ensure that your command line for Xen has: console=com1,vga
> guest_loglvl=all

Made that change and tried again.  rc was -12.  Do you need the whole 
dump?  I'm not really sure how to capture it...

> And tell me what environemtn you are using? Is the hypervisor a 64-bit
> while dom0 is 32bit or 64bit? Is DomU 32bit or 64bit?

This particular test is on a Dell Precision M4400 w/ 4GB of RAM. 
Everything is 32-bit.  Not using HVM.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>