From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: I cannot get any message from domU by console / pv_ops domU kernel crashes with xen_create_contiguous_region failed Date: Tue, 22 Dec 2009 09:32:03 -0500 Message-ID: <20091222143203.GA2785@phenom.dumpdata.com> References: <20091221183000.GO16033@reaktio.net> <20091222084214.GR16033@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20091222084214.GR16033@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com, ?????? List-Id: xen-devel@lists.xenproject.org > > (early) [ 0.000000] Kernel panic - not syncing: > > <3>xen_create_contiguous_region failed This implies you did not have enough DMA32 memory in the hypervisor for the guest. Meaning at least 64MB. When you launch your guest, run 'xm info' and see what you have. The latest from xen-unstable tries to have _at least_ that amount of memory available for the guest. Here is what I see: free_memory : 3938 node_to_cpu : node0:0-1 node_to_memory : node0:3938 node_to_dma32_mem : node0:3514 The node_to_dma32_mem needs to have at least 64. Or you can add 'iommu=off' to your boot arguments that should disable the SWIOTLB. You only need SWIOTLB if you do PCI pass through.