All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: vfb console inhibiting Xen console?
Date: Fri, 03 Jul 2009 10:14:53 -0700	[thread overview]
Message-ID: <4A4E3C8D.3060501@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0907031227470.11588@kaball-desktop>

On 07/03/09 04:38, Stefano Stabellini wrote:
> Yes, you can.
> Check that /local/domain/$DOMID/serial/0/tty exists and contains the
> tty path in dom0.
> If you specify vfb in your config file then qemu provides the console
> backend and creates that node on xenstore that specify the tty device
> path.
> I just tried to start a pv guest with a vfb and didn't have any problem
> connecting to the console, maybe you don't have an updated qemu tree?
>   

I can never tell whether the versions match up or not.  I did a clean
build and it appeared to do some git pulling.

But I just did an specific "git pull" in ioemu-remote, and the behaviour
has changed.  Now with a vfb it seems to hang forever: the domain
appears to boot, but there's no console output, and it doesn't seem to
have brought up its network.  There's nothing on the vfb either. 
/local/domain/$DOMID/serial/0/tty has /dev/pts/1, which the xenconsole
process has open.

If I remove the vfb in the config, it works as expected.

    J

  reply	other threads:[~2009-07-03 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 22:22 vfb console inhibiting Xen console? Jeremy Fitzhardinge
2009-07-03  7:36 ` Gerd Hoffmann
2009-07-03  8:46 ` Ian Campbell
2009-07-03 11:38 ` Stefano Stabellini
2009-07-03 17:14   ` Jeremy Fitzhardinge [this message]
2009-07-06  9:58     ` Stefano Stabellini

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=4A4E3C8D.3060501@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.