From owner-freebsd-xen@FreeBSD.ORG  Tue Jul 15 20:05:59 2014
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 19643B70
 for <freebsd-xen@FreeBSD.org>; Tue, 15 Jul 2014 20:05:59 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id EE0AA2ED6
 for <freebsd-xen@FreeBSD.org>; Tue, 15 Jul 2014 20:05:58 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6FK5wKV007741
 for <freebsd-xen@FreeBSD.org>; Tue, 15 Jul 2014 20:05:58 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-xen@FreeBSD.org
Subject: [Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still
 waiting after 60 seconds for xenbusb_nop_confighook_cb
Date: Tue, 15 Jul 2014 20:05:58 +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: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: feld@FreeBSD.org
X-Bugzilla-Status: Timeout
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-164630-23905-aparJK6tpr@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-164630-23905@https.bugs.freebsd.org/bugzilla/>
References: <bug-164630-23905@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-xen@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2014 20:05:59 -0000

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

Mark Felder <feld@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |feld@FreeBSD.org

--- Comment #5 from Mark Felder <feld@FreeBSD.org> ---
(In reply to mcdouga9 from comment #3)
> I can still reproduce this issue.  I just installed FreeBSD 9.3-RELEASE,
> compiled and installed a kernel from the XENHVM config file on the following
> platforms:
> 
> XenServer 6.2SP1 (Xen 4.1) 70446c XS62ESP1002
> XenServer "6.5"  (Xen 4.4) 86858c XenServer Creedence Alpha 4
> 
> The reason is because r256423 was merged to 10 as r256757 but not to 9 yet. 
> 10 works great.
> 
> In the meantime I am still using feld@'s patch every time I have to compile
> 9: https://feld.me/freebsd/freebsd9-xen-cdrom-fix.patch
> 
> It would be appreciated if it could be incorporated into 9.  Thanks.

Please note on FreeBSD 9.3 you do not need to build a XENHVM kernel. Just add
xenhvm_load="YES" to loader.conf

I'm surprised this wasn't backported to 9-STABLE. (It wasn't my patch; I
believe I just fixed it slightly to patch to 9 cleanly)

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