From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Use of xend-pci-permissive.sxp Date: Mon, 21 Dec 2009 12:04:03 -0500 Message-ID: <20091221170403.GE17700@phenom.dumpdata.com> References: 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: David Gonzalez Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Dec 18, 2009 at 04:48:01AM -0500, David Gonzalez wrote: > Hi xen developers, > > You're the best, Xen Rulez. Although I've subscribed to xen's mailing list I > post and I never get an answer, I hope this time this mail went somewhere. > > I've PV'ed CentOS 5.3 i386 as DomU with CentOS 5.4 x86_64 as Dom0. I have I was under the impression that 5.4 (2.6.18-128.el5) did not have the pciback module. Either way, I would recommend you use the pv-ops [1] and try that one. If you still have trouble with the pv-ops, please include more details: dmesg of both DomU and Dom0, lspci -vvv of both domains, and boot your Xen with guest_loglvl=all ... snip .. > Anyway, The only way to solve this issue was to use xend-pci-permissive.sxp > adding: ..snip.. > (unconstrained_dev_ids > ('e159:0001') # OpenVox A1200P > ) I am reading this as, it fixed the warning about the device not being safe, but did not help with your Dom0 hang? [1]. http://wiki.xensource.com/xenwiki/XenParavirtOps