From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Hoffmann <kraxel@suse.de>
Subject: two xenfb bugs for sale ;)
Date: Wed, 07 Feb 2007 12:42:17 +0100
Message-ID: <45C9BB19.708@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Markus Armbruster <armbru@redhat.com>, Xen devel list <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

  Hi,

Wondered where some xen-vncfb processes handing around on my machine
came from.  After some Investigation I've figured that xen-vncfb never
ever exits if you boot a virtual machine with a virtual framebuffer
configured, but boot a kernel without framebuffer support.  It sits
waiting for the frontend device come up and doesn't exit when the domain
goes away.

Oh, and it also doesn't unmap the framebuffer memory once the frontend
enteres the "Closing" state.

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>