From owner-freebsd-virtualization@freebsd.org Mon May 27 10:06:58 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0443115BEE6E for ; Mon, 27 May 2019 10:06:58 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 509C58D1B7 for ; Mon, 27 May 2019 10:06:57 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0ADA315BEE6D; Mon, 27 May 2019 10:06:57 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAC7B15BEE6C for ; Mon, 27 May 2019 10:06:56 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D9398D1B6 for ; Mon, 27 May 2019 10:06:56 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: by mail-ed1-x529.google.com with SMTP id p26so25951658edr.2 for ; Mon, 27 May 2019 03:06:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Dhi2U7oqQgdiNmsy/lBfAQfxRhnaOiVz4AqdAiXndFc=; b=WyyXOs9noqDxu9dQ00ZrDFuHh48L93br7Wt7Lzt7DJ/ajDJb/U3OgZkgtPICESIsad g7JMAZXTySWgRRysxa3ungbimN7Dqq5g9qHN68VwDWoS0lnUMBPm+TMgLpuxT0Ttc7k6 NqVyqk+ERweIcfkfmwtrmzsZI8zVhfryjfUlhjvp/3EleONoxMx6IYKSyK2AlmZdpXsE sSBo4W/Rb7ewcsjQqFrzjcNIioQR/Lympu4t+ncMwQlB83iJMuCyjRcSqtit9brX2fOf nHVBXNH5P8mRahi42U/HmnwOhB0HKxykJTTMCk74hS52OwT3vHBtJWZYQ9mHi5K9lT06 rxAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Dhi2U7oqQgdiNmsy/lBfAQfxRhnaOiVz4AqdAiXndFc=; b=jI4av6Wse9P/Wz19VbsSJobEzHTyjlE3wqyUYe3xQ5adJvSi7RRb8anj2fjAPc1rp4 v+LF3LTbWf5kJ0OBuiR4UBudwCB9vFUOCigYy+8mN08s3xJXHwczi/K8BVkfIzBIJfK7 1oANRNxz7U8+TwJaoWOINGA12wSYA0RxYvgHXqwjwq1H8gQJwr4qxFPoYfrR0qZdqyup ff6YLmHXAsaDZ1A/64ak8bQ1xX3uTdAFbYodChxdUXpXrme99R4v2pZU+d9lHdrj36rv UJ1S0/FcAIPQ95Pc6PzvK+xq9H9v+od3Qlw4NhKVz0l+O1unf3uVVo/c9S8MxzavQfSz XAng== X-Gm-Message-State: APjAAAWhu+zW7KJxzGD5do4H8Y1TudzKs8REA1qSY4HsIlyNbjeTYmx7 mr3RQq/0lll+T977r3CwSN+67a1DNuKWDfXQ2Io= X-Google-Smtp-Source: APXvYqytjVFYRhcysY+ym6jzOIeeBiMfo1ukEqcIAxBTkFxXCpKgbrG96OW7337uYLASw1l3hSorgM/F7AMdjX0Tqts= X-Received: by 2002:a50:ad77:: with SMTP id z52mr121449309edc.174.1558951614889; Mon, 27 May 2019 03:06:54 -0700 (PDT) MIME-Version: 1.0 References: <20190527013609.dl6zup3rinzh3tw4@mutt-hbsd> In-Reply-To: <20190527013609.dl6zup3rinzh3tw4@mutt-hbsd> From: Alexandru Elisei Date: Mon, 27 May 2019 11:06:43 +0100 Message-ID: Subject: Re: bhyve/arm64 status To: Shawn Webb Cc: virtualization@freebsd.org X-Rspamd-Queue-Id: 3D9398D1B6 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 27 May 2019 10:06:58 -0000 Hi, I've been working on bhyve for arm64. For the CPUs that you have posted: - Overdrive, pine64, pinebook and rock64 don't support bhyvearm64, because they have an older version of the interrupt controller (GIC400 vs GIC500). - RPI3 doesn't support bhyvearm64, because it has a custom interrupt controller. - ThunderX2 will support bhyvearm64 in its current state, however the hypervisor won't take advantage of some important virtualization optimizations that the CPU implements. bhyvearm64 hasn't been tested on hardware, but Mihai is considering the espressobin platform for hardware bringup. On Mon, May 27, 2019 at 2:37 AM Shawn Webb wrote: > Hey all, > > I'm trying to figure out the state of bhyve on arm64 in 13-current. I > have two SoftIron OverDrive 1000s, a bajillion RPI3s, a Pine64, > Rock64, and PineBook, and a ThunderX2. Punish me. > > Thanks, > > -- > Shawn Webb > Cofounder / Security Engineer > HardenedBSD > > Tor-ified Signal: +1 443-546-8752 > Tor+XMPP+OTR: lattera@is.a.hacker.sx > GPG Key ID: 0xFF2E67A277F8E1FA > GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2 >