From owner-freebsd-emulation@FreeBSD.ORG Sat Jun 5 06:47:33 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C2DE1065672 for ; Sat, 5 Jun 2010 06:47:33 +0000 (UTC) (envelope-from tedm@mittelstaedt.us) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.freebsd.org (Postfix) with ESMTP id 113C38FC14 for ; Sat, 5 Jun 2010 06:47:32 +0000 (UTC) Received: from [192.168.1.202] (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) by mail.freebsd-corp-net-guide.com (8.14.3/8.14.3) with ESMTP id o556lV6X070972 for ; Fri, 4 Jun 2010 23:47:32 -0700 (PDT) (envelope-from tedm@mittelstaedt.us) Message-ID: <4C09F303.5050602@mittelstaedt.us> Date: Fri, 04 Jun 2010 23:47:31 -0700 From: Ted Mittelstaedt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-emulation@freebsd.org References: <4BD0D601.6080600@mittelstaedt.us> In-Reply-To: <4BD0D601.6080600@mittelstaedt.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (mail.freebsd-corp-net-guide.com [65.75.192.90]); Fri, 04 Jun 2010 23:47:32 -0700 (PDT) Subject: Serial ports under VirtualBox X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2010 06:47:33 -0000 A month or so ago I posted the following, I was wondering if anyone has taken a look at the "disconnect then cannot reconnect" problem in the port. There is an update to the bug I referenced here that will help the situation, but it won't do any good if the FreeBSD port still has the "disconnect then cannot reconnect" problem with the serial ports. Ted On 4/22/2010 4:04 PM, Ted Mittelstaedt wrote: > Hi All, > > Host is FreeBSD 8.0-CURRENT Ports are from CVS done 4/17 > > VirtualBox 3.1.6 OSE with FreeBSD setup as the host OS > > Hardware is dual Xeon 2.0Mhz > > Client OS is Windows XP SP3 > > XP runs great except for the serial ports. I have an app that calls > pagers and dials a USR 56k Sportster > > I can cu -l /dev/cuau0 -s 57600 to the modem and send AT commands > to it just fine. > > When I first tried accessing the serial port from the XP session it failed > completely. Then I found a patch on http://www.virtualbox.org/ticket/1548 > and applied this and now I can talk to the modem from the XP session. > > However there is a problem with opening and closing the serial > port. > > I can run VirtualBox, boot the XP session, go into Hyperterminal, > open the assigned com port, send at commands to the modem, get responses, > dial into my remote, everything works fine. But then once I close the > session > and disconnect from the COM port from Hyperterminal, when I try to > reopen the port I get nothing. > > If I reboot the XP session within the virtual machine I still get nothing. > > I have to close VirtualBox down, then restart it before I can > access the serial port again. > > Any suggestions? > > Ted >