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 14:50:40 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, ?????? <peb1611@xxxxxxxxx>, Ian.Campbell@xxxxxxxxxx, xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Dec 2009 11:51:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091222191426.GC31242@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
> On Tue, Dec 22, 2009 at 01:47:54PM -0500, Michael D Labriola wrote:
> > > > Well, this seems to work for the first case (domU not needing PCI 
> > > > passthrough).  Haven't tried passing anything through yet.  On a 
> > > > general pv_ops domU note, though... I no longer get a login prompt 

> > after 
> > > > watching the system boot with 'xm create -c'.  Is there something 
> > my 
> > > > domU config that needs to change?
> > > 
> > > console=hvc0
> > > 
> > > Otherwise the output is going to 'tty0' which is your VNC 
> > 
> > I already had that in the 'extra' section of my domUs config file... 
> > that not the right place for it?
> That is the right place. You are sure you don't have another 'extra'or 
> later on in the config file that would overwrite the first one?

Yeah.  Last line of my config is:

extra="earlyprintk=xen iommu=soft console=hvc0"

No login for me.  Just one of those days, I guess.

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 
so "BUG: scheduling while atomic" messages w/ call traces.  My domU 
eventually starts up ok, but lspci returns with no output.

I've attached /var/log/messages from my dom0 after attempting to create my 


Attachment: messages
Description: Binary data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>