From owner-freebsd-current@FreeBSD.ORG Wed Jul 20 23:19:40 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 158CB1065676; Wed, 20 Jul 2011 23:19:40 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 238628FC08; Wed, 20 Jul 2011 23:19:38 +0000 (UTC) Received: by ewy1 with SMTP id 1so1246441ewy.13 for ; Wed, 20 Jul 2011 16:19:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z6ePna1RH0f8rxNEe0c9pQ6fjDCoS8lEEc/onlMBfH4=; b=nx2VKpZkj0cjy+meOQpJtfAyf0gbgW4QoFkMhm59TeP/1kxl5O9j9Czr3br5M0+H05 wMDmn7kNF/CzP9jB4C7+XgoMf+ZGWFyuS0YUHp4IG0WUMVAjQ0n2eETzfy2+BWsPJDeA rClPVAL0/hqBx66AoZDeJSCerEuEEAGgletNc= MIME-Version: 1.0 Received: by 10.213.29.196 with SMTP id r4mr1359444ebc.52.1311203977963; Wed, 20 Jul 2011 16:19:37 -0700 (PDT) Received: by 10.213.15.70 with HTTP; Wed, 20 Jul 2011 16:19:37 -0700 (PDT) In-Reply-To: <565082b8e8b3e358266054e58e591e12@bluelife.at> References: <4E263EFE.3040200@FreeBSD.org> <201107200741.26362.jhb@freebsd.org> <565082b8e8b3e358266054e58e591e12@bluelife.at> Date: Wed, 20 Jul 2011 19:19:37 -0400 Message-ID: From: Ryan Stone To: Bernhard Froehlich Content-Type: text/plain; charset=ISO-8859-1 Cc: Steve Wills , freebsd-current@freebsd.org Subject: Re: em problem in virtualbox since the weekend X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2011 23:19:40 -0000 On Wed, Jul 20, 2011 at 8:33 AM, Bernhard Froehlich wrote: > I think it would be good if someone could try to reproduce that with > emulators/virtualbox-ose-legacy which is 3.2.12 to get some vbox dev > look into the problem again. I saw the problem this weekend on a Linux host running virtualbox 3.2.8. I can