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 15:07:21 -0500 Message-ID: <20091222200721.GC31761@phenom.dumpdata.com> References: <20091222191426.GC31242@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Michael D Labriola Cc: xen-devel@lists.xensource.com, ?????? , Ian.Campbell@citrix.com, xen-devel-bounces@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > A also can't seem to pass devices through (unless I'm doing it wrong). > When trying to pass my soundcard do the domU, it appears to be > appropriately hidden from dom0 via xen-pciback.hide kernel param > (/var/log/messages says 'pciback 0000:00:1b.0: seizing device') but when I > try to start my domU with iommu=soft and pci=["00:1b.0"] I get a dozen or You are doing it right. > so "BUG: scheduling while atomic" messages w/ call traces. My domU > eventually starts up ok, but lspci returns with no output. Hmm, I wonder if this patch is in your tree: commit 1aa61698354ca0582b07eb865e0432a13b459f11 Author: Ian Campbell Date: Thu Dec 17 14:08:25 2009 +0000 xen: fix hang on suspend. and causing this (or maybe the pciback driver is the culprit and the above patch exposes a bug?). Try reverting that patch and seeing what happens. I the meantime let me compile a new Dom0 with the above mentioned commit and see if I get the failure too.