From owner-freebsd-questions@FreeBSD.ORG Tue Oct 25 02:23:24 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42C1116A41F for ; Tue, 25 Oct 2005 02:23:24 +0000 (GMT) (envelope-from e.schuele@computer.org) Received: from rwcrmhc12.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id E537743D46 for ; Tue, 25 Oct 2005 02:23:23 +0000 (GMT) (envelope-from e.schuele@computer.org) Received: from [192.168.214.215] (c-24-1-232-64.hsd1.tx.comcast.net[24.1.232.64]) by comcast.net (rwcrmhc13) with ESMTP id <2005102502220301500r8khee>; Tue, 25 Oct 2005 02:22:03 +0000 Message-ID: <435D96C8.2040407@computer.org> Date: Mon, 24 Oct 2005 21:22:00 -0500 From: Eric Schuele User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050930) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dick hoogendijk References: <20051024190847.5b856678.dick@nagual.st> In-Reply-To: <20051024190847.5b856678.dick@nagual.st> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: fbsdq Subject: Re: /dev/kqemu X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2005 02:23:24 -0000 dick hoogendijk wrote: > Earlier I wrote: > > > Strangely enough starting qemu [file] I get a warning > "could not open '/dev/kqemu' - QEMU accellaration layer not activated" > I kldloaded kqemu.ko and in /dev I see the device (666). > > > I have found out that only the FIRST user that starts QEMU on ht > computer gets support for kqemu accellaration. Even if he closes hiw > qemu session and logs off, another NEW user can start QEMU but gets NO > accel support. The above error is put on the screen. > Hmmm... after reading this post... I wondered if that was the problem I was experiencing. But I retested on RELENG_6, and I am not seeing this behavior. Is that your 4.x or your 5.x machine behaving that way? > So, how come the device kqemu is not freed after I close the qemu > session and keeps being "busy"? > > Is there a solution I have overlooked to overcome this problem? > > I looked into the user and kqemu online dox but can't find a thing > relating to my problem. Who has some clues? > -- Regards, Eric