From owner-freebsd-virtualization@freebsd.org Fri Jul 21 22:59:17 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 5DFFCC09BCA for ; Fri, 21 Jul 2017 22:59:17 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 E69D31F60 for ; Fri, 21 Jul 2017 22:59:16 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id v139so6535825wmv.0 for ; Fri, 21 Jul 2017 15:59:16 -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=REhIxiswUOib0qC6nFwRsYCvsbzgUlmjnbi57EVHR18=; b=B35J/uZNQQO+legb1bTJQ7u3pH7Qgzr1DoZdYS3/IXK7niweQ60lLdy9QbSINUUeas s+tlMQlZnvaaw5QfOtBFdX9fYdQ5q5xcV9ylUJP653eTfkhltDo5sdXi7ZrUG8WlvgKr x/JbWCYcgKEXX+tlzPhKGLsh40mXOJE/IQAueZQ8gRdhLnwq7ooe+1TXVcD7kR40rykb 0aK21rseX0M+xosX9E3SrsVv+Rbcme+y50B4ewj2Z4XvZU2JXWkuCxEKMgW+UKk1MwoT xz1L6yyBfq13Q3Sttjogp6VuReSeAiytfP36LV4tevnX2blNi+dxECB0K6ssx95vdY6/ /m+Q== 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=REhIxiswUOib0qC6nFwRsYCvsbzgUlmjnbi57EVHR18=; b=keiX7Tyx62YZ51Uq1gLYfYxtwyj/POnBZmCaVtyKgHaz1rsftyQUBPBz1nS7Lzp9hn 4zyGrHKxl9C/cw4CyROX0YBIvCCiuKxtsGXUJmFxvGglukQnAj68j3pJD45RT1fIDNlu kNmmjRT2d+lbuyBP2ZdXmP++izA6N9F9qWT5ABuQXGsDBmjpBTxPXLfUFb1bvy723wdi nw7pX9b3ht9vY12tcDslOz5j4BU6BQABhwSVM9UjNyVrtsoRXqF6DDBn0bAlBRxCo/LZ UUxyFzfXFItiukv83+RK4XIeZizxBBPbd9WSJklGfQK5p1iHy8YDr48G2OpNc3c4362v neDg== X-Gm-Message-State: AIVw113zwbwg6romAU8MEHTkEDCDmB+G4hxV1iPEB8y8WIX9/t8nUk63 ial+DS8mCieMWWGQn1v7LmAnuDzykDSz X-Received: by 10.80.222.138 with SMTP id c10mr7333607edl.97.1500677955378; Fri, 21 Jul 2017 15:59:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.220.8 with HTTP; Fri, 21 Jul 2017 15:59:14 -0700 (PDT) In-Reply-To: References: From: Zaphod Beeblebrox Date: Fri, 21 Jul 2017 18:59:14 -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 22:59:17 -0000 ... 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? >