From owner-freebsd-virtualization@freebsd.org Fri Jul 21 23:01:11 2017 Return-Path: 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 C6D61C09C70 for ; Fri, 21 Jul 2017 23:01:11 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5AB092157 for ; Fri, 21 Jul 2017 23:01:11 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id w191so18398763wmw.1 for ; Fri, 21 Jul 2017 16:01:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=MJDcpaS9pKVqmStnIzJQinweHSslmffPjiUSfrfmdY4=; b=h7ZdXeHTftde/g0WibFkLO7hvuS8ANNF/d5g/ArXqtq/eyHRFOn4mUgackCew4dQ0L d9/xCWix7XsNoMEo0OfbXnqsqzLnOfNQL3fRUg1C0pG6XnJGK8MpRfwhUUtmIn1wHUVc SsBoEZdMxKnFWmddPgpv58qLS3+jTVpJNsytm4AiNgMV//3fXm9jhvsWJjWKKAXH8vAq kv7NcHFQDfQ3EbmckSjzORf7DIx+1PZ3BW78WTzeJYUbW9YQi+/4EYyhmnRkM4AVY2qK vQih+8wuKbjJ9HtJVI8A1y66Zml9IqLddC2nyJ07a3puogE1weGPhhILDLBnlVmUQy1R K9xQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=MJDcpaS9pKVqmStnIzJQinweHSslmffPjiUSfrfmdY4=; b=NdHdZXSy4OH33h29hBz3H5M/LILZYmsrsj0Ptn23lPaDedJ7H8ggEAaqwQeUnHTMLz LObH2WrASGjknAYCTaB+fvUQPlXXzWe4Bt62I7sBk07rr/AOKRQYsQFV9NLwwDICGIoX j88V3Dv9tJW4J28I3JAFPKp7n+hHqDS2Xi3x/9t6N29X8Rfu1I7c6CfCGxwZV0cGrzMM WYAobOfiOgwfDZH1kOLoM+B/igAeoDIy4FjzYRzLZ2BcJU5jT9hLP25e2NECIcaStp3n dfE2q0q/UHyLrX6XHLQFaYpSur0tGvxMX5SBLVomY4AjfQDGvtEZ2ir5R0t525S9RRFn piQg== X-Gm-Message-State: AIVw111/X9axOYwui5G/zU6EhACwLAamjlSSVy3RtbTXImwf2pWbEXHj LQdNzBuAfLPKdfItrKIevVk1xwhcgYIK X-Received: by 10.80.158.168 with SMTP id a37mr7089102edf.169.1500678069355; Fri, 21 Jul 2017 16:01:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.220.8 with HTTP; Fri, 21 Jul 2017 16:01:08 -0700 (PDT) In-Reply-To: References: From: Zaphod Beeblebrox Date: Fri, 21 Jul 2017 19:01:08 -0400 Message-ID: Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2017 23:01:11 -0000 oh ... and ... the console spit out: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4522, size: 8192 (swap is on a separate zVol). On Fri, Jul 21, 2017 at 6:59 PM, Zaphod Beeblebrox wrote: > ... curiously, top running on the guest reveals (the point at which the > bhyve wedges): > > 88722 root 1 52 0 109M 105M pfault 3 0:03 42.37% > llvm-tblgen > 88687 root 1 52 0 374M 347M pfault 2 0:04 38.24% > llvm-tblgen > 88668 root 1 52 0 236M 225M pfault 0 0:04 35.11% > llvm-tblgen > 88743 root 1 52 0 55460K 26392K pfault 3 0:00 10.23% cc > > ... where top on the host just shows 100% bhyve 100% busy on 4 threads. > > > On Fri, Jul 21, 2017 at 6:43 PM, Zaphod Beeblebrox > wrote: > >> Since I found out that I can't run a Samba directory server in a jail, >> I've had the setup of a bhyve on my list. I had toyed with Bhyve 6 or 8 >> months ago, and still had the images, so I zfs cloned one and set about a >> source upgrade. >> >> This ignomineously hung. >> >> So... I upgraded the host to 11.1-RC3, and I reinstalled a fresh guest >> from the 11.1-RC3 install CD. The guest uses UFS2 on a 40G disk, the >> server is an AMD 9590 with 32G RAM and a 40T ZFS array. >> >> After installation, I started the guest again with 1G ram, 4 processors >> (of the 8 on the source CPU) and tried a buildworld again. This time the >> guest crashed and rebooted. >> >> What should be next steps here? This is repeatable. The host is stable >> (it can makeworld -j32 in about 25 minutes ... so it's hardware seems >> good). Is this an AMD bug? Is it bad to use ZFS ZVols? >> > >