From owner-freebsd-xen@FreeBSD.ORG Sun Dec 7 08:19:08 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8FEDC2F2 for ; Sun, 7 Dec 2014 08:19:08 +0000 (UTC) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1370C198 for ; Sun, 7 Dec 2014 08:19:08 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id pv20so2620386lab.13 for ; Sun, 07 Dec 2014 00:19:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=wuIm9B8OadmbXWV9qyWyMEUANtrI0C7TAbsEYOlftp8=; b=ToDMg/W8YliRWbAbBrXXDIqO4ZJOttiq0mM4HtdXJoonBrIaI3Rm2zqbb5kcJdfvtP TEuNhvHXx2Udg0wtUUSqUUCoEcZNVFzlkGr6GQ+EnGuDpEMtJRF3PgvayX6a4yBegxvw NHuAxgHmwY8IeAqUD4P3vmqxKUhIrvXdJFC5DyXdlm1mxqSbXeS2aqQdkyRfprWsngEB FssMcnYnhtzAeqYCTx1ivuvd2/pryZ7VZh5f6GdipPbdH4M5tj2LkL6liiAebHh49Qyn tCgndS6YakPJn8kLRbxejTCSdZ25HpMshNF9JHx7nRdbfqbwHT+ew7JCU4s88lyn0wCl 8Z6g== MIME-Version: 1.0 X-Received: by 10.112.199.233 with SMTP id jn9mr10731575lbc.18.1417940345506; Sun, 07 Dec 2014 00:19:05 -0800 (PST) Received: by 10.112.89.136 with HTTP; Sun, 7 Dec 2014 00:19:05 -0800 (PST) Date: Sun, 7 Dec 2014 11:49:05 +0330 Message-ID: Subject: OpenStack On FreeBSD From: Nika Behjati To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 08:19:08 -0000 Hi Excuse me,I have a problem. I installed FreeBSD on XenServer.Can I install OpenStack on FreeBSD?? Best Regards -- Nika Behjati BSc Student - IT Engineering QIAU, Qazvin, Iran From owner-freebsd-xen@FreeBSD.ORG Sun Dec 7 23:54:23 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C0A922B for ; Sun, 7 Dec 2014 23:54:23 +0000 (UTC) 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 837466A3 for ; Sun, 7 Dec 2014 23:54:23 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB7NsN2R077739 for ; Sun, 7 Dec 2014 23:54:23 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: Sun, 07 Dec 2014 23:54:23 +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: miguelmclara@gmail.com X-Bugzilla-Status: Closed 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: In-Reply-To: References: 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-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 23:54:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 miguelmclara@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |miguelmclara@gmail.com --- Comment #9 from miguelmclara@gmail.com --- I was also getting the error: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb After an update via freebsd-update So I rebooted into the old kernel I had compiled and got "9 stable" trough svn. I noticed above: Please note on FreeBSD 9.3 you do not need to build a XENHVM kernel. Just add xenhvm_load="YES" to loader.conf So I built GENERIC + VIMAGE and added the line... the machine boots fine but I get an re0 interface and not xn0 so I'm not sure if XENHVM drivers are really in use. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@FreeBSD.ORG Mon Dec 8 00:37:32 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5A0CAB73 for ; Mon, 8 Dec 2014 00:37:32 +0000 (UTC) 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 41A53A7E for ; Mon, 8 Dec 2014 00:37:32 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB80bW5x023473 for ; Mon, 8 Dec 2014 00:37:32 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: Mon, 08 Dec 2014 00:37:32 +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: miguelmclara@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 00:37:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #10 from miguelmclara@gmail.com --- Actually after a reboot I'm back to: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb % svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn0.eu.freebsd.org/base/stable/9 Relative URL: ^/stable/9 Repository Root: svn://svn0.eu.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 275582 Node Kind: directory Schedule: normal Last Changed Author: ngie Last Changed Rev: 275525 Last Changed Date: 2014-12-05 21:37:27 +0000 (Fri, 05 Dec 2014) Should I try building XENHVM myself again? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@FreeBSD.ORG Mon Dec 8 02:30:08 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8FA28403 for ; Mon, 8 Dec 2014 02:30:08 +0000 (UTC) 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 77DB735E for ; Mon, 8 Dec 2014 02:30:08 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB82U8lU098607 for ; Mon, 8 Dec 2014 02:30:08 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: Mon, 08 Dec 2014 02:30: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: miguelmclara@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 02:30:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #11 from miguelmclara@gmail.com --- Reverting xenfront.c to Revision 251973 worked for me! -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@FreeBSD.ORG Mon Dec 8 18:56:50 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 29955345 for ; Mon, 8 Dec 2014 18:56:50 +0000 (UTC) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7905FC0 for ; Mon, 8 Dec 2014 18:56:49 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id lj1so5730946pab.18 for ; Mon, 08 Dec 2014 10:56:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dpdtech.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=yBsI05GjIWh4R5DFKK2GQTpZGAIJLgoTxqqfYlhjIm4=; b=VSnj6X+FLXXRBgW1Pl1Vj2pxBxeMKSmpZomU51Svm/V/pf+FE6w0pYTX37ZkWiXFo8 hdviovlGfxxR86v5JRaIkPYTVEQylxQnyhezpHz2qtElXFsxjjm5D2+5I1kBOhQ+i1WM iEMxIwR3JwgoNY3fHMkrylDgyMUz20LobiLvk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=yBsI05GjIWh4R5DFKK2GQTpZGAIJLgoTxqqfYlhjIm4=; b=WTA5gUr69TiBKRqVoD2Qd94ugyFXJORHyqJNqJEEhkQsPdMC3u6idu8etbgDfabcgx r86Jek93SUfUXV8EXTA95DkDV6Uzd3UzYI1UbAptIDrvaD2us9XQ7M3gXJJAzejhlsj2 ws6QOR6vGK0sLtVCerJTjnXZcADNJAnztypPut0lEsSYWAkWBATsJya4tbKLhr8aOD/B XMiHwOF1d5MEg1C1E62DQHmXMKhTV5hdiCgvKKaKjyKyTGFU4WBCRQNUqBVPYQ4CbxDG G8vi9ost5OAFP3rLJfUZh59j9X0gsTCASYdQ8dgImidb77TSFBMMULfztcmWSOpA4VM+ uRsA== X-Gm-Message-State: ALoCoQl4sjGRpBIYlfTa3Ivt1xPTYyBgoew8YXnkW16etyOo1+YU/ZUDWo6dSpqaEdKZHmMu6UsI X-Received: by 10.66.139.106 with SMTP id qx10mr57391395pab.138.1418065009018; Mon, 08 Dec 2014 10:56:49 -0800 (PST) Received: from 173-13-188-41-sfba.hfc.comcastbusiness.net (173-13-188-41-sfba.hfc.comcastbusiness.net. [173.13.188.41]) by mx.google.com with ESMTPSA id w1sm20148747pdf.38.2014.12.08.10.56.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 10:56:48 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_C40F0F68-26A7-421D-86B4-89E2F6199FCC"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: OpenStack On FreeBSD From: "David P. Discher" In-Reply-To: Date: Mon, 8 Dec 2014 10:56:51 -0800 Message-Id: <90E25269-0823-43F1-AB6A-29F85527E30E@dpdtech.com> References: To: Nika Behjati X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 18:56:50 -0000 --Apple-Mail=_C40F0F68-26A7-421D-86B4-89E2F6199FCC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 In theory, in should be possible. Last time I tried was like ~ 4 years = ago. There was a linux specific function call in the build process or = pre-start for one of the modules.=20 If I recall, it was something with swift for making blank images.=20 It=92s probably worth someone revisiting at some point. - David P. Discher http://davidpdischer.com/ AIM: DavidDPD | Y!M: daviddpdz=20 On Dec 7, 2014, at 12:19 AM, Nika Behjati wrote: > Hi >=20 > Excuse me,I have a problem. > I installed FreeBSD on XenServer.Can I install OpenStack on FreeBSD?? >=20 > Best Regards >=20 > --=20 > Nika Behjati > BSc Student - IT Engineering > QIAU, Qazvin, Iran > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" --Apple-Mail=_C40F0F68-26A7-421D-86B4-89E2F6199FCC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUhfR0AAoJEEmwU6XuhYWOl9gIAJAA4F+Pk3isWuFhaz09h4aB nr5ytz4gq0nVlRuORRYUHdR2pgwvZ582bTknBWngMI+vencW/BYKKdYH8fUy9DiU 2cGvQckQP3DqQKCeUuhUT2L2dYpTfquzmo4z4l8fqb3lCvJPoGsOX5RrnYXFEeQr qbT098AgoP/+rGR1adh+nxsCZitbaUsuyuTetg0TdCQp8FijNY7lu70KReCJlysd KzEi5Y0hN88Wg1+vvLVfg60tV8/ngRA/DazisgYe8szHDEseRusELkJ4umRanX51 S5PQxPq94n1Irp78GHv4ILimDRbaN94P85iM4REeQQM7mqWoyax959on84JDY2U= =wNy2 -----END PGP SIGNATURE----- --Apple-Mail=_C40F0F68-26A7-421D-86B4-89E2F6199FCC-- From owner-freebsd-xen@FreeBSD.ORG Mon Dec 8 22:45:18 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 98BA14EA for ; Mon, 8 Dec 2014 22:45:18 +0000 (UTC) Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B306C3A for ; Mon, 8 Dec 2014 22:45:18 +0000 (UTC) Received: by mail-pa0-f50.google.com with SMTP id bj1so6135801pad.9 for ; Mon, 08 Dec 2014 14:45:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dpdtech.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=XjktEFc5pfz7aSAwoYMKSr904TuV8lQDbWzjuHkMUCI=; b=cOGcVOZ0y2yvFgHiEGUapFlALjJNLimUhWAsZ9hIlrdSOTuGEj5Ofp9FjbjG6Yue97 WCO0V7ZtCX99gHsI6thMmH0aYiOpBu8egiGJwZJ1z4c8d8trbgwxbagVFIU5dAyrb+AA gJVaMfer0hEg7pG2oGfSc/SWRKqJE/OIcvJVU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=XjktEFc5pfz7aSAwoYMKSr904TuV8lQDbWzjuHkMUCI=; b=YVR6u4fruiJYhwXSZ8K8IKXSDz2n8IVHhcwTa5CPt4+TS3Scek3rg1Bnk645Bn1/7r weAQD7hulOXol7M4RaYzpa0K/xbJJm7xah8rzhCqfBnmVXourgm24uN6FNa7I+iDmdJF tqBcP/sTLLa/QpDMa7CwtKqxXx1j8avQZMw/gBjaF4IW6Ff4Oo6CfP0BeFZvrEly8Lol lhCmKjbGjA41OBz6F5g9jflwHwbMbpoeBhlbe17cGlrWxJL/EOCKn4m1Ka9Q94k0GFw3 HqjtYfuTnbN6aMRlRngrgVUOxqeW7yRa20ctGIiv9rRF5ARBNTGpq9snhRKhRFTt6S4O hlww== X-Gm-Message-State: ALoCoQnxBj7tt6trLcfJoUv08Q9hmqF0Tr4V0rGlERTu4NNNfblDqPPvHf4JE9xUrJ6qimnN88II X-Received: by 10.70.128.80 with SMTP id nm16mr25184368pdb.1.1418078717605; Mon, 08 Dec 2014 14:45:17 -0800 (PST) Received: from 173-13-188-41-sfba.hfc.comcastbusiness.net (173-13-188-41-sfba.hfc.comcastbusiness.net. [173.13.188.41]) by mx.google.com with ESMTPSA id z3sm13489450pdp.17.2014.12.08.14.45.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 14:45:17 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_01F670E0-CE32-40AC-A367-DE072E2D22C9"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Attempting to Get Xen FreeBSD Dom0 working From: "David P. Discher" In-Reply-To: <54819D6A.4050603@citrix.com> Date: Mon, 8 Dec 2014 14:45:21 -0800 Message-Id: <7F90454D-16D5-4871-A155-5ADD01014976@dpdtech.com> References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> <547DFCC0.6030003@citrix.com> <547F1476.8080305@citrix.com> <29437DB9-7DC8-47A8-8FC4-2BFDE736B5BC@dpdtech.com> <547F59B4.1010105@citrix.com> <2DDCAA68-3B11-4E3C-AE61-EAD8CEEF1E2D@dpdtech.com> <547F6AC1.9060709@citrix.com> <7C356027-01D8-4800-B211-282566BC9871@dpdtech.com> <54801F77.5050700@citrix.com> <54819D6A.4050603@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 22:45:18 -0000 --Apple-Mail=_01F670E0-CE32-40AC-A367-DE072E2D22C9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I tried all the combinations of things =E2=80=A6 and still couldn=E2=80=99= t get the xen console switch to work. I finally googled "xen X8STi = console=E2=80=9D, and found - = http://wiki.xen.org/wiki/Xen_Serial_Console - which calls out the super = micro board X8STi - with the options: com1=3D115200,8n1,0x3e8,5 I don=E2=80=99t know what that =E2=80=9C,5=E2=80=9D does =E2=80=A6 but = it fixed it. I have also disabled all the ttys in /etc/ttys for the = serial ports. (haven=E2=80=99t tried the trailing 5 with the ttyu[012] = =E2=80=9Con=E2=80=9D. ) Ok, back to it =E2=80=A6 re-started the debian install, and had = =E2=80=9Cxentop=E2=80=9D running and =E2=80=9Cxl info=E2=80=9D in a = loop, and eventually, within in minutes, the hyper call fails.=20 xc: error: Could not bounce buffer for sysctl hypercall (35 =3D = Resource temporarily unavailabl): Internal error libxl: error: libxl.c:5024:libxl_get_physinfo: getting physinfo: = Resource temporarily unavailable libxl_physinfo failed. xc: error: Could not bounce buffer for sysctl hypercall (35 =3D = Resource temporarily unavailabl): Internal error libxl: error: libxl.c:5507:libxl_get_scheduler: getting domain = info list: Resource temporarily unavailable The debian install is still going, but makes it impossible to launch the = installed system, since no call for xl will work. Sent SIGTERM to all processes = =E2=94=82 Sent SIGKILL to all = processes=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=98 Requesting system reboot [ 1157.299205] Restarting system. root@borg:/zdata/debian # root@borg:/zdata/debian # root@borg:/zdata/debian # xl create -c debian.cfg root@borg:/zdata/debian # xl destroy debian xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error libxl: error: libxl.c:658:libxl_list_domain: getting domain info = list: Resource temporarily unavailable debian is an invalid domain identifier (rc=3D-5) root@borg:/zdata/debian # I=E2=80=99m running AHCI with MSI off in the FreeBSD kernel, and so far, = so good on that front. The great thing is now I got the Xen console = working, so can get the debug output. However the bounce = buffer/hypercall issue i would think is far more important than MSI = interrupts at the monument.=20 - David P. Discher http://davidpdischer.com/ AIM: DavidDPD | Y!M: daviddpdz=20 On Dec 5, 2014, at 3:56 AM, Roger Pau Monn=C3=A9 = wrote: > El 04/12/14 a les 22.28, David P. Discher ha escrit: >> Update: So, I changed a few things, and stuff is working better. >>=20 >> The Xen kernel line is now: >>=20 >> dom0_mem=3D2048M dom0_max_vcpus=3D4 dom0pvh=3D1 sync_console = com1=3D115200,8n1,0x3e8 console=3Dvga,com1 iommu=3Ddebug >=20 > I would advise against sync_console, it can easily cause delays in > interrupt delivery which can cause timeouts in FreeBSD. >=20 >>=20 >> Also note, I have these set in FreeBSD: >>=20 >> console=3D"comconsole vidconsole" >> comconsole_speed=3D"115200" >> comconsole_port=3D"0x3e8" >> boot_multicons=3D"yes" >> vm.max_wired=3D2097152 >> verbose_loading=3D"YES" >> boot_verbose=3D"" # -v: Causes extra debugging information to be = printed >>=20 >> hint.ahci.0.msi=3D0 >> hw.acpi.verbose=3D1 >> debug.acpi.enable_debug_objects=3D1 >>=20 >> So far, no AHCI timeouts. I=E2=80=99v gotten completely through an = install of Debian =E2=80=A6 granted it failed, but for a linux reasons - = couldn=E2=80=99t find/download a package. But is still going. >>=20 >> The change to the console lines also help =E2=80=A6 console=3Dvga,com1 = & sync_console to xen allowed the IPMI SOL COM3 to fully complete the = boot under freebsd. And the tty/login ran and displayed on xc0 : >>=20 >> FreeBSD/amd64 (borg.dpdtech.com) (xc0) >=20 > I will try to find a system similar to yours with an IPMI SOL console > and see if I can figure out what's going on. As a test, could you try = to > disable the comconsole from FreeBSD and see if that makes a = difference? >=20 > console=3D"vidconsole" >=20 > And remove all the comconsole_* and boot_multicons options. This will > have the side effect of removing serial output from the bootloader, = but > it might prevent FreeBSD from screwing the Xen serial console. >=20 >> However, this console will not take any input. I still can=E2=80=99t = get switched into the Xen console (Ctrl-A x3) on either the serial of = VGA consoles.=20 >>=20 >> Another troubling item, em0 flaps when debian is starting up: >>=20 >> xnb(xnb_probe:1144): Claiming device 0, xnb >> xnb1.0: bpf attached >> xnb(xnb_attach:1292): Attaching to backend/vif/1/0 >> xnb(xnb_frontend_changed:1416): frontend_state=3DInitialising, = xnb_state=3DInitWait >> em0: Link is Down >> xnb1.0: 2 link states coalesced >> (d1) mapping kernel into physical memory >> (d1) about to get started... >> xnb(xnb_frontend_changed:1416): frontend_state=3DConnected, = xnb_state=3DInitWait >> xnb(xnb_connect_comms:796): rings connected! >> em0: Link is up 1000 Mbps Full Duplex >>=20 >> em0 is in bridge0, which is what the debian.cfg is using. >=20 > I certainly don't see this kind of flipping on my network card, but I > would focus on fixing the console first, so we can get debug info. >=20 >>=20 >> Also, something really odd =E2=80=A6 hyper calls aren=E2=80=99t = working after launching the debian guest - which also means I can=E2=80=99= t launch any more guests.=20 >>=20 >> root@borg:~ # xl list >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> libxl: error: libxl.c:658:libxl_list_domain: getting domain info = list: Resource temporarily unavailable >> libxl_list_domain failed. >=20 > It seems like you are running out of wired memory, you should increase > vm.max_wired, this can be changed at runtime with sysctl without = problems. >=20 >>=20 >> I=E2=80=99m heading out for the afternoon shortly, but it seems the = next thing to do is to get the consoles working correctly so I can get = debugging info from the hypervisor. Will hopefully bang on this this = evening.=20 >=20 > Thanks for the efforts, please keep me posted on how it goes. >=20 > Roger. >=20 --Apple-Mail=_01F670E0-CE32-40AC-A367-DE072E2D22C9 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUhioCAAoJEEmwU6XuhYWO7WsIAJbOnNA2PKi8s7LY/T+1OGs4 vkq4jsETqONfAa/ScvW6s6PqtLeiE2vliAQD2gCp+nQpGIzoOUQgH9owbB1RNQkU UmuyPDXrDbJH75s7eP/Vl35kUJGYcjhPi8gjpEAt+olqiIwqQngvipJt8vG5gqW5 hMVx7S+CaAhQHdZCjk9LPly8+5Ykk9RdBWodp+T02ZsnWjgYRR5C7OcYmPtUyC6f bP08XcZajjt5nHS6rbWwjVb4MLpeFlSipSkdnvjDuNY5DF6v6w5NTLE2S7YSFd97 nBVgzA4aheq8EpPucGmKxZsndpUzMzFDHNjRr+cTwIA+IGgClham4cexQ7N+cLk= =7T5o -----END PGP SIGNATURE----- --Apple-Mail=_01F670E0-CE32-40AC-A367-DE072E2D22C9-- From owner-freebsd-xen@FreeBSD.ORG Tue Dec 9 08:27:58 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FBD42FC for ; Tue, 9 Dec 2014 08:27:58 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 80B68F21 for ; Tue, 9 Dec 2014 08:27:56 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.07,543,1413244800"; d="scan'208";a="202180134" Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.3.210.2; Tue, 9 Dec 2014 03:27:52 -0500 Message-ID: <5486B287.7070302@citrix.com> Date: Tue, 9 Dec 2014 09:27:51 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: "David P. Discher" Subject: Re: Attempting to Get Xen FreeBSD Dom0 working References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> <547DFCC0.6030003@citrix.com> <547F1476.8080305@citrix.com> <29437DB9-7DC8-47A8-8FC4-2BFDE736B5BC@dpdtech.com> <547F59B4.1010105@citrix.com> <2DDCAA68-3B11-4E3C-AE61-EAD8CEEF1E2D@dpdtech.com> <547F6AC1.9060709@citrix.com> <7C356027-01D8-4800-B211-282566BC9871@dpdtech.com> <54801F77.5050700@citrix.com> <54819D6A.4050603@citrix.com> <7F90454D-16D5-4871-A155-5ADD01014976@dpdtech.com> In-Reply-To: <7F90454D-16D5-4871-A155-5ADD01014976@dpdtech.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA1 Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 08:27:58 -0000 Hello, El 08/12/14 a les 23.45, David P. Discher ha escrit: > > Sent SIGTERM to all processes │ > Sent SIGKILL to all processes───────────────────────────────────────────────┘ > Requesting system reboot > [ 1157.299205] Restarting system. > root@borg:/zdata/debian # > root@borg:/zdata/debian # > root@borg:/zdata/debian # xl create -c debian.cfg > root@borg:/zdata/debian # xl destroy debian > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > libxl: error: libxl.c:658:libxl_list_domain: getting domain info list: Resource temporarily unavailable > debian is an invalid domain identifier (rc=-5) > root@borg:/zdata/debian # > > I’m running AHCI with MSI off in the FreeBSD kernel, and so far, so good on that front. The great thing is now I got the Xen console working, so can get the debug output. However the bounce buffer/hypercall issue i would think is far more important than MSI interrupts at the monument. Glad to know you got it working at the end! I've already pointed this out in my last email, but did you try to increase vm.max_wired even further? This usually happens when mlock in freebsd_privcmd_alloc_hypercall_buffer (xc_freebsd_osdep.c) fails to wire down the memory that would be used by the hypercalls. Roger. From owner-freebsd-xen@FreeBSD.ORG Tue Dec 9 12:01:55 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6C91490 for ; Tue, 9 Dec 2014 12:01:55 +0000 (UTC) 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 CE0B3AAB for ; Tue, 9 Dec 2014 12:01:55 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB9C1tBb053140 for ; Tue, 9 Dec 2014 12:01:55 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, 09 Dec 2014 12:01:55 +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: royger@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 12:01:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D164630 --- Comment #12 from Roger Pau Monn=C3=83=C2=A9 --- I'm not sure I'm correctly understanding the problem you are reporting. Usi= ng freebsd-update should be fine, but AFAIK the patch in this bug report is not included in 9.3 so the updated kernel you get when using freebsd-update will also not contain this patch. Also, I don't see any xenfront.c file in the FreeBSD source tree, so I'm not sure what you meant. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@FreeBSD.ORG Tue Dec 9 13:32:39 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CFCC0A95 for ; Tue, 9 Dec 2014 13:32:39 +0000 (UTC) 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 B3DA03E3 for ; Tue, 9 Dec 2014 13:32:39 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB9DWd2j088636 for ; Tue, 9 Dec 2014 13:32:39 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, 09 Dec 2014 13:32:39 +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: miguelmclara@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 13:32:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D164630 --- Comment #13 from miguelmclara@gmail.com --- Sorry my confusion I assumed from the last comment that the patch was appli= ed: "Roger Pau Monn=C3=83=C2=A9 freebsd_committer 2014-07-18 07:38:39 UTC I've MFCed the patch to stable-9, sorry for missing the 9.3 release." Also I meant "sys/dev/xen/blkfront/blkfront.c" I am getting the same error if I get the latest revision of blkfront.c, but reverting the one before (r251973) works fine! Hope this is a bit more clear, thanks --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@FreeBSD.ORG Tue Dec 9 16:00:08 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 919DAFEF for ; Tue, 9 Dec 2014 16:00:08 +0000 (UTC) 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 788A0836 for ; Tue, 9 Dec 2014 16:00:08 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB9G08Bt071791 for ; Tue, 9 Dec 2014 16:00:08 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, 09 Dec 2014 16:00: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 16:00:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D164630 --- Comment #14 from Roger Pau Monn=C3=83=C2=A9 --- (In reply to miguelmclara from comment #13) > Sorry my confusion I assumed from the last comment that the patch was > applied: > "Roger Pau Monn=C3=83=C2=A9 freebsd_committer 2014-07-18 07:38:39 UTC > I've MFCed the patch to stable-9, sorry for missing the 9.3 release." >=20 >=20 > Also I meant "sys/dev/xen/blkfront/blkfront.c" >=20 > I am getting the same error if I get the latest revision of blkfront.c, b= ut > reverting the one before (r251973) works fine! So if you use the latest revision of the stable-9 branch (that contains r268832), it doesn't work, and the issue that you see is the same as the one mentioned in this bug report (run_interrupt_driven_hooks: still waiting after...)? Can you try to just revert r268832 (instead of going back to r251973), and = see if that solves the problem? HEAD also has this same patch, do you also observe this problem with HEAD? I assume you are using XenServer instead of OSS Xen, is that right? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@FreeBSD.ORG Tue Dec 9 16:39:06 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0F381EAB for ; Tue, 9 Dec 2014 16:39:06 +0000 (UTC) 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 EA724CFC for ; Tue, 9 Dec 2014 16:39:05 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB9Gd53r071667 for ; Tue, 9 Dec 2014 16:39:05 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, 09 Dec 2014 16:39:06 +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: miguelmclara@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 16:39:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #15 from miguelmclara@gmail.com --- I'm no home now but I'll revert the patch as soon as I get there. I should add though that the Dom0 is NetBSD, sorry should have mention that already. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@FreeBSD.ORG Tue Dec 9 19:17:30 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 99D979A6 for ; Tue, 9 Dec 2014 19:17:30 +0000 (UTC) Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B8057D8 for ; Tue, 9 Dec 2014 19:17:30 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id y13so1149904pdi.2 for ; Tue, 09 Dec 2014 11:17:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dpdtech.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=7Q/aG07XkX04Ji9YurRJKBc+EExRtMcPgaNerDq7eo8=; b=JnDiToejvTqLuiY93qLW+cHZeSkX5/THCQJ/i8k78WsOLEi+bbiRI/688Yl5mF7bE6 UZ3jVQTth46wfU98TOItlyK2EHYB+Bbp/ni51EkRMS4rXo7J5SbfTLVbTE7hE0dLqTk1 nl7wcwpo/iQFnDX/Q40EKGb4doD1ZNFiXnFfY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=7Q/aG07XkX04Ji9YurRJKBc+EExRtMcPgaNerDq7eo8=; b=GixboY0ftrNkI91L5LhJ/Fs3K88fjrgmfbYP+eymmfi/zc1GZbwNQW9/RL8Z0Qw1gs 04hFliXIUiXaTQLgBEQL2BKVT0IrEwM8ZJUBzD6jm14gFOfQA8WJMZzVcR4jEmnaxOci 4TGXlDXqmRDjQTIYXMmhLDaYf1brEXGPjOw69mzWpPj0+tJ+1Rg4e9yUK+6gnfLqztSl 5Whb4hYCFSkoWNC+AtEhH6fBlc/1S2H0re2oJcqDbHaN52v6+f6yRaEA/JHElMOErVtR cKoTxPUrrysUw4YMoMjQ2wKl3o4os3NimbQTQoHvu/Dv+5Di58jPsrxXEv8VF8OjWPSB 2XXw== X-Gm-Message-State: ALoCoQkgj6PfnDskyuYUmsw4byZkzlo59slOzL4sgXX8um9h3BaxoluBBo6NRPlo5k0r95uqiPci X-Received: by 10.68.108.165 with SMTP id hl5mr8026589pbb.121.1418152649370; Tue, 09 Dec 2014 11:17:29 -0800 (PST) Received: from 173-13-188-41-sfba.hfc.comcastbusiness.net (173-13-188-41-sfba.hfc.comcastbusiness.net. [173.13.188.41]) by mx.google.com with ESMTPSA id 9sm2150832pdg.38.2014.12.09.11.17.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Dec 2014 11:17:28 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_093D7833-78A3-47CE-87D7-F162846FE817"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Attempting to Get Xen FreeBSD Dom0 working From: "David P. Discher" In-Reply-To: <5486B287.7070302@citrix.com> Date: Tue, 9 Dec 2014 11:17:26 -0800 Message-Id: <55E2C419-E537-4324-B7AB-A21E94863E17@dpdtech.com> References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> <547DFCC0.6030003@citrix.com> <547F1476.8080305@citrix.com> <29437DB9-7DC8-47A8-8FC4-2BFDE736B5BC@dpdtech.com> <547F59B4.1010105@citrix.com> <2DDCAA68-3B11-4E3C-AE61-EAD8CEEF1E2D@dpdtech.com> <547F6AC1.9060709@citrix.com> <7C356027-01D8-4800-B211-282566BC9871@dpdtech.com> <54801F77.5050700@citrix.com> <54819D6A.4050603@citrix.com> <7F90454D-16D5-4871-A155-5ADD01014976@dpdtech.com> <5486B287.7070302@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 19:17:30 -0000 --Apple-Mail=_093D7833-78A3-47CE-87D7-F162846FE817 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 ah, sorry missed that. Will try that today. =20 AHCI lasted over night with MSI off. Something I noticed, is that when = the AHCI bus was timing out, it looked like the Xen Kernel was = re-scanning the PCI bus. (Sorry, didn=E2=80=99t save these logs). = I=E2=80=99ve love to dig into this further. =20 Please let me know what/where to add some debugging code. - David P. Discher http://davidpdischer.com/ AIM: DavidDPD | Y!M: daviddpdz=20 Mobile: 408.368.3725 On Dec 9, 2014, at 12:27 AM, Roger Pau Monn=C3=A9 = wrote: > Hello, >=20 > El 08/12/14 a les 23.45, David P. Discher ha escrit: > >>=20 >> Sent SIGTERM to all processes = =E2=94=82 >> Sent SIGKILL to all = processes=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=98 >> Requesting system reboot >> [ 1157.299205] Restarting system. >> root@borg:/zdata/debian # >> root@borg:/zdata/debian # >> root@borg:/zdata/debian # xl create -c debian.cfg >> root@borg:/zdata/debian # xl destroy debian >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> xc: error: Could not bounce buffer for version hypercall (35 =3D = Resource temporarily unavailabl): Internal error >> libxl: error: libxl.c:658:libxl_list_domain: getting domain info = list: Resource temporarily unavailable >> debian is an invalid domain identifier (rc=3D-5) >> root@borg:/zdata/debian # >>=20 >> I=E2=80=99m running AHCI with MSI off in the FreeBSD kernel, and so = far, so good on that front. The great thing is now I got the Xen = console working, so can get the debug output. However the bounce = buffer/hypercall issue i would think is far more important than MSI = interrupts at the monument.=20 >=20 > Glad to know you got it working at the end! I've already pointed this > out in my last email, but did you try to increase vm.max_wired even = further? >=20 > This usually happens when mlock in > freebsd_privcmd_alloc_hypercall_buffer (xc_freebsd_osdep.c) fails to > wire down the memory that would be used by the hypercalls. >=20 > Roger. >=20 --Apple-Mail=_093D7833-78A3-47CE-87D7-F162846FE817 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUh0rGAAoJEEmwU6XuhYWOSn4H/1uEg8acXfL3cAJk69N08kRB oitpJnHzVmYlDfjI1B1lkCGs+KTCSIH0YjYyrBuK2hmtDafgkZ1iB1reUxcPfMDU mTvY45TmeqgJYV8O9qwQYiKS7urR1Z0kIjQ+wqlnrb6X/3+vI6Oqh20btUy2pjLo 1vcMz9tBtDxXHFu7ts8s8CEGq3bYbNon9ynbVsAAiS8p3UPB/BtX88/mXW98uRYv HYSPoJw8uTjO71qBUwZKBP3LeESiq5rzOw1yJIUI7lwcHILbXgeTtWI9liEfF4Df PxiJy1VpxXZlutoi0wPsAd7viOLQTCPVttqIP05NuFFy75dyyK4/waBbxBmkoGU= =NC7P -----END PGP SIGNATURE----- --Apple-Mail=_093D7833-78A3-47CE-87D7-F162846FE817-- From owner-freebsd-xen@FreeBSD.ORG Thu Dec 11 00:21:47 2014 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 61C55553 for ; Thu, 11 Dec 2014 00:21:47 +0000 (UTC) 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 49570C44 for ; Thu, 11 Dec 2014 00:21:47 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sBB0LlQN019228 for ; Thu, 11 Dec 2014 00:21:47 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: Thu, 11 Dec 2014 00:21:47 +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: miguelmclara@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 00:21:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #16 from miguelmclara@gmail.com --- Since you mention this should work with the latest revision I tested with a fresh svn checkout and rebuilt/reinstalled the kernel. It works fine. So this was most likely a mistake I made or something wrong with the build... My best guess I might have done something wrong in the make installkernel. So the issue is only present when using 9.3-RELEASE not stable! Sorry for the noise! -- You are receiving this mail because: You are the assignee for the bug.