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: Michael D Labriola <mlabriol@xxxxxxxx>
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: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Tue, 22 Dec 2009 14:09:42 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, "xen-devel-bounces@xxxxxxxxxxxxxxxxxxx" <xen-devel-bounces@xxxxxxxxxxxxxxxxxxx>, ?????? <peb1611@xxxxxxxxx>
Delivery-date: Tue, 22 Dec 2009 06:10:01 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <OF39738892.7B443120-ON85257694.00475FF8-85257694.0047D8CA@xxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <OF39738892.7B443120-ON85257694.00475FF8-85257694.0047D8CA@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2009-12-22 at 13:04 +0000, Michael D Labriola wrote:
> How do I make sure xen_create_contiguous_region is privileged 
> enough? 

By adding a PCI device to your domU config -- that's obviously just a
workaround though and in general you do not want domUs to be able to tie
down arbitrary amounts of "special" memory.

Later on:
> When you said to enable PCI passthrough, did you mean by setting 
> CONFIG_XEN_PCIDEV_BACKEND_PASS as apposed to the newer 

This is independent of CONFIG_XEN_PCIDEV_BACKEND_*.


Xen-devel mailing list

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