From owner-freebsd-virtualization@freebsd.org  Sun Sep 24 20:49:08 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 D31B6E00F3C
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Sun, 24 Sep 2017 20:49:08 +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 C13682B41
 for <freebsd-virtualization@FreeBSD.org>; Sun, 24 Sep 2017 20:49:08 +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 v8OKn7EW034464
 for <freebsd-virtualization@FreeBSD.org>; Sun, 24 Sep 2017 20:49:08 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 213333] FreeBSD 11-RELEASE fails to boot under KVM/Qemu
Date: Sun, 24 Sep 2017 20:49:08 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: fbsdbugs17@omni.poc.net
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: cc
Message-ID: <bug-213333-27103-ueb2mrwTew@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-213333-27103@https.bugs.freebsd.org/bugzilla/>
References: <bug-213333-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: Sun, 24 Sep 2017 20:49:08 -0000

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

fbsdbugs17@omni.poc.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fbsdbugs17@omni.poc.net

--- Comment #14 from fbsdbugs17@omni.poc.net ---
This is affecting me too. I tried to identify the CPU feature flags that mi=
ght
be preventing boot on "Opteron_G4", by iteratively attempting boot with each
single non-G3 feature flag disabled in KVM. Unfortunately none of those
attempts worked, so it seems this must be due to a some combination of mult=
iple
CPU feature flags.

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