[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] RE: [PATCH] fixed serial console support


  • To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, "Williamson, Alex (Linux Kernel Dev)" <alex.williamson@xxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Tue, 6 Dec 2005 08:25:24 -0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 06 Dec 2005 16:25:40 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcX3KOtt8t9CKs6XSUOFei7rfWjGXgDWGn4A
  • Thread-topic: [Xen-ia64-devel] RE: [PATCH] fixed serial console support

> From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx] 
> Subject: Re: [Xen-ia64-devel] RE: [PATCH] fixed serial console support
> 
> > > >  Also,
> > > > will this eliminate the need to have CONFIG_VT=y
> > > > on dom0 and CONFIG_VT=n on domU?
> > >
> > >    I don't know, I never really understood the problem there.  Xen
> > > provides a ttyS (serial) console device to dom0  and a 
> tty (vt) device
> > > to non-dom0 domains.  I would therefore have expected domU to need
> > > CONFIG_VT=y.  What was the problem with CONFIG_VT on domU before?
> > > Thanks,
> >
> > Tristan or Matt, do you know?
> No idea, but I can try to investigate if you want.

FYI, I tried setting CONFIG_VT=y for domU.  No console output
after "Freeing unused kernel memory" and then dom0 crashed!

Dan

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.