From owner-freebsd-emulation@FreeBSD.ORG  Tue Oct 28 02:09:19 2014
Return-Path: <owner-freebsd-emulation@FreeBSD.ORG>
Delivered-To: freebsd-emulation@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 55F4658A
 for <freebsd-emulation@freebsd.org>; Tue, 28 Oct 2014 02:09:19 +0000 (UTC)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com
 [IPv6:2a00:1450:400c:c05::22c])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id E8034970
 for <freebsd-emulation@freebsd.org>; Tue, 28 Oct 2014 02:09:18 +0000 (UTC)
Received: by mail-wi0-f172.google.com with SMTP id d1so4453284wiv.17
 for <freebsd-emulation@freebsd.org>; Mon, 27 Oct 2014 19:09:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=1pxib4wyZq52YcQw+niXaIfVijZM88yx4acVtMM2quE=;
 b=KUzCwQ1IlaW9fftxuwDLeX+DfQzxX8X9u5eoNnTJS6R2/kRva+LuyFvUwyk5Yv6hQ9
 aN8rNqoicjdXSsHyjRxG63u8KwZ5mhtI8gaGfUJ08Z6zx8BYqF8x+xkMeCPo3yPVa7fe
 EjCZt8biyz30ibcvkxqoNYWyA/oDC1iGXz7oPskxm7cQZYpSqbMdhqLz2Or2bvDWiExB
 DWTMBFysvFoNB80PljO4Wz47RcTJlgnU4Kh87LUZk3W2BMepJ6tEJZrJQSq5FmzMItnO
 egXX+l2r8W4yaRXAwsYFy1HAKt5eImSSGEWGETijIlD2EK+3eKYSZhZfEd4AMKEZgJV5
 xF0w==
MIME-Version: 1.0
X-Received: by 10.180.102.135 with SMTP id fo7mr950098wib.79.1414462157214;
 Mon, 27 Oct 2014 19:09:17 -0700 (PDT)
Received: by 10.217.131.79 with HTTP; Mon, 27 Oct 2014 19:09:17 -0700 (PDT)
Date: Mon, 27 Oct 2014 19:09:17 -0700
Message-ID: <CAD9n1_rTA9joJ94u=XuTDnWzGYf=52qJMfeQ_vehgM5ZmSQPQA@mail.gmail.com>
Subject: /emulators/virtualbox-ose Serial port access?
From: Anthony Takata <htwiz2002@gmail.com>
To: freebsd-emulation@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-emulation@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Development of Emulators of other operating systems
 <freebsd-emulation.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-emulation>, 
 <mailto:freebsd-emulation-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-emulation/>
List-Post: <mailto:freebsd-emulation@freebsd.org>
List-Help: <mailto:freebsd-emulation-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>, 
 <mailto:freebsd-emulation-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Oct 2014 02:09:19 -0000

So I have battled my way through various forum posts and sites around the
internet, and I think I have whittled my issue down to something weird in
VirtualBox.
Basically, I am trying to pass a serial port into a VM for the purposes of
running a fax modem.
The modem appears on the FreeBSD host as /dev/cuau0, and I can use Minicom
to open it and perform various AT commands at the host level.
So, I have set a Windows 2012 VM to put the port as Com1 using the Serial
Device /dev/cuau0.
The problem is, communication is highly erratic inside the Guest, most
characters not coming or going correctly, even under a simple HyperTerminal
session. It is almost like the CTS pin is permanently active but the actual
device is not really ready for data.

Is this a known issue?
Using VirtualBox 4.3.18_OSE on FreeBSD 9.2

Apparently the users and Oracle are pointing the finger at the
oh-so-highly-customized-we-dont-know-what-they-did-to-it FreeBSD version of
virtualbox, and will no lift a finger to help diagnose the issue.