From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: vfb console inhibiting Xen console? Date: Fri, 03 Jul 2009 10:14:53 -0700 Message-ID: <4A4E3C8D.3060501@goop.org> References: <4A4D331A.5080105@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: Ian Campbell , Xen-devel , Ian Jackson , Keir Fraser List-Id: xen-devel@lists.xenproject.org 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