From owner-freebsd-emulation Tue Jan 29 2:49:57 2002 Delivered-To: freebsd-emulation@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 3304737B416 for ; Tue, 29 Jan 2002 02:49:54 -0800 (PST) Received: from laptop.6bone.nl (penguin.ripe.net [193.0.1.232]) by birch.ripe.net (8.11.6/8.11.6) with SMTP id g0TAnrW08128 for ; Tue, 29 Jan 2002 11:49:53 +0100 Received: (nullmailer pid 1617 invoked by uid 1000); Tue, 29 Jan 2002 10:49:51 -0000 Date: Tue, 29 Jan 2002 11:49:51 +0100 From: Mark Santcroos To: freebsd-emulation@freebsd.org Subject: vmware doesn't close tap device on -CURRENT Message-ID: <20020129114951.H391@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Handles: MS6-6BONE, MS18417-RIPE Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I didn't use vmware for a few weeks so I don't exactly know since when it is. My problem is that I can only use vmware once. The vmnet1 device stays open and so the second time I start vmware it can't open the device (makes sense ofcourse). The question is why it doesn't close. By ktracing vmware I do see that close() is called on the /dev/vmnet1 filedescriptor and the call succeeds. I'm planning to track this further down to see where the close fails. It doesnt seem to be a generic tap(4) problem as opening and closing from the commandline works fine. It would be nice if someone could ack this behaviour. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message