From owner-freebsd-virtualization@freebsd.org  Mon Apr 17 18:35:55 2017
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id F01ABD42503
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Mon, 17 Apr 2017 18:35:55 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id DFAA61ED6
 for <freebsd-virtualization@FreeBSD.org>; Mon, 17 Apr 2017 18:35:55 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3HIZtZW026769
 for <freebsd-virtualization@FreeBSD.org>; Mon, 17 Apr 2017 18:35:55 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 218715] e1000 emulation in bhyve will lock up under Windows
 guests
Date: Mon, 17 Apr 2017 18:35:55 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: bhyve
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: grehan@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status keywords bug_severity priority component assigned_to
 reporter
Message-ID: <bug-218715-27103@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Apr 2017 18:35:56 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218715

            Bug ID: 218715
           Summary: e1000 emulation in bhyve will lock up under Windows
                    guests
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Keywords: bhyve
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-virtualization@FreeBSD.org
          Reporter: grehan@FreeBSD.org

When using the e1000 emulation in bhyve with Windows guests, it's possible =
to
get a lockup where a single vCPU spins at 100%.

This can be reproduced within 10 minutes or so by running iperf3 on Windows=
 to
the host. In normal use, the lockup can take hours or even weeks, but seems=
 to
eventually occur.

A workaround is to use the virtio network drivers on Windows with the
virtio-net emulation on bhyve.

--=20
You are receiving this mail because:
You are the assignee for the bug.=