virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: Oops
Date: Thu, 11 Jan 2007 09:41:45 -0800	[thread overview]
Message-ID: <20070111174145.GR10475@sequoia.sous-sol.org> (raw)
In-Reply-To: <45A65B7C.6050503@suse.de>

* Gerd Hoffmann (kraxel@suse.de) wrote:
> Chris Wright wrote:
> > 
> > This should not be needed, the console should be xcv0, completely decoupled
> > from serial.
> 
> You've made the whole thing even more complicated with the last commit.
> Enabling VT is possible now.  Good.  No way around that.  The kernel
> hangs now though.  Fix is attached:  better don't try to setup the vga
> console for xen guests which don't have the hardware.

I'm not really sure what, the last commit I did was lhype?

> Next problem:  The default for xencons (tty) conflicts with the virtual
> consoles.  I'm tempted to drop the complete xencons=foobar stuff into
> the waste basket and leave in xencons=xvc only.  And maybe xencons=off.
>  xencons=tty conflicts with the VT subsystem.  xencons=ttyS conflicts
> with the serial driver.  Disabling the offending drivers is completely
> out of question for a kernel which is supposed to work both native and
> paravirtualized.

Yes, all of tty ttyS xencons goes away.  Here the default is xvc.

> One more issue:  What should be the default console?  Right now it is
> the vt console (using the dummy device).  Not very good.  vgacon doesn't
> work.  fbcon doesn't work either (yet).  So you'll end up with a
> non-functional console by default.  Bummer.

default console should be xvc in the guest.

thanks,
-chris

  reply	other threads:[~2007-01-11 17:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09 13:34 Oops Gerd Hoffmann
2007-01-09 22:46 ` Oops Jeremy Fitzhardinge
2007-01-10  8:16   ` Oops Gerd Hoffmann
2007-01-10 10:29     ` Oops Gerd Hoffmann
2007-01-10 13:05       ` Oops Gerd Hoffmann
2007-01-10 20:07         ` Oops Jeremy Fitzhardinge
2007-01-10 23:52         ` Oops Chris Wright
2007-01-10 23:53           ` Oops Jeremy Fitzhardinge
2007-01-11  8:13             ` Oops Gerd Hoffmann
2007-01-11  8:11           ` Oops Gerd Hoffmann
2007-01-11 15:45           ` Oops Gerd Hoffmann
2007-01-11 17:41             ` Chris Wright [this message]
2007-01-12  8:24               ` Oops Gerd Hoffmann
2007-01-12  2:53             ` Oops Rusty Russell
2007-01-12  4:23               ` Oops Chris Wright
2007-01-12  8:31                 ` Oops Gerd Hoffmann
2007-01-10 20:06       ` Oops Jeremy Fitzhardinge
2007-01-10 21:44       ` Oops Jeremy Fitzhardinge
2007-01-11 14:12         ` Oops Gerd Hoffmann
2007-01-11 19:56           ` Oops Jeremy Fitzhardinge
2007-01-10 19:38     ` Oops Jeremy Fitzhardinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070111174145.GR10475@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=kraxel@suse.de \
    --cc=virtualization@lists.osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).