Re: [Xen-devel] I cannot get any message from domU by console / pv_ops domU kernel crashes with xen_create_contiguous_region failed

[Michael D Labriola <mlabriol@xxxxxxxx>]

> 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 
more 
> > > > 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 
in 
> > my 
> > > > domU config that needs to change?
> > > 
> > > console=hvc0
> > > 
> > > Otherwise the output is going to 'tty0' which is your VNC 
framebuffer.
> > 
> > I already had that in the 'extra' section of my domUs config file... 
is 
> > that not the right place for it?
> 
> That is the right place. You are sure you don't have another 'extra'or 
'root'
> 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 
domU.

-Mike

Attachment: messages
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel