From owner-freebsd-x11@freebsd.org  Wed Sep  2 21:13:10 2015
Return-Path: <owner-freebsd-x11@freebsd.org>
Delivered-To: freebsd-x11@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 ADA1E9C33AB
 for <freebsd-x11@mailman.ysv.freebsd.org>;
 Wed,  2 Sep 2015 21:13:10 +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 99C6E19F8
 for <freebsd-x11@FreeBSD.org>; Wed,  2 Sep 2015 21:13:10 +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 t82LDAih046061
 for <freebsd-x11@FreeBSD.org>; Wed, 2 Sep 2015 21:13:10 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-x11@FreeBSD.org
Subject: [Bug 202643] x11/xorg: illegal instruction starting xorg in FreeBSD
 10.2 in kvm/qemu virtulization
Date: Wed, 02 Sep 2015 21:13:10 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: nogcjx@fastmail.fm
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-202643-8047-xmKkQm4xcY@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-202643-8047@https.bugs.freebsd.org/bugzilla/>
References: <bug-202643-8047@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-x11@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: X11 on FreeBSD -- maintaining and support <freebsd-x11.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-x11/>
List-Post: <mailto:freebsd-x11@freebsd.org>
List-Help: <mailto:freebsd-x11-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2015 21:13:10 -0000

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

--- Comment #12 from nogcjx@fastmail.fm ---
(In reply to Ephelyon from comment #11)
> I think the virtualisation element might be the key issue here.  If you were to run FreeBSD natively on that hardware - and I'm not asking you to, it's just to highlight the issue - my suspicion is that Xorg would probably work.

If I boot from a live DVD, would that suffice as a test?  Is this a live DVD:
File:FreeBSD-10.2-RELEASE-amd64-dvd1.iso

Would that answer who should fix the bug (KVM vs FreeBSD)?  Should FreeBSD fix
it to work with KVM for the purpose of backward compatibility??

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