From owner-freebsd-virtualization@freebsd.org Sun Mar 31 03:47:31 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 142491571259 for ; Sun, 31 Mar 2019 03:47:31 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [65.103.231.193]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 10D158E080 for ; Sun, 31 Mar 2019 03:47:30 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 2D76DC5243; Sat, 30 Mar 2019 21:48:14 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 0gicF1RaLvBJ; Sat, 30 Mar 2019 21:48:13 -0600 (MDT) Received: from macbex.local (209-33-197-163.dsl.infowest.net [209.33.197.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Sat, 30 Mar 2019 21:48:13 -0600 (MDT) From: Rebecca Cran Subject: Re: Updating uefi-edk2-bhyve To: "Rodney W. Grimes" Cc: D Scott Phillips , freebsd-virtualization@freebsd.org References: <201903302037.x2UKbk4u006726@gndrsh.dnsmgr.net> Message-ID: Date: Sat, 30 Mar 2019 21:47:19 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <201903302037.x2UKbk4u006726@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 10D158E080 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.94 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-2.98)[ip: (-9.87), ipnet: 65.100.0.0/14(-4.90), asn: 209(-0.07), country: US(-0.07)]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bluestop.org:+]; DMARC_POLICY_ALLOW(-0.50)[bluestop.org,quarantine]; MX_GOOD(-0.01)[mail.bluestop.org]; NEURAL_HAM_SHORT(-0.95)[-0.952,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:209, ipnet:65.100.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[] 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: Sun, 31 Mar 2019 03:47:31 -0000 On 3/30/19 2:37 PM, Rodney W. Grimes wrote: >> On 3/30/19 1:08 AM, Rodney W. Grimes wrote: >>> >>> So it is a edk2 implementation, and can you point me at >>> the bhyve version of it? The Qemu/KVM version is rather >>> not relavent to this discussion as that would not work due >>> to core vmm implementation differences. Yes, OVMF is part of the TianoCore EDK2. OVMF/KVM is relevant in my opinion because the BHYVE UEFI firmware is a port of OVMF. In fact, with Scott's changes there's no longer a BhyvePkg, but our copy of OvmfPkg works with Bhyve. The code can be found at https://gitlab.com/scott-ph/edk2/tree/wip/2019-03/v2-bhyve-rebase-edk2-stable201903 . > ^^^^^^^^^^^ This is the critical version, this is the > version of the SMBIOS/dmitables implemented by the bios. I think you're confused: I wasn't asking about updating the version of _SMBIOS_ that Bhyve uses, just the BIOS version and release date that are shown in the BIOS section of the SMBIOS data. -- Rebecca Cran From owner-freebsd-virtualization@freebsd.org Sun Mar 31 07:44:10 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 79C171551543 for ; Sun, 31 Mar 2019 07:44:10 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 6870B6DE51 for ; Sun, 31 Mar 2019 07:44:09 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x2V7i3kO008825; Sun, 31 Mar 2019 00:44:03 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x2V7i38B008824; Sun, 31 Mar 2019 00:44:03 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201903310744.x2V7i38B008824@gndrsh.dnsmgr.net> Subject: Re: Updating uefi-edk2-bhyve In-Reply-To: To: Rebecca Cran Date: Sun, 31 Mar 2019 00:44:03 -0700 (PDT) CC: "Rodney W. Grimes" , D Scott Phillips , freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 6870B6DE51 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [0.22 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.85)[-0.850,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.52)[-0.521,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.69)[0.688,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.01)[ip: (0.08), ipnet: 69.59.192.0/19(0.04), asn: 13868(0.02), country: US(-0.07)] 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: Sun, 31 Mar 2019 07:44:10 -0000 > > On 3/30/19 2:37 PM, Rodney W. Grimes wrote: > >> On 3/30/19 1:08 AM, Rodney W. Grimes wrote: > >>> > >>> So it is a edk2 implementation, and can you point me at > >>> the bhyve version of it? The Qemu/KVM version is rather > >>> not relavent to this discussion as that would not work due > >>> to core vmm implementation differences. > > > Yes, OVMF is part of the TianoCore EDK2. OVMF/KVM is relevant in my > opinion because the BHYVE UEFI firmware is a port of OVMF. In fact, with > Scott's changes there's no longer a BhyvePkg, but our copy of OvmfPkg > works with Bhyve. The code can be found at > https://gitlab.com/scott-ph/edk2/tree/wip/2019-03/v2-bhyve-rebase-edk2-stable201903 > . > > > > ^^^^^^^^^^^ This is the critical version, this is the > > version of the SMBIOS/dmitables implemented by the bios. > > > I think you're confused: I wasn't asking about updating the version of > _SMBIOS_ that Bhyve uses, just the BIOS version and release date that > are shown in the BIOS section of the SMBIOS data. Ack, I get your queston now, and my answer is: Yes if Scott updated the edk2 port the bios version in that should defanitly be bumped. What SMBIOS version is it reporting, out of curosity as I need to do some work on that part of it with respect to my VM_MAXCPU changes. (Three reviews process, expect 3 to 5 more before work is completed.) > Rebecca Cran -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Sun Mar 31 13:26:02 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 74CB9155E0E4 for ; Sun, 31 Mar 2019 13:26:02 +0000 (UTC) (envelope-from chuck@tuffli.net) Received: from mail-io1-xd44.google.com (mail-io1-xd44.google.com [IPv6:2607:f8b0:4864:20::d44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 756E681993 for ; Sun, 31 Mar 2019 13:26:00 +0000 (UTC) (envelope-from chuck@tuffli.net) Received: by mail-io1-xd44.google.com with SMTP id c4so5424112ioh.9 for ; Sun, 31 Mar 2019 06:26:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuffli-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Aeptdwul5hqEmJjO1UUdnj2fLR9Me6KWd97xXQhgalc=; b=L0EB8MsxECLNxSqnkdjUEDPpMbsBz8LRAzbZIwPeTjy9gqzoNUtIdtNEqVkkn31FtS qfVS7Y5NUJcw5A/B/A0w1HyhAIqEGthuDwWE7MMQUjFcbEuOHqDrWu7+YUG9clKZCfQ1 qAaMawXteq/bzZhYK0WEpx7Ptz5V8C7YR0weoXwvhpTGUmvoBgEJvXL6d2ZXwqlgdTXQ xSUOFEegYZLlsymH5jzWGPQqPYkCukai00A/Ow9k8uLyeCuc63XqVhPzS9leztxj9mC6 DYDa5LfUtYyand0USd+s/VXRHUXn/EdKHMO8saWrO0Lhg3kplLYK54o4JL+5VN07KEMD 5G5Q== 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=Aeptdwul5hqEmJjO1UUdnj2fLR9Me6KWd97xXQhgalc=; b=CR15ESUAZEjwd3M6bKVrToCB3bwJnwkHFUJgzWdBoLb8Nc2OpW1tNi+rZb+MiKAAoY ZGYisIqFciBeoz6+51owwE+l7IRiKkh6VKgf3glXaQsxIBFgxwDiKagaGfbCPLd5ZZ63 KXQwXz3rRv6dxMZvJ+i+6noYTK6Xz0t8doc4jP/WpYWHHaXPfeRFLJms1xeALCikeXR2 k1y3vaCNYa1uJCH7Y3CB2z665RADc7PjQEo5UjQIABK/PYI90nNISKVpmbhIfknd624Z Hh61lEgMMSiqIwGU5X10cHNthTIHkoxsyL83uk9/WBydol1gcWBnJoZRVbXatuOErtzF 9L2w== X-Gm-Message-State: APjAAAXugmkZIBWpBRD3xUX61sa0SwFdoltjzJk5h5x667fNBZACKuEI sG+5sDIsvhaD323ydQCtN+n0WPdVcZlopzIbxBVwaA== X-Google-Smtp-Source: APXvYqxwvXbLLYwyWu5i/Ybv0fEvL3KxWiz4FJoUEz8oVwNFBc8bK5ZVpgKP9MDLUMyeV85XYZ5Ej/prddJjHSgkmRY= X-Received: by 2002:a5d:855a:: with SMTP id b26mr25715297ios.151.1554038759414; Sun, 31 Mar 2019 06:25:59 -0700 (PDT) MIME-Version: 1.0 References: <79b6eebd-2320-1888-1162-d3ca5492670c@physik.tu-berlin.de> In-Reply-To: <79b6eebd-2320-1888-1162-d3ca5492670c@physik.tu-berlin.de> From: Chuck Tuffli Date: Sun, 31 Mar 2019 06:25:48 -0700 Message-ID: Subject: Re: core dumps running in bhyve To: Fabian Freyer Cc: freebsd-emulation@freebsd.org, FreeBSD Hackers , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 756E681993 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tuffli-net.20150623.gappssmtp.com header.s=20150623 header.b=L0EB8Msx; spf=permerror (mx1.freebsd.org: domain of chuck@tuffli.net uses mechanism not recognized by this client) smtp.mailfrom=chuck@tuffli.net X-Spamd-Result: default: False [-3.84 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[tuffli-net.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; DMARC_NA(0.00)[tuffli.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[tuffli-net.20150623.gappssmtp.com:+]; R_SPF_PERMFAIL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.4.d.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com,aspmx.l.google.com,aspmx2.googlemail.com,aspmx3.googlemail.com,aspmx4.googlemail.com,alt2.aspmx.l.google.com,aspmx5.googlemail.com]; IP_SCORE(-0.70)[ip: (1.60), ipnet: 2607:f8b0::/32(-2.89), asn: 15169(-2.15), country: US(-0.07)]; NEURAL_HAM_SHORT(-0.84)[-0.836,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] 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: Sun, 31 Mar 2019 13:26:02 -0000 On Fri, Dec 28, 2018 at 3:53 AM Fabian Freyer wrote: > > CCing freebsd-virtualization@, because they might know more about this. > > Am 25.12.2018 um 02:24 schrieb Chuck Tuffli: > > Using the latest bhyve, I'm seeing core dumps in the guest when running: > > nvmecontrol identify nvme0 > > against the emulated NVMe drive. The location of the core dump changes > > from run to run, but I suspect the root cause is a memory corruption > > caused by the transfer of the Identify data (4KB) back to the guest. > > This transfer of data is actually a memcpy to an address returned from > > vm_map_gpa() based on the physical address provided by the guest. > > > > Based on the signature of one of the core dumps, I modified > > nvmecontrol to always pass a 4KB aligned buffer to the driver instead > > of the (typically) unaligned address of the structure on the stack. > > With this change, nvmecontrol in the guest no longer core dumps. What > > I don't understand is why this changes the behavior. Do the addresses > > passed to vm_map_gpa() need to be page aligned? > > AFAIK vm_map_gpa maps a page, so yes, it needs to be 4k-aligned. > > > Or did moving the > > memory location from the stack to the heap merely mitigate what is > > corrupted? Thanks Fabian for the redirect to a better list. FWIW, the issue is with bhyve's NVMe emulation code and not anything to do with vm_map_gpa() per se. See https://reviews.freebsd.org/D19695 for those who are curious. --chuck From owner-freebsd-virtualization@freebsd.org Mon Apr 1 21:34:57 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 8ACC8156FC72 for ; Mon, 1 Apr 2019 21:34:57 +0000 (UTC) (envelope-from james@enginsoftusa.com) Received: from NAM05-BY2-obe.outbound.protection.outlook.com (mail-eopbgr710102.outbound.protection.outlook.com [40.107.71.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D5C38B120 for ; Mon, 1 Apr 2019 21:34:55 +0000 (UTC) (envelope-from james@enginsoftusa.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORG4150962.onmicrosoft.com; s=selector1-enginsoftusa-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=20TE6Wt8sYC/btXrsJRD+0o3S+Wd56l1dIeCDBAxJVI=; b=wR9B/qdMJp+rSMRdv3Wa3N/1beHIJXr0oDJeUN6a4zPkhuJLJ3WzTZNsbpqAbMzdLbshXn7xS4Qo6fWth5NjeXlt4xfMrBx8DSeemx1tqvU9aej79kxa7q0vi1NHLACAD5cwEC8vkNIFyl4EYZtOEFKcrc97ZH+drszF/mUahAY= Received: from SN6PR04MB4527.namprd04.prod.outlook.com (52.135.120.25) by SN6PR04MB5278.namprd04.prod.outlook.com (20.177.253.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.20; Mon, 1 Apr 2019 21:34:53 +0000 Received: from SN6PR04MB4527.namprd04.prod.outlook.com ([fe80::c95e:c178:8d66:3703]) by SN6PR04MB4527.namprd04.prod.outlook.com ([fe80::c95e:c178:8d66:3703%3]) with mapi id 15.20.1750.017; Mon, 1 Apr 2019 21:34:53 +0000 From: James Crist To: "'freebsd-virtualization@freebsd.org'" Subject: VMs without unrestricted mode support Thread-Topic: VMs without unrestricted mode support Thread-Index: AdTo0nx01okGBmHDSu68HzLe7/4m2g== Date: Mon, 1 Apr 2019 21:34:53 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [2605:6000:1525:80c6:7cc2:96b4:5f51:a28e] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: f6313398-309b-4f5b-9b5f-08d6b6e9e0b8 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(5600139)(711020)(4605104)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(2017052603328)(7193020); SRVR:SN6PR04MB5278; x-ms-traffictypediagnostic: SN6PR04MB5278: x-ms-exchange-purlcount: 4 x-microsoft-antispam-prvs: x-forefront-prvs: 0994F5E0C5 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(136003)(346002)(376002)(366004)(39830400003)(199004)(189003)(46003)(97736004)(6916009)(106356001)(316002)(105586002)(6436002)(54896002)(8936002)(4744005)(5660300002)(86362001)(52536014)(25786009)(53936002)(68736007)(508600001)(7696005)(476003)(486006)(71200400001)(236005)(55016002)(71190400001)(74316002)(21615005)(6306002)(9686003)(99286004)(8676002)(6116002)(790700001)(256004)(2906002)(14444005)(102836004)(6346003)(33656002)(81156014)(81166006)(606006)(6506007)(186003)(14454004)(7736002)(491001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR04MB5278; H:SN6PR04MB4527.namprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: enginsoftusa.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: 7LX/OleM2POH8C5hM6gsc/CItlnGKWQdQkDT1KFF3xwTP6zrkBSR0GWkRZEjnTiBDl5/5vfeLyCYw7mTQzO2QXDZvHTAgqTklApyblaKZCx6E52mdBrgFuFcednVZlAm9XdcZpyqDHrI9luArMbIU/2byOPVsePKku55sQWrolVhF6LZ1dIR4a7Ln4HOqDHmmC8VhTIy1biOMystb7oof28NHOS5riHX7AoioAZ26j9101438wQJEmi/dv9SW2vSrNzxxCzMzgFVGC+tGMePUOO7lxJ2hccg6SDZ+z+FtRXshjDxOiJ5h5QNwk1BLeQM7i4XrHqxmyB/W6mpL6dYOc55qdlFUj4O3xra+QzyK/WvYrY7U8KLuZy8t6AdIlO4R0MKMKGC1mK9RVDZZgDWxE4ZX8j1TSvYlsIqQu9TpJw= MIME-Version: 1.0 X-OriginatorOrg: enginsoftusa.com X-MS-Exchange-CrossTenant-Network-Message-Id: f6313398-309b-4f5b-9b5f-08d6b6e9e0b8 X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2019 21:34:53.2112 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: e5b86156-7766-436e-a0cb-644ff58be8ee X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR04MB5278 X-Rspamd-Queue-Id: 1D5C38B120 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=NETORG4150962.onmicrosoft.com header.s=selector1-enginsoftusa-com header.b=wR9B/qdM; spf=pass (mx1.freebsd.org: domain of james@enginsoftusa.com designates 40.107.71.102 as permitted sender) smtp.mailfrom=james@enginsoftusa.com X-Spamd-Result: default: False [-2.12 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.85)[-0.849,0]; R_DKIM_ALLOW(-0.20)[NETORG4150962.onmicrosoft.com:s=selector1-enginsoftusa-com]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[enginsoftusa.com]; NEURAL_HAM_LONG(-0.99)[-0.994,0]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[NETORG4150962.onmicrosoft.com:+]; MX_GOOD(-0.01)[enginsoftusa-com.mail.protection.outlook.com,enginsoftusa-com.mail.protection.outlook.com]; RCVD_IN_DNSWL_NONE(0.00)[102.71.107.40.list.dnswl.org : 127.0.3.0]; NEURAL_SPAM_SHORT(0.24)[0.238,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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, 01 Apr 2019 21:34:57 -0000 Hello, I originally asked this on the FreeNAS forums and was directed here.= I'm not sure if this is a FreeNAS issue, a bhyve issue, or a me doing some= thing wrong issue. My processor (W3550) supports virtualization but does not have unrestricted= guest capability. According to the documentation (https://www.freebsd.org/= doc/handbook/virtualization-host-bhyve.html) it sounds like I should still = be able to run VMs as long as they only have one vCPU but I still get the e= rror. According to this post (https://redmine.ixsystems.com/issues/31338) i= t sounds like this is only true for FreeBSD VMs but the source provided doe= sn't talk about number of cores. Can someone confirm under what conditions a VM can be run without unrestric= ted guest? Thank you, James From owner-freebsd-virtualization@freebsd.org Mon Apr 1 22:15:48 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 0871F1570690 for ; Mon, 1 Apr 2019 22:15:48 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from mx1.shrew.net (mx1.shrew.net [38.97.5.131]) (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 940898C25C for ; Mon, 1 Apr 2019 22:15:46 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from mail.shrew.net (mail.shrew.prv [10.24.10.20]) by mx1.shrew.net (8.15.2/8.15.2) with ESMTP id x31MFiJZ018630 for ; Mon, 1 Apr 2019 17:15:45 -0500 (CDT) (envelope-from mgrooms@shrew.net) Received: from [10.16.32.30] (unknown [172.126.77.65]) by mail.shrew.net (Postfix) with ESMTPSA id BDE9B195681 for ; Mon, 1 Apr 2019 17:15:39 -0500 (CDT) Subject: Re: VMs without unrestricted mode support To: freebsd-virtualization@freebsd.org References: From: Matthew Grooms Message-ID: Date: Mon, 1 Apr 2019 17:15:37 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx1.shrew.net [10.24.10.10]); Mon, 01 Apr 2019 17:15:45 -0500 (CDT) X-Rspamd-Queue-Id: 940898C25C X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of mgrooms@shrew.net designates 38.97.5.131 as permitted sender) smtp.mailfrom=mgrooms@shrew.net X-Spamd-Result: default: False [-4.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[cached: mx1.shrew.net]; NEURAL_HAM_SHORT(-0.89)[-0.893,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:174, ipnet:38.0.0.0/8, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; DMARC_NA(0.00)[shrew.net]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[131.5.97.38.list.dnswl.org : 127.0.10.0]; IP_SCORE(-0.89)[ip: (-9.53), ipnet: 38.0.0.0/8(2.88), asn: 174(2.26), country: US(-0.06)] 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, 01 Apr 2019 22:15:48 -0000 On 4/1/2019 4:34 PM, James Crist wrote: > Hello, I originally asked this on the FreeNAS forums and was directed here. I'm not sure if this is a FreeNAS issue, a bhyve issue, or a me doing something wrong issue. > > My processor (W3550) supports virtualization but does not have unrestricted guest capability. According to the documentation (https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html) it sounds like I should still be able to run VMs as long as they only have one vCPU but I still get the error. According to this post (https://redmine.ixsystems.com/issues/31338) it sounds like this is only true for FreeBSD VMs but the source provided doesn't talk about number of cores. > > Can someone confirm under what conditions a VM can be run without unrestricted guest? I can't remember exact, but I believe unrestricted guest is also required for UEFI/CSM ( BIOS ) support. If that's true, you may still be able to use bhyveload or grub2-bhyve to boot single vCPU VMs, but not UEFI. Hopefully someone with more knowledge will chime in to correct me if I'm misleading you. -Matthew From owner-freebsd-virtualization@freebsd.org Tue Apr 2 14:56:13 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 E951E15699F9 for ; Tue, 2 Apr 2019 14:56:12 +0000 (UTC) (envelope-from darkfiberiru@gmail.com) Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ED8E28FDC8 for ; Tue, 2 Apr 2019 14:56:11 +0000 (UTC) (envelope-from darkfiberiru@gmail.com) Received: by mail-oi1-x231.google.com with SMTP id j132so10733136oib.2 for ; Tue, 02 Apr 2019 07:56:11 -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=7qUguHVQOZyW30fLRi6xnqYKu93iF7t5A6TEoivWZiU=; b=fNCJKa+mM3HBGyFJUzYhDuyDQr+MHsTmdmgpIL0fjvjgG6yp8BrjcKsd5o2Z0n810P raTOuFkfNoDXGoGu5aCChdgANALZDqOxwRfBTeBlbeZroEpACoOIBakpIeY4CqbBGOtL uCxrQ9Hr8yg5FzwOs17VmNWV2O/vdqZ9M9p70cY+QedeDLX9RwjGx2bIdDuEnqbz9OjF lrnzs3K0Nuqlpc+W47wS+8lyflEccGNfSi3az+cm1u4/JSzLmRrB0Gqg5AWXXwT0el8H eazOKpPmGyEok5uMX1cuL5TXJUoL8b1XFygdoUxw7+98nuUogqFPKjSNkP/0A2Z7mKI9 rybg== 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=7qUguHVQOZyW30fLRi6xnqYKu93iF7t5A6TEoivWZiU=; b=HUXkivPFaTCPDzcuWKH5D8yzn6mNR2U25MYM0Fd1Ke1j2lqk+lqN9shInYxeppPkRa f8X34sniX1yVfkevPaw4sys94PDJYVTYO/XZJXMEctb7AM0U9xpbVvLR6KMlk56Dakjk WSWuNeYU72VWmM43izFCgPmFO4msN5A3Q4zzSi019uiXsU7JMpg6QAuGwVVPIEWkY49L lr8TtkjZD72AZwivqLonvb3keF0oHqrc6+N3CvBm/1vFLkqH/OzXhQo8B2Lozjch6ULj KA2mFUqnBXAghz8yV9sGjUqhJZB0cDtImBbRKo9UXTaH4zy9Yg3HNzoI7/bQ84l2Yveu /l4g== X-Gm-Message-State: APjAAAUp5O4nKXHEupI1hg2dXE5dJaVrqBAK0NwGR3qAi5aJnW4s65T3 VNMyDGjCeVBZF395g8ys96/TA4Hd4zygdGs65uHovA== X-Google-Smtp-Source: APXvYqxE3VnzrTGb+i4jitgZL8kcgxc83aTofC6XM8/u3wNaisWKr9/fqhTadlp9v2PiTbz2uYrttr3SP98ZRSHiDnY= X-Received: by 2002:aca:e58d:: with SMTP id c135mr1516793oih.20.1554216971130; Tue, 02 Apr 2019 07:56:11 -0700 (PDT) MIME-Version: 1.0 References: <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <20190303032918.GA60561@admin.sibptus.ru> In-Reply-To: <20190303032918.GA60561@admin.sibptus.ru> From: Nick Wolff Date: Tue, 2 Apr 2019 10:56:13 -0400 Message-ID: Subject: Re: Windows 2019 server To: Victor Sudakov Cc: freebsd-virtualization@freebsd.org X-Rspamd-Queue-Id: ED8E28FDC8 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=fNCJKa+m; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of darkfiberiru@gmail.com designates 2607:f8b0:4864:20::231 as permitted sender) smtp.mailfrom=darkfiberiru@gmail.com X-Spamd-Result: default: False [-6.91 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.993,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.3.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.91)[ip: (-9.45), ipnet: 2607:f8b0::/32(-2.89), asn: 15169(-2.15), country: US(-0.06)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] 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: Tue, 02 Apr 2019 14:56:13 -0000 There is paravirtulized support in FreeBSD 11.2 and 12 but you need to sideload the virtio drivers into windows. Sadly microsoft doesn't ship with them even with how "cloud" focused they are. Ahci-hd will allow you to get around this. I know we had some restrictions in the past on needing specific virt-io drivers for windows I'm not sure if that is fixed now. I think nvme paravirtual might also just work with windows but haven't confirmed that lately. On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov wrote: > Jason Tubnor wrote: > > > > > Which kind of storage did you present to the Windows 2019 guest, > > > paravirtualized or ahcd-hd ? > > > > ahci-hd is what you want with bhyve and uefi > > Still no paravirtualized disks support for Windows guests, even in > FreeBSD 12? How sad. > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/ > From owner-freebsd-virtualization@freebsd.org Tue Apr 2 16:04:31 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 CA283156B523 for ; Tue, 2 Apr 2019 16:04:31 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from app.eeeit.de (app.eeeit.de [188.68.43.176]) (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 9CFA06B624 for ; Tue, 2 Apr 2019 16:04:30 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from [100.92.110.33] (ip-109-41-195-17.web.vodafone.de [109.41.195.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: mike@reifenberger.com) by app.eeeit.de (Postfix) with ESMTPSA id B3E735972D; Tue, 2 Apr 2019 18:04:19 +0200 (CEST) Date: Tue, 02 Apr 2019 18:04:25 +0200 User-Agent: K-9 Mail for Android In-Reply-To: References: <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <20190303032918.GA60561@admin.sibptus.ru> MIME-Version: 1.0 Subject: Re: Windows 2019 server To: freebsd-virtualization@freebsd.org, Nick Wolff , Victor Sudakov From: Michael Message-ID: X-Rspamd-Queue-Id: 9CFA06B624 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.50 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.93)[0.930,0]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[reifenberger.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.96)[0.959,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[app.eeeit.de,app.reifenberger.com]; NEURAL_SPAM_LONG(0.99)[0.991,0]; IP_SCORE(0.73)[asn: 197540(3.65), country: DE(-0.01)]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:197540, ipnet:188.68.32.0/20, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Tue, 02 Apr 2019 16:04:32 -0000 Hi, I just tried on FreeBSD12 and Windows10, bhyve crashes when loading the vi= rtstor driver=2E Am 2=2E April 2019 16:56:13 MESZ schrieb Nick Wolff : >There is paravirtulized support in FreeBSD 11=2E2 and 12 but you need to >sideload the virtio drivers into windows=2E Sadly microsoft doesn't ship >with >them even with how "cloud" focused they are=2E Ahci-hd will allow you to >get >around this=2E I know we had some restrictions in the past on needing >specific virt-io drivers for windows I'm not sure if that is fixed now=2E >I >think nvme paravirtual might also just work with windows but haven't >confirmed that lately=2E > >On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov >wrote: > >> Jason Tubnor wrote: >> > >> > > Which kind of storage did you present to the Windows 2019 guest, >> > > paravirtualized or ahcd-hd ? >> > >> > ahci-hd is what you want with bhyve and uefi >> >> Still no paravirtualized disks support for Windows guests, even in >> FreeBSD 12? How sad=2E >> >> -- >> Victor Sudakov, VAS4-RIPE, VAS47-RIPN >> 2:5005/49@fidonet http://vas=2Etomsk=2Eru/ >> >_______________________________________________ >freebsd-virtualization@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-virtualization >To unsubscribe, send any mail to >"freebsd-virtualization-unsubscribe@freebsd=2Eorg" Gru=C3=9F ---=20 Michael From owner-freebsd-virtualization@freebsd.org Tue Apr 2 16:23:51 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 20CBD156BE79 for ; Tue, 2 Apr 2019 16:23:51 +0000 (UTC) (envelope-from jason@corrupted.io) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 C50F56C3EE for ; Tue, 2 Apr 2019 16:23:48 +0000 (UTC) (envelope-from jason@corrupted.io) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id C6D4F22077 for ; Tue, 2 Apr 2019 12:23:47 -0400 (EDT) Received: from imap3 ([10.202.2.53]) by compute6.internal (MEProxy); Tue, 02 Apr 2019 12:23:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=corrupted.io; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=mesmtp; bh=tF nhBXUBBS1/HbTjbSyLd+NmsWN4GS9pvs2uAgCjMs0=; b=fz2Xg29aCscK+0bAOw QdHMT5mTDuNTSpNIkHMTYsQzvE7PF7ZhPJQiYqCX4Bup1A2qBtYwZtRM87NQMSVr fnu8SKIKt0JIWy3VlrLfn9b2Sklyn3m5v4CEwA257R9AlSDjomzShfe0Gldg7lQ7 6RbmRcNwLpMxNpjQlbaMv+TB4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=tFnhBXUBBS1/HbTjbSyLd+NmsWN4GS9pvs2uAgCjM s0=; b=QlJbRKwlQ89KaOgzaB94vGceGj+gpSQ4XGCPAJTlbuLqmjIVfESf+qECi Jy88+Lsu1maELL/nKYaOr/ekWcZtOLxUrZx6H/iW23+/i1a9ojiB9dL/yA0pUlOZ nmVwkCqlYkIZ4rQd1cmDw2uMO0ABxBlz/gfbScKofsyOlZHGZZnRdyU6Hlr5sPiv CAVVznoMjv1vgOTZbovs5pdnGmK7+EOT6DW6uOVvSPKtjCpL7WcJQi7WjvWKsi/m O9MpNZlb0TRIPNefrDg0pGC99HfGTG9Uw+/nYCTeNu5nWyl7IR7u8qwn0z+r8NY0 WuhQ2zHyw4RvgX1ciKH/+M37NW+LA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrtddtgdektdculddtuddrgedutddrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecufghrlhcuvffnffculd egmdenucfjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhep fdflrghsohhnuceurghrsghivghrfdcuoehjrghsohhnsegtohhrrhhuphhtvggurdhioh eqnecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgpdhkvgihsggrshgvrdhiohdpvhgr shdrthhomhhskhdrrhhunecurfgrrhgrmhepmhgrihhlfhhrohhmpehjrghsohhnsegtoh hrrhhuphhtvggurdhiohenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 056607C1BF; Tue, 2 Apr 2019 12:23:47 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-329-gf4aae99-fmstable-20190329v1 Mime-Version: 1.0 X-Me-Personality: 64405576 Message-Id: <1c80a14e-eb1e-4d95-b74a-337f20573189@www.fastmail.com> In-Reply-To: References: <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <20190303032918.GA60561@admin.sibptus.ru> Date: Tue, 02 Apr 2019 12:23:46 -0400 From: "Jason Barbier" To: freebsd-virtualization@freebsd.org Subject: Re: Windows 2019 server Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: C50F56C3EE X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=corrupted.io header.s=mesmtp header.b=fz2Xg29a; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=QlJbRKwl; dmarc=pass (policy=none) header.from=corrupted.io; spf=pass (mx1.freebsd.org: domain of jason@corrupted.io designates 66.111.4.26 as permitted sender) smtp.mailfrom=jason@corrupted.io X-Spamd-Result: default: False [-6.45 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[corrupted.io:s=mesmtp,messagingengine.com:s=fm2]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(-3.40)[ip: (-8.95), ipnet: 66.111.4.0/24(-4.59), asn: 11403(-3.38), country: US(-0.06)]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[corrupted.io:+,messagingengine.com:+]; DMARC_POLICY_ALLOW(-0.50)[corrupted.io,none]; MX_GOOD(-0.01)[aspmx.l.google.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,aspmx.l.google.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,aspmx.l.google.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com]; NEURAL_HAM_SHORT(-0.95)[-0.950,0]; RCVD_IN_DNSWL_LOW(-0.10)[26.4.111.66.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; MID_RHS_WWW(0.50)[] 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: Tue, 02 Apr 2019 16:23:51 -0000 happen to catch a stack trace for the crash? --- Jason Barbier | E: jason@corrupted.io=20 GPG: 0x40B8FA1D72EF0D89 (https://keybase.io/kusuriya) On Tue, Apr 2, 2019, at 9:05 AM, Michael wrote: > Hi, > I just tried on FreeBSD12 and Windows10, bhyve crashes when loading th= e=20 > virtstor driver. >=20 >=20 > Am 2. April 2019 16:56:13 MESZ schrieb Nick Wolff : > >There is paravirtulized support in FreeBSD 11.2 and 12 but you need t= o > >sideload the virtio drivers into windows. Sadly microsoft doesn't shi= p > >with > >them even with how "cloud" focused they are. Ahci-hd will allow you t= o > >get > >around this. I know we had some restrictions in the past on needing > >specific virt-io drivers for windows I'm not sure if that is fixed no= w. > >I > >think nvme paravirtual might also just work with windows but haven't > >confirmed that lately. > > > >On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov > >wrote: > > > >> Jason Tubnor wrote: > >> > > >> > > Which kind of storage did you present to the Windows 2019 guest= , > >> > > paravirtualized or ahcd-hd ? > >> > > >> > ahci-hd is what you want with bhyve and uefi > >> > >> Still no paravirtualized disks support for Windows guests, even in > >> FreeBSD 12? How sad. > >> > >> -- > >> Victor Sudakov, VAS4-RIPE, VAS47-RIPN > >> 2:5005/49@fidonet http://vas.tomsk.ru/ > >> > >_______________________________________________ > >freebsd-virtualization@freebsd.org mailing list > >https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > >To unsubscribe, send any mail to > >"freebsd-virtualization-unsubscribe@freebsd.org" >=20 > Gru=C3=9F > ---=20 > Michael > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to=20 > "freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@freebsd.org Tue Apr 2 19: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 BF76015706C8 for ; Tue, 2 Apr 2019 19:06:57 +0000 (UTC) (envelope-from darkfiberiru@gmail.com) Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75DD272D9B for ; Tue, 2 Apr 2019 19:06:56 +0000 (UTC) (envelope-from darkfiberiru@gmail.com) Received: by mail-ot1-x330.google.com with SMTP id u15so13019524otq.10 for ; Tue, 02 Apr 2019 12: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=rFhDNJKc37t+A5O0M1un4YpfRkZv3DdNd8dv+QZ2YhQ=; b=niLKTsnANxov+K0NC439DBavqTcFZVzUOTNm8CLBHutj8TEG0oSYH29o6DaJ74Dvzf iDSzUrep/XKiKfix5KmqpEDGlERD97CnwUV7aYf5aB5Svj8o63BmcnAfCp9CGZr4BGoC 5UBuMByoBVZA08Mmanj03Ac08muYEi3duA59TL6cN/g//0PmmtR5aal8kQ+tSbh96SKC 2+yUo0YtXYxrQK4YuxRbP/GyZWMHqh2kqolt8txjil1koYbvSFRFuc9b8qgpB9hb9Wkh At33vpZAyx8Lt4jKqaze0PK2/Ddgl7ZKtGAFbp7I8rkjkwiBBZE1MCD+b88U0/uSoyuH LZfg== 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=rFhDNJKc37t+A5O0M1un4YpfRkZv3DdNd8dv+QZ2YhQ=; b=RXlFCEn9zMnLrSCbsK2sU36abbOtZ+GjDuERhOMYU4fpmUudJrx4QyIGS9OCAaqa/U o7Gj9I3NqUNkZJnJsB7eKTgISYBtbTaRpU/vgbzguqNsv9QoiejzrtatKZCRotHNdmbX 9z2vWPISRxDGLB4J9g2B9gNZ8gjGwvKxx+f+om3MhbcccVxSCf0D+jtKSdLSZ8VLFLMb D0KXnGVx58MqLejfe8uZAhcmPDu9LjjzYJ0g6WckxuyaqtMi1OA9nP9vJYJuFs/FKMKi jgoc5eVGltEK91h08k3BEwgdraOvQr7OS+3kXXYZd5VERZke7d3PL391eowaT/42P5MG EVIQ== X-Gm-Message-State: APjAAAXqtlOvOzL6mQzqZLTqinnJV2443bkSqtv8wzt9c4Xr8tW5znFu jtBNSQQn62ZRsqV8g+JTQfikk2zh+9n+Gx2a4ZU/Hk2+ X-Google-Smtp-Source: APXvYqyvcK2fUsa9B8I+ZiGWpKUSP333UYgRV4mMVh/6L9nMGHCrXQmFAxuCdypYy4d+pyNfJIxXHDdXnamqSLvtaow= X-Received: by 2002:a9d:5d0b:: with SMTP id b11mr29635663oti.80.1554232015581; Tue, 02 Apr 2019 12:06:55 -0700 (PDT) MIME-Version: 1.0 References: <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <20190303032918.GA60561@admin.sibptus.ru> <1c80a14e-eb1e-4d95-b74a-337f20573189@www.fastmail.com> In-Reply-To: <1c80a14e-eb1e-4d95-b74a-337f20573189@www.fastmail.com> From: Nick Wolff Date: Tue, 2 Apr 2019 15:06:57 -0400 Message-ID: Subject: Re: Windows 2019 server To: Jason Barbier Cc: freebsd-virtualization@freebsd.org X-Rspamd-Queue-Id: 75DD272D9B X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=niLKTsnA; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of darkfiberiru@gmail.com designates 2607:f8b0:4864:20::330 as permitted sender) smtp.mailfrom=darkfiberiru@gmail.com X-Spamd-Result: default: False [-6.76 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.977,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[0.3.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.78)[ip: (-8.73), ipnet: 2607:f8b0::/32(-2.93), asn: 15169(-2.17), country: US(-0.06)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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: Tue, 02 Apr 2019 19:06:58 -0000 Micheal, Would you mind trying with https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-vi= rtio/virtio-win-0.1.118-1/ That is the iso I've used in the past with newer drivers failing(I don't think it caused a panic though when I dealt with it) Thanks, Nick Wolff On Tue, Apr 2, 2019 at 12:24 PM Jason Barbier wrote: > happen to catch a stack trace for the crash? > > --- > Jason Barbier | E: jason@corrupted.io > GPG: 0x40B8FA1D72EF0D89 (https://keybase.io/kusuriya) > > On Tue, Apr 2, 2019, at 9:05 AM, Michael wrote: > > Hi, > > I just tried on FreeBSD12 and Windows10, bhyve crashes when loading the > > virtstor driver. > > > > > > Am 2. April 2019 16:56:13 MESZ schrieb Nick Wolff < > darkfiberiru@gmail.com>: > > >There is paravirtulized support in FreeBSD 11.2 and 12 but you need to > > >sideload the virtio drivers into windows. Sadly microsoft doesn't ship > > >with > > >them even with how "cloud" focused they are. Ahci-hd will allow you to > > >get > > >around this. I know we had some restrictions in the past on needing > > >specific virt-io drivers for windows I'm not sure if that is fixed now= . > > >I > > >think nvme paravirtual might also just work with windows but haven't > > >confirmed that lately. > > > > > >On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov > > >wrote: > > > > > >> Jason Tubnor wrote: > > >> > > > >> > > Which kind of storage did you present to the Windows 2019 guest, > > >> > > paravirtualized or ahcd-hd ? > > >> > > > >> > ahci-hd is what you want with bhyve and uefi > > >> > > >> Still no paravirtualized disks support for Windows guests, even in > > >> FreeBSD 12? How sad. > > >> > > >> -- > > >> Victor Sudakov, VAS4-RIPE, VAS47-RIPN > > >> 2:5005/49@fidonet http://vas.tomsk.ru/ > > >> > > >_______________________________________________ > > >freebsd-virtualization@freebsd.org mailing list > > >https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > >To unsubscribe, send any mail to > > >"freebsd-virtualization-unsubscribe@freebsd.org" > > > > Gru=C3=9F > > --- > > Michael > > _______________________________________________ > > freebsd-virtualization@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to > > "freebsd-virtualization-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@freebsd.org Tue Apr 2 21:53:47 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 1AF36155014A for ; Tue, 2 Apr 2019 21:53:47 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D86EB82716 for ; Tue, 2 Apr 2019 21:53:45 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-oi1-f173.google.com with SMTP id j132so11867595oib.2 for ; Tue, 02 Apr 2019 14:53:45 -0700 (PDT) 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=d1zrAniPcdh614Jy27JnWG8h4vS51ZjT6Bax/QPNcto=; b=B6OnL1mwAoSJKfriX4Opw3cGe674amyM+2vOYknsE+MrdxQq5geIFS7s8hBX+/Wbay yos0K3H64qAMLHp7uOJLnf/RKkH05qt2JuK+xQDGNGAyxl/C0k134mFfj3MmkuSTPcc/ Uqnnq/2yj5ykt9X5Hc0JAz4oBBtW4L4vFUPQ4EvKfT4qLy8oPqB+ZwfseFfq9iC+rBuQ hYVY48zgO3xwHsn9inJf98m8qyqh7MNTiIqcBuNu9B26pWhs5arbyJch5MjTdBcbwPyt aN7dBbSA8VXr2IyfyAgxQqnDCYIedkhIigOLf3T7vUo2Gff3+zQh48TP/ZTDGL3YZxGE ROZg== X-Gm-Message-State: APjAAAWeD3lxPLk8EhD5aIXprthzoqgX42sAtx+b6fgNjd3GVQCBuXGQ HmS+lNufNRZvt/C9IiyvbTz4JoFeMpRKC9uvExw= X-Google-Smtp-Source: APXvYqzA/AISkwxg8g8Ag59shs97/hYvWHNkWFPBpqQj6ssdYdNrBO0JaesWn/6Eib6tdtUiX1PrO4G9qQP/voIPhIw= X-Received: by 2002:aca:5358:: with SMTP id h85mr18876874oib.98.1554241671050; Tue, 02 Apr 2019 14:47:51 -0700 (PDT) MIME-Version: 1.0 References: <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <20190303032918.GA60561@admin.sibptus.ru> In-Reply-To: From: Jason Tubnor Date: Wed, 3 Apr 2019 08:47:39 +1100 Message-ID: Subject: Re: Windows 2019 server To: Nick Wolff Cc: Victor Sudakov , "freebsd-virtualization@freebsd.org" X-Rspamd-Queue-Id: D86EB82716 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of jtubnor@gmail.com designates 209.85.167.173 as permitted sender) smtp.mailfrom=jtubnor@gmail.com X-Spamd-Result: default: False [-3.93 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; DMARC_NA(0.00)[tubnor.net]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.70)[-0.695,0]; RCVD_IN_DNSWL_NONE(0.00)[173.167.85.209.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; FORGED_SENDER(0.30)[jason@tubnor.net,jtubnor@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[jason@tubnor.net,jtubnor@gmail.com]; IP_SCORE(-1.22)[ipnet: 209.85.128.0/17(-3.87), asn: 15169(-2.17), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] 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: Tue, 02 Apr 2019 21:53:47 -0000 On Wed, 3 Apr 2019 at 01:56, Nick Wolff wrote: > > specific virt-io drivers for windows I'm not sure if that is fixed now. I > think nvme paravirtual might also just work with windows but haven't > confirmed that lately. > > Initial testing with some out of tree patches has fixed issues with NVMe and Windows, current snaps/stable don't work with Windows and NVMe. They should be imported shortly. Cheers > On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov wrote: > > > Jason Tubnor wrote: > > > > > > > Which kind of storage did you present to the Windows 2019 guest, > > > > paravirtualized or ahcd-hd ? > > > > > > ahci-hd is what you want with bhyve and uefi > > > > Still no paravirtualized disks support for Windows guests, even in > > FreeBSD 12? How sad. > > > > -- > > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > > 2:5005/49@fidonet http://vas.tomsk.ru/ > > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > -- "If my calculations are correct, when this baby hits 88MPH, you're gonna to see some serious shit" - Emmett "Doc" Brown From owner-freebsd-virtualization@freebsd.org Wed Apr 3 00:35:28 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 A50CD15549DC for ; Wed, 3 Apr 2019 00:35:28 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [65.103.231.193]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7820D87D70 for ; Wed, 3 Apr 2019 00:35:27 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 13C6ACB612 for ; Tue, 2 Apr 2019 18:36:12 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BPNOFg8z1FJy for ; Tue, 2 Apr 2019 18:36:11 -0600 (MDT) Received: from photon.int.bluestop.org (unknown [65.103.231.197]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA for ; Tue, 2 Apr 2019 18:36:11 -0600 (MDT) To: freebsd-virtualization@freebsd.org From: Rebecca Cran Subject: Debugging UEFI code in Bhyve Message-ID: <5554d42f-5186-4b52-cfa2-0a3158d65df4@bluestop.org> Date: Tue, 2 Apr 2019 18:35:24 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 7820D87D70 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.99 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(-2.99)[ip: (-9.88), ipnet: 65.100.0.0/14(-4.90), asn: 209(-0.09), country: US(-0.06)]; MX_GOOD(-0.01)[cached: mail.bluestop.org]; DKIM_TRACE(0.00)[bluestop.org:+]; DMARC_POLICY_ALLOW(-0.50)[bluestop.org,quarantine]; NEURAL_HAM_SHORT(-0.99)[-0.994,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:209, ipnet:65.100.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[] 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: Wed, 03 Apr 2019 00:35:28 -0000 I was wondering, has anyone done any work on supporting debugging UEFI code under Bhyve? If not, I can take a look at adapting DebugPkg (https://code.bluestop.org/w/tianocore/debugging-with-gdb/). -- Rebecca Cran From owner-freebsd-virtualization@freebsd.org Wed Apr 3 00:47:12 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 60FE51554E8D for ; Wed, 3 Apr 2019 00:47:12 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 15E668832D for ; Wed, 3 Apr 2019 00:47:10 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: by mail-lj1-x233.google.com with SMTP id f23so13266269ljc.0 for ; Tue, 02 Apr 2019 17:47:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=8fVFKVAMP+TAM/EyAbk2RuyLHEgikw41XIVp2ZkBGp8=; b=linvsBRTYq014ZuBQJLGOYuaVSIWgN+Qj/AGaxdc/+CNkIAqPjGwy8/ZxI84JYnN9p TRTaNrKsxjj/ZJjb5pq8pACZ/eEEINYMNoNBcztssOy5uUwFHisumKQY/iF0fNky6IRc g3yM3O1Bd3sBoaL58VtH8eJsUKcwnQDF0Pb6Il5dLtRnGe8kCAQat/SgfgasWUr/a7fd IwAIl7laOtNaJ3zwVatI3QV/JiU9ml+c3BJXeK6IiKOGSCwRgtjErSbO7DKW5YAJpk3O EjzSrNTUaIrMPWZBvXFm/McOuVwZboPbNsGoV7jKl6/RESv/3AHkO8cGOCLEev4nOE5U 39VQ== 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:reply-to :from:date:message-id:subject:to:cc; bh=8fVFKVAMP+TAM/EyAbk2RuyLHEgikw41XIVp2ZkBGp8=; b=C7P9PNt/XL4Tu4+zylaxsck7N8EjHEy+bSFAWT+F7L9eajm6Nz68HBOH8GrdBq3tsY EXTXNSP/pf/iL2bCEDZblmk/+y+fuu1fE3iyn+vogyJSN6xLsQPCy7oP6uRMB5N39jUN GQTOmV6CtjvArk4NxPClynI10x1pA317DEMPqlyIp5MCCgTbTUOKP/saqWXlcaZsbAX6 BS19wayHbjBCFYRDbEW9YHz0Q4waf1XU3Afjudn3+9cmok+i8rgemsFky7XGNnhRVH1Q HSX27RVmIHa4TxcBFX7ea4tbZHRG+VOO1kfeeAwl/ZTZLlw9J7SEE9Un1gwjsdbEMyBr xv+w== X-Gm-Message-State: APjAAAX7iG1AdB3HjxJuXgFTSw1saAAE1TwpQcnd+nQRbkYTUVFXmYbU StwfwQwuTfiuq6nRcTlOMW7Kh+/bg/dh8+0CKKn0tw== X-Google-Smtp-Source: APXvYqwn6PmHwm8woRsejJFGEw+8b6DkJ87ZVXKZUHsJM4rXNSQqKKeAWObZmtpUosRh5ICi4hWl+qHMCNE55OlZxp0= X-Received: by 2002:a2e:8888:: with SMTP id k8mr21165914lji.43.1554252428689; Tue, 02 Apr 2019 17:47:08 -0700 (PDT) MIME-Version: 1.0 References: <5554d42f-5186-4b52-cfa2-0a3158d65df4@bluestop.org> In-Reply-To: <5554d42f-5186-4b52-cfa2-0a3158d65df4@bluestop.org> Reply-To: araujo@freebsd.org From: Marcelo Araujo Date: Wed, 3 Apr 2019 08:46:58 +0800 Message-ID: Subject: Re: Debugging UEFI code in Bhyve To: Rebecca Cran Cc: freebsd-virtualization@freebsd.org X-Rspamd-Queue-Id: 15E668832D X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=linvsBRT; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of araujobsdport@gmail.com designates 2a00:1450:4864:20::233 as permitted sender) smtp.mailfrom=araujobsdport@gmail.com X-Spamd-Result: default: False [-6.72 / 15.00]; HAS_REPLYTO(0.00)[araujo@freebsd.org]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.94)[-0.937,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.3.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.77)[ip: (-9.25), ipnet: 2a00:1450::/32(-2.37), asn: 15169(-2.17), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] 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: Wed, 03 Apr 2019 00:47:12 -0000 On Wed, Apr 3, 2019, 8:35 AM Rebecca Cran via freebsd-virtualization < freebsd-virtualization@freebsd.org wrote: > I was wondering, has anyone done any work on supporting debugging UEFI > code under Bhyve? If not, I can take a look at adapting DebugPkg > (https://code.bluestop.org/w/tianocore/debugging-with-gdb/). > > > > -- > Rebecca Cran > > > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > Hi Rebecca, That would be super helpful, I did some debugs on edk2 in the past with virtio-scsi and virtio-nvme, it wasn't user friendly, mostly I needed to put edk2's printf all over the place and capture it via console to be able to debug boot issues with those two drivers. Would be great to have a debug method on edk2 and perhaps a howto with examples how to debug it. Best, > From owner-freebsd-virtualization@freebsd.org Wed Apr 3 08:24:19 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 A079D1563CA0 for ; Wed, 3 Apr 2019 08:24:19 +0000 (UTC) (envelope-from Michael@reifenberger.com) Received: from app.eeeit.de (app.eeeit.de [188.68.43.176]) (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 E7BE36B9D4 for ; Wed, 3 Apr 2019 08:24:17 +0000 (UTC) (envelope-from Michael@reifenberger.com) Received: from localhost (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: mike@reifenberger.com) by app.eeeit.de (Postfix) with ESMTPSA id 292DA7A19B; Wed, 3 Apr 2019 10:24:15 +0200 (CEST) Received: from ppp-93-104-73-164.dynamic.mnet-online.de (ppp-93-104-73-164.dynamic.mnet-online.de [93.104.73.164]) by app.eeeit.de (Horde Framework) with HTTPS; Wed, 03 Apr 2019 08:24:15 +0000 Date: Wed, 03 Apr 2019 08:24:15 +0000 Message-ID: <20190403082415.Horde.2jD2Fjwd-E1Bk1_ZUlCRJwn@app.eeeit.de> From: Michael Reifenberger To: Nick Wolff Cc: Jason Barbier , freebsd-virtualization@freebsd.org Subject: Re: Windows 2019 server References: <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <20190303032918.GA60561@admin.sibptus.ru> <1c80a14e-eb1e-4d95-b74a-337f20573189@www.fastmail.com> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: E7BE36B9D4 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.22 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.77)[0.768,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[reifenberger.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.85)[0.855,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: app.eeeit.de]; NEURAL_SPAM_LONG(0.98)[0.984,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[164.73.104.93.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:197540, ipnet:188.68.32.0/20, country:DE]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(0.73)[asn: 197540(3.63), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[] 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: Wed, 03 Apr 2019 08:24:19 -0000 Hi, Zitat von Nick Wolff : > Micheal, > > Would you mind trying with > https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.118-1/ > > > That is the iso I've used in the past with newer drivers failing(I don't > think it caused a panic though when I dealt with it) > Trying to use this ISO for loading the driver during the installation doesn't lead to a panic but aborts the guest while the driver gets loaded: Apr. 03 10:11:11: initialising Apr. 03 10:11:11: [loader: uefi] Apr. 03 10:11:11: [cpu: 2] Apr. 03 10:11:11: [memory: 6G] Apr. 03 10:11:11: [hostbridge: standard] Apr. 03 10:11:11: [com ports: com1] Apr. 03 10:11:11: [uuid: a9656f03-7f7a-11e7-983e-98e7f4868540] Apr. 03 10:11:11: [utctime: yes] Apr. 03 10:11:11: [debug mode: no] Apr. 03 10:11:11: [primary disk: disk0] Apr. 03 10:11:11: [primary disk dev: zvol] Apr. 03 10:11:11: initialising network device tap0 Apr. 03 10:11:11: adding tap0 -> bridge1 (private addm) Apr. 03 10:11:11: bring up tap0 -> bridge1 (private addm) Apr. 03 10:11:11: booting Apr. 03 10:11:11: [bhyve options: -c 2 -m 6G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U a9656f03-7f7a-11e7-983e-98e7f4868540 -u] Apr. 03 10:11:11: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/dev/zvol/zdata/VM/w10e-ltsb-2/disk0 -s 5:0,nvme,/dev/zvol/zdata/VM/w10e-ltsb-2/disk1 -s 6:0,ahci-cd,/VM2/w10e-ltsb-2/disk2.img -s 7:0,virtio-net,tap0,mac=58:9c:fc:04:eb:ed -s 8:0,fbuf,tcp=0.0.0.0:5900,w=1600,h=900 -s 9:0,xhci,tablet] Apr. 03 10:11:11: [bhyve console: -l com1,/dev/nmdm-w10e-ltsb-2.1A] Apr. 03 10:11:11: [bhyve iso device: -s 3:0,ahci-cd,/VM/.iso/en_windows_10_enterprise_ltsc_2019_x64_dvd_be3c8ffb.iso,ro] Apr. 03 10:11:11: starting bhyve (run 1) Apr. 03 10:13:10: bhyve exited with status 134 Apr. 03 10:13:10: destroying network device tap0 Apr. 03 10:13:10: stopped The relevant entries of the config file are: ... cpu=2 memory=6G network0_type="virtio-net" network0_switch="private" disk0_type="virtio-blk" disk0_dev="zvol" disk0_name="disk0" disk1_type="nvme" disk1_dev="zvol" disk1_name="disk1" disk2_type="ahci-cd" disk2_name="disk2.img" ... (disk0 is the one I'm trying to use here, disk2 is the ISO) Greetings --- mike Gruß --- Michael Reifenberger From owner-freebsd-virtualization@freebsd.org Wed Apr 3 08:57:25 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 A51A61564DC9 for ; Wed, 3 Apr 2019 08:57:25 +0000 (UTC) (envelope-from Michael@reifenberger.com) Received: from app.eeeit.de (app.eeeit.de [188.68.43.176]) (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 5F5E46D724 for ; Wed, 3 Apr 2019 08:57:23 +0000 (UTC) (envelope-from Michael@reifenberger.com) Received: from localhost (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: mike@reifenberger.com) by app.eeeit.de (Postfix) with ESMTPSA id A866E7A53E; Wed, 3 Apr 2019 10:57:21 +0200 (CEST) Received: from ppp-93-104-73-164.dynamic.mnet-online.de (ppp-93-104-73-164.dynamic.mnet-online.de [93.104.73.164]) by app.eeeit.de (Horde Framework) with HTTPS; Wed, 03 Apr 2019 08:57:21 +0000 Date: Wed, 03 Apr 2019 08:57:21 +0000 Message-ID: <20190403085721.Horde.uIbnPqGDk6SPyyiWNkI_sSK@app.eeeit.de> From: Michael Reifenberger To: Jason Tubnor Cc: Nick Wolff , freebsd-virtualization@freebsd.org Subject: Re: Windows 2019 server References: <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <20190303032918.GA60561@admin.sibptus.ru> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 5F5E46D724 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.07 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.57)[0.566,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[reifenberger.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.90)[0.900,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: app.eeeit.de]; NEURAL_SPAM_LONG(0.99)[0.991,0]; R_SPF_NA(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[164.73.104.93.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:197540, ipnet:188.68.32.0/20, country:DE]; FREEMAIL_CC(0.00)[gmail.com]; IP_SCORE(0.72)[asn: 197540(3.62), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[] 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: Wed, 03 Apr 2019 08:57:26 -0000 Hi, do you mean: https://reviews.freebsd.org/D19695 if yes I can confirm that with the patch I get ltsc-2019 installed and running. Greetings --- mike Zitat von Jason Tubnor : > On Wed, 3 Apr 2019 at 01:56, Nick Wolff wrote: > >> >> specific virt-io drivers for windows I'm not sure if that is fixed now. I >> think nvme paravirtual might also just work with windows but haven't >> confirmed that lately. >> >> > Initial testing with some out of tree patches has fixed issues with NVMe > and Windows, current snaps/stable don't work with Windows and NVMe. > > They should be imported shortly. > > Cheers > > >> On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov wrote: >> >> > Jason Tubnor wrote: >> > > >> > > > Which kind of storage did you present to the Windows 2019 guest, >> > > > paravirtualized or ahcd-hd ? >> > > >> > > ahci-hd is what you want with bhyve and uefi >> > >> > Still no paravirtualized disks support for Windows guests, even in >> > FreeBSD 12? How sad. >> > >> > -- >> > Victor Sudakov, VAS4-RIPE, VAS47-RIPN >> > 2:5005/49@fidonet http://vas.tomsk.ru/ >> > >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to " >> freebsd-virtualization-unsubscribe@freebsd.org" >> > > > -- > "If my calculations are correct, when this baby hits 88MPH, you're gonna to > see some serious shit" - Emmett "Doc" Brown > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org" Gruß --- Michael Reifenberger From owner-freebsd-virtualization@freebsd.org Wed Apr 3 16:36:26 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 06CBE1572FE9 for ; Wed, 3 Apr 2019 16:36:26 +0000 (UTC) (envelope-from vhpc.dist@gmail.com) Received: from mail-it1-x134.google.com (mail-it1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E6D6B89D54 for ; Wed, 3 Apr 2019 16:36:24 +0000 (UTC) (envelope-from vhpc.dist@gmail.com) Received: by mail-it1-x134.google.com with SMTP id x132so10109160itf.2 for ; Wed, 03 Apr 2019 09:36:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=KCokFmSrK259FI4hG1RTlUnW6nI6rAmQqNLgIppWW3Q=; b=QL8PgAyzQoqRe5g2vW+ednm/t35gm14CQLYuYXZagIQ21exF1C5f0j+nKctmk1knyi EnsQLEPzONz9JlAyAHNOmvOXK7rdpceOy/u76b+AZ4FgbFMzLeDfOJB0CgLNyMcTRaZ6 +NhR6LcQwxBY4Atg+D6hAKx0KS1SWquzd5SRv6ziuwAKcH15ZBGNFf/wyqUdpKLkC6VJ IsSYuup1kXdocLi6omtrn/3zPS1vDqBKYeGoQrcmr4RW09/yrIVHsKa0dIfHyCVLTuJ4 qfqxP9Z2kNYHMuVpL94dBaEl1fGzcmhWc52rlU5FGGfrHxrL0y8HlFl+vV3V6H4eycrx VHsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=KCokFmSrK259FI4hG1RTlUnW6nI6rAmQqNLgIppWW3Q=; b=UfoOfp79LLbm0aztUi3qC58d9bx873gKvPXcu+S33L12ctDIGj0q1fH/gt8IDmhEf5 uEO9sVucuaAxn/lR0CQsO1xFFLRTI1Pq01ALQd6ClXUyvvGI6KQ8hvOeSDqIw4Yi9xSM vc3H0/MWJenKBkpeQ72Er6eaf1TrOIu7POcCQDNpD/s+VkT5qWyPK40AKqU0TleC8HQH /2LTUxloKTWTAyCZKL8CBSLHpZlA4uF5AQskvkKw4tjbQVDQnAuwNfGlisMLVEjFCAIn rDUzlSUAPUolOpsaMwfww2eAS+JSAsY/BB37ZKPl5RcJGgUvBRy7+eYCKOkqqIwvT9yb hGKg== X-Gm-Message-State: APjAAAUJx34FrdZuaM6CAThtRL8FBqkt4PWpDXFh+XSnkXSPUkQQeeOf LVex5w691K5lvt8YH1BZ7drAIlCk9ssPPCL+DLh5/zH5RlU= X-Google-Smtp-Source: APXvYqxlUYEHrP5F1bcZl1e+SeK96XsxcxRRhQ8jwXW3wxoC6I/WOxQgH7p4XyWJxcAHU1Mtm18fuZee32YmaorcTVg= X-Received: by 2002:a24:3dc7:: with SMTP id n190mr1027078itn.62.1554309384111; Wed, 03 Apr 2019 09:36:24 -0700 (PDT) MIME-Version: 1.0 From: VHPC 19 Date: Wed, 3 Apr 2019 18:36:11 +0200 Message-ID: Subject: CfP VHPC19: HPC Virtualization-Containers: Paper due May 1, 2019 (extended) To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: E6D6B89D54 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=QL8PgAyz; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of vhpcdist@gmail.com designates 2607:f8b0:4864:20::134 as permitted sender) smtp.mailfrom=vhpcdist@gmail.com X-Spamd-Result: default: False [-6.73 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.88)[-0.881,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-2.84)[ip: (-9.04), ipnet: 2607:f8b0::/32(-2.91), asn: 15169(-2.16), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[4.3.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] 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: Wed, 03 Apr 2019 16:36:26 -0000 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CALL FOR PAPERS 14th Workshop on Virtualization in High=C2=AD-Performance Cloud Computing (VHPC '19) held in conjunction with the International Supercomputing Conference - High Performance, June 16-20, 2019, Frankfurt, Germany. (Springer LNCS Proceedings) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Date: June 20, 2019 Workshop URL: http://vhpc.org Paper Submission Deadline: May 1, 2019 (extended) Springer LNCS, rolling abstract submission Abstract/Paper Submission Link: https://edas.info/newPaper.php?c=3D25685 Call for Papers Containers and virtualization technologies constitute key enabling factors for flexible resource management in modern data centers, and particularly in cloud environments. Cloud providers need to manage complex infrastructures in a seamless fashion to support the highly dynamic and heterogeneous workloads and hosted applications customers deploy. Similarly, HPC environments have been increasingly adopting techniques that enable flexible management of vast computing and networking resources, close to marginal provisioning cost, which is unprecedented in the history of scientific and commercial computing. Various virtualization-containerization technologies contribute to the overall picture in different ways: machine virtualization, with its capability to enable consolidation of multiple under=C2=ADutilized servers with heterogeneous software and operating systems (OSes), and its capability to live=C2=AD-migrate a fully operating virtual machine (VM) with a very short downtime, enables novel and dynamic ways to manage physical servers; OS-=C2=ADlevel virtualization (i.e., containerization), with its capability to isolate multiple user=C2=AD-space environments and to allow for their co=C2=ADexistence within the same OS kernel, promises to provide many of the advantages of machine virtualization with high levels of responsiveness and performance; lastly, unikernels provide for many virtualization benefits with a minimized OS/library surface. I/O Virtualization in turn allows physical network interfaces to take traffic from multiple VMs or containers; network virtualization, with its capability to create logical network overlays that are independent of the underlying physical topology is furthermore enabling virtualization of HPC infrastructures. Publication Accepted papers will be published in a Springer LNCS proceedings volume. Topics of Interest The VHPC program committee solicits original, high-quality submissions related to virtualization across the entire software stack with a special focus on the intersection of HPC, containers-virtualization and the cloud. Major Topics: - HPC on Containers and VMs - Containerized applications with OS-level virtualization - Lightweight applications with Unikernels - HP-as-a-Service each major topic encompassing design/architecture, management, performance management, modeling and configuration/tooling: Design / Architecture: - Containers and OS-level virtualization (LXC, Docker, rkt, Singularity, Shifter, i.a.) - Hypervisor support for heterogeneous resources (GPUs, co-processors, FPGAs, etc.) - Hypervisor extensions to mitigate side-channel attacks ([micro-]architectural timing attacks, privilege escalation) - VM & Container trust and security models - Multi-environment coupling, system software supporting in-situ analysis with HPC simulation - Cloud reliability, fault-tolerance and high-availability - Energy-efficient and power-aware virtualization - Containers inside VMs with hypervisor isolation - Virtualization support for emerging memory technologies - Lightweight/specialized operating systems in conjunction with virtual machines - Hypervisor support for heterogeneous resources (GPUs, co-processors, FPGAs, etc.) - Novel unikernels and use cases for virtualized HPC environments - ARM-based hypervisors, ARM virtualization extensions Management: - Container and VM management for HPC and cloud environments - HPC services integration, services to support HPC - Service and on-demand scheduling & resource management - Dedicated workload management with VMs or containers - Workflow coupling with VMs and containers - Unikernel, lightweight VM application management - Environments and tools for operating containerized environments (batch, orchestration) - Novel models for non-HPC workload provisioning on HPC resources Performance Measurements and Modeling: - Performance improvements for or driven by unikernels - Optimizations of virtual machine monitor platforms and hypervisors - Scalability analysis of VMs and/or containers at large scale - Performance measurement, modeling and monitoring of virtualized/cloud workloads - Virtualization in supercomputing environments, HPC clusters, HPC in the cloud Configuration / Tooling: - Tool support for unikernels: configuration/build environments, debuggers, profilers - Job scheduling/control/policy and container placement in virtualized environments - Operating MPI in containers/VMs and Unikernels - Software defined networks and network virtualization - GPU virtualization operationalization The Workshop on Virtualization in High=C2=AD-Performance Cloud Computing (VHPC) aims to bring together researchers and industrial practitioners facing the challenges posed by virtualization in order to foster discussion, collaboration, mutual exchange of knowledge and experience, enabling research to ultimately provide novel solutions for virtualized computing systems of tomorrow. The workshop will be one day in length, composed of 20 min paper presentations, each followed by 10 min discussion sections, plus lightning talks that are limited to 5 minutes. Presentations may be accompanied by interactive demonstrations. Important Dates May 1, 2019 - Abstract/Paper extended submission deadline (Springer LNCS) May 20, 2019 - Acceptance notification June 20th, 2019 - Workshop Day July 10th, 2019 - Camera-ready version due Chair Michael Alexander (chair), University of Vienna, Austria Anastassios Nanos (co-=C2=ADchair), SunLight.io, UK Andrew Younge (co-chair), Sandia National Laboratories Program committee Stergios Anastasiadis, University of Ioannina, Greece Jakob Blomer, CERN, Europe Eduardo C=C3=A9sar, Universidad Autonoma de Barcelona, Spain Taylor Childers, Argonne National Laboratory, USA Stephen Crago, USC ISI, USA Tommaso Cucinotta, St. Anna School of Advanced Studies, Italy Christoffer Dall, Columbia University, USA Fran=C3=A7ois Diakhat=C3=A9, CEA, France Patrick Dreher, MIT, USA Kyle Hale, Northwestern University, USA Bob Killen, University of Michigan, USA Brian Kocoloski, Washington University, USA John Lange, University of Pittsburgh, USA Giuseppe Lettieri, University of Pisa, Italy Qing Liu, Oak Ridge National Laboratory, USA Nikos Parlavantzas, IRISA, France Kevin Pedretti, Sandia National Laboratories, USA Amer Qouneh, Western New England University, USA Carlos Rea=C3=B1o, Queen=E2=80=99s University Belfast, UK Borja Sotomayor, University of Chicago, USA Jonathan Sparks, Cray, USA Joe Stubbs, Texas Advanced Computing Center, USA Anata Tiwari, San Diego Supercomputer Center, USA Kurt Tutschku, Blekinge Institute of Technology, Sweden John Walters, USC ISI, USA Yasuhiro Watashiba, Osaka University, Japan Chao-Tung Yang, Tunghai University, Taiwan Na Zhang, VMware, USA Paper Submission-Publication Papers submitted to the workshop will be reviewed by at least two members o= f the program committee and external reviewers. Submissions should include abstract, keywords, the e-mail address of the corresponding author, and mus= t not exceed 10 pages, including tables and figures at a main font size no smaller than 11 point. Submission of a paper should be regarded as a commit= ment that, should the paper be accepted, at least one of the authors will regist= er and attend the conference to present the work. Accepted papers will be published in a Springer LNCS volume. The format must be according to the Springer LNCS Style. Initial submission= s are in PDF; authors of accepted papers will be requested to provide source files. Format Guidelines: ftp://ftp.springernature.com/cs-proceeding/llncs/llncs2e.zip Abstract, Paper Submission Link: https://edas.info/newPaper.php?c=3D25685 Lightning Talks Lightning Talks are non-paper track, synoptical in nature and are strictly limited to 5 minutes. They can be used to gain early feedback on ongoing research, for demonstrations, to present research results, early research ideas, perspectives and positions of interest to the community. Submit abst= ract via the main submission link. General Information The workshop is one day in length and will be held in conjunction with the International Supercomputing Conference - High Performance (ISC) 2019, June 16-20, Frankfurt, Germany. From owner-freebsd-virtualization@freebsd.org Wed Apr 3 20:49:30 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 89EA11553234 for ; Wed, 3 Apr 2019 20:49:30 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C2436D403 for ; Wed, 3 Apr 2019 20:49:29 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-ot1-f44.google.com with SMTP id u15so253179otq.10 for ; Wed, 03 Apr 2019 13:49:29 -0700 (PDT) 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=I/U+qrgrtYFt6Klibael9CRCn8pGlbHV2JulXnHsaHw=; b=HmdVeh38OPI5HF+qHbFg2KGPcf3cI4e6CiAlZo98M0Y0NWshfd6QyAdeZ2314cLiI5 ZhBw7lDyLVBUAiqPkZiJ7pyql/ZH7XPTEAY7oUIe7gLZJeNLNypc94blL+vl9BJWe6M5 2rxUwMFIbUwqOYp0o9McGh4jLz+zGeN1Qb3kGKmBleWWH+JB9EWtCTzYlEBoqxOM3D65 rp/qWmb3YU7NUa8rHoVTuEpLn9VaQx7YOy703lai+dH5TLsJ0r5zKAqXIgoT9ocWvlqf raWqUU6LMz8rKhaajmJdiAXabaLTXcQ1XszJ108Vm2BobBGQeCy2ggGOO5UGxCbduzxb Je+w== X-Gm-Message-State: APjAAAWPWKjN3SK3RKPBbTn0IvfF84BNGtMioT5QRkI2Mg+hrcPxa1Ar 1juHFJH05C1XU6ANM29jeAbQSmYqKl+2WrCj9veVFoNR X-Google-Smtp-Source: APXvYqwUUbboMAvPZfe1kKYhKS+Oxc90AggCxqAs74udCxhSwZqAS8bYcueSWylRP5S3ZMly1gPRHggwfDcYf/fL9VQ= X-Received: by 2002:a9d:30d8:: with SMTP id r24mr1453827otg.100.1554324562816; Wed, 03 Apr 2019 13:49:22 -0700 (PDT) MIME-Version: 1.0 References: <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <20190303032918.GA60561@admin.sibptus.ru> <20190403085721.Horde.uIbnPqGDk6SPyyiWNkI_sSK@app.eeeit.de> In-Reply-To: <20190403085721.Horde.uIbnPqGDk6SPyyiWNkI_sSK@app.eeeit.de> From: Jason Tubnor Date: Thu, 4 Apr 2019 07:49:11 +1100 Message-ID: Subject: Re: Windows 2019 server To: Michael Reifenberger Cc: Nick Wolff , "freebsd-virtualization@freebsd.org" X-Rspamd-Queue-Id: 9C2436D403 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of jtubnor@gmail.com designates 209.85.210.44 as permitted sender) smtp.mailfrom=jtubnor@gmail.com X-Spamd-Result: default: False [-4.32 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; DMARC_NA(0.00)[tubnor.net]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.99)[-0.990,0]; RCVD_IN_DNSWL_NONE(0.00)[44.210.85.209.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; FORGED_SENDER(0.30)[jason@tubnor.net,jtubnor@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[jason@tubnor.net,jtubnor@gmail.com]; IP_SCORE(-1.32)[ip: (-0.49), ipnet: 209.85.128.0/17(-3.87), asn: 15169(-2.16), country: US(-0.06)]; FREEMAIL_CC(0.00)[gmail.com] 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: Wed, 03 Apr 2019 20:49:30 -0000 On Wed, 3 Apr 2019 at 19:57, Michael Reifenberger wrote: > Hi, > do you mean: > https://reviews.freebsd.org/D19695 > if yes I can confirm that with the patch I get ltsc-2019 installed and > running. Yes, that is the patch. From owner-freebsd-virtualization@freebsd.org Wed Apr 3 23:36:54 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 B35AB1559012 for ; Wed, 3 Apr 2019 23:36:54 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9896972561 for ; Wed, 3 Apr 2019 23:36:53 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Wed, 03 Apr 2019 23:36:36 +0000 To: Robert Crowston From: Robert Crowston Cc: "freebsd-virtualization@freebsd.org" Reply-To: Robert Crowston Subject: Re: GPU passthrough: mixed success on Linux, not yet on Windows Message-ID: <_jA2UXvV5kqhYMOMU9WYEVi0YyChL0Z7YLfziC4KWkNfijzZxCbeuJEE7T7zV9aEIwH_HpEc-a_fjokPENr--i6JW6NpcDOCvsKYjpi5NXU=@protonmail.com> In-Reply-To: References: Feedback-ID: 2OVbcR1yHYpdkD8cgQllkFwcuMVZg_LiVMMPvptooFDfHD_03MuQO4ZaF626jWHZYFEhNR2cmIbZ53j4QGWMBQ==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.protonmail.ch X-Rspamd-Queue-Id: 9896972561 X-Spamd-Bar: ------- X-Spamd-Result: default: False [-7.80 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; DKIM_TRACE(0.00)[protonmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; MX_GOOD(-0.01)[cached: mailsec.protonmail.ch]; FREEMAIL_TO(0.00)[protonmail.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ASN(0.00)[asn:19905, ipnet:185.70.40.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[22.40.70.185.list.dnswl.org : 127.0.5.1]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=default]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.968,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-3.72)[ip: (-9.74), ipnet: 185.70.40.0/24(-4.90), asn: 19905(-3.92), country: US(-0.06)]; RCVD_TLS_ALL(0.00)[] 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: Wed, 03 Apr 2019 23:36:55 -0000 > The hack I had to make: I found that many instructions to access memory-m= apped PCI BARs are not being executed on the CPU in guest mode but are bein= g passed back for emulation in the hypervisor. Update on this: I found that by mapping the BARs within the lower 4 GB of t= he guest's address space I am able to start X under Linux without other wei= rd hacks. The size of the BAR that was causing difficulty is 128 MB. The vm= _map_pptdev_mmio() call apparently succeeds in mapping the memory range but= the processor then faults on any guest instruction that accesses this rang= e. You can change the memory region either by bumping the size of a "small req= uest" (initially 32 MB) in bhyve/pci_emul.c around line 638, or by tweaking= the value of the macro constant PCI_EMUL_MEMBASE64 in the same file. I als= o tried setting PCI_EMUL_MEMBASE64 to other low values (like 32 GB) but see= ms like it has to be below 4 GB for Linux to be happy. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Sunday, 17 March 2019 16:22, Robert Crowston via freebsd-virtualization = wrote: > Hi folks, this is my first post to the group. Apologies for length. > > I've been experimenting with GPU passthrough on bhyve. For background, th= e host system is FreeBSD 12.0-RELEASE on an AMD Ryzen 1700 CPU @ 3.8 GHz, 3= 2 GB of ECC RAM, with two nVidia GPUs. I'm working with a Linux Debian 9 gu= est and a Windows Server 2019 (desktop experience installed) guest. I also = have a USB controller passed-through for bluetooth and keyboard. > > With some unpleasant hacks I have succeeded in starting X on the Linux gu= est, passing-through an nVidia GT 710 under the nouveau driver. I can run t= he "mate" desktop and glxgears, both of which are smooth at 4K. The Unity H= eaven benchmark runs at an embarrassing 0.1 fps, and 2160p x264 video in VL= C runs at about 5 fps. Neither appears to be CPU-bound in the host or the g= uest. > > The hack I had to make: I found that many instructions to access memory-m= apped PCI BARs are not being executed on the CPU in guest mode but are bein= g passed back for emulation in the hypervisor. This causes an assertion to = fail inside passthru_write() in pci_passthru.c ["pi->pi_bar[baridx].type = =3D=3D PCIBAR_IO"] because it does not expect to perform memory-mapped IO f= or the guest. Examining the to-be-emulated instructions in vmexit_inst_emul= () {e.g., movl (%rdi), %eax}, they look benign to me, and I have no explana= tion for why the CPU refused to execute them in guest mode. > > As an amateur work-around, I removed the assertion and instead I obtain t= he desired offset into the guest's BAR, calculate what that guest address t= ranslates to in the host's address space, open(2) /dev/mem, mmap(2) over to= that address, and perform the write directly. I do a similar trick in pass= thru_read(). Ugly, slow, but functional. > > This code path is accessed continuously whether or not X is running, with= an increase in activity when running anything GPU-heavy. Always to bar 1, = and mostly around the same offsets. I added some logging of this event. It = runs at about 100 lines per second while playing video. An excerpt is: > ... > Unexpected out-of-vm passthrough write #492036 to bar 1 at offset 41100. > Unexpected out-of-vm passthrough write #492037 to bar 1 at offset 41100. > Unexpected out-of-vm passthrough read #276162 to bar 1 at offset 561280. > Unexpected out-of-vm passthrough write #492038 to bar 1 at offset 38028. > Unexpected out-of-vm passthrough write #492039 to bar 1 at offset 38028. > Unexpected out-of-vm passthrough read #276163 to bar 1 at offset 561184. > Unexpected out-of-vm passthrough read #276164 to bar 1 at offset 561184. > Unexpected out-of-vm passthrough read #276165 to bar 1 at offset 561184. > Unexpected out-of-vm passthrough read #276166 to bar 1 at offset 561184. > ... > > So my question here is, > > 1. How do I diagnose why the instructions are not being executed in gues= t mode? > > Some other problems: > > 2. Once the virtual machine is shut down, the passed-through GPU doesn't= get turned off. Whatever message was on the screen in the final throes of = Linux's shutdown stays there. Maybe there is a specific detach command whic= h bhyve or nouveau hasn't yet implemented? Alternatively, maybe I could exp= loit some power management feature to reset the card when bhyve exits. > 3. It is not possible to reboot the guest and then start X again without= an intervening host reboot. The text console works fine. Xorg.0.log has a = message like > (EE) [drm] Failed to open DRM device for pci:0000:00:06.0: -19 > (EE) open /dev/dri/card0: No such file or directory > dmesg is not very helpful either.[0] I suspect that this is related t= o problem (2). > > 4. There is a known bug in the version of the Xorg server that ships wit= h Debian 9, where the switch from an animated mouse cursor back to a static= cursor causes the X server to sit in a busy loop of gradually increasing s= tack depth, if the GPU takes too long to communicate with the driver.[1] Fo= r me, this consistently happens after I type my password into the Debian lo= gin dialog box and eventually (~ 120 minutes) locks up the host by eating a= ll the swap. A work-around is to replace the guest's animated cursors with = static cursors. The bug is fixed in newer versions of X, but I haven't test= ed whether their fix works for me yet. > 5. The GPU doesn't come to life until the nouveau driver kicks in. What = is special about the driver? Why doesn't the UEFI open the GPU and send it = output before the boot? Any idea if the problem is on the UEFI side or the = hypervisor side? > 6. On Windows, the way Windows probes multi-BAR devices seems to be inco= nsistent with bhyve's model for storing io memory mappings. Specifically, I= believe Windows assigns the 0xffffffff sentinel to all BARs on a device in= one shot, then reads them back and assigns the true addresses afterwards. = However, bhyve sees the multiple 0xffffffff assignments to different BARs a= s a clash and errors out on the second BAR probe. I removed most of the mmi= o_rb_tree error handling in mem.c and this is sufficient for Windows to boo= t, and detect and correctly identify the GPU. (A better solution might be t= o handle the initial 0xffffffff write as a special case.) I can then instal= l the official nVidia drivers without problem over Remote Desktop. However,= the GPU never springs into life: I am stuck with a "Windows has stopped th= is device because it has reported problems. (Code 43)" error in the device = manager, a blank screen, and not much else to go on. > > Is it worth me continuing to hack away at these problems---of course = I'm happy to share anything I come up with---or is there an official soluti= on to GPU support in the pipe about to make my efforts redundant :)? > > Thanks, > Robert Crowston. > > > Footnotes > > [0] Diff'ing dmesg after successful GPU initialization (+) and after fail= ure (-), and cutting out some lines that aren't relevant: > nouveau 0000:00:06.0: bios: version 80.28.a6.00.10 > +nouveau 0000:00:06.0: priv: HUB0: 085014 ffffffff (1f70820b) > nouveau 0000:00:06.0: fb: 1024 MiB DDR3 > @@ -466,24 +467,17 @@ > nouveau 0000:00:06.0: DRM: DCB conn 00: 00001031 > nouveau 0000:00:06.0: DRM: DCB conn 01: 00002161 > nouveau 0000:00:06.0: DRM: DCB conn 02: 00000200 > -nouveau 0000:00:06.0: disp: chid 0 mthd 0000 data 00000400 00001000 0000= 0002 > -nouveau 0000:00:06.0: timeout at /build/linux-UEAD6s/linux-4.9.144/drive= rs/gpu/drm/nouveau/nvkm/engine/disp/dmacgf119.c:88/gf119_disp_dmac_init()! > -nouveau 0000:00:06.0: disp: ch 1 init: c207009b > -nouveau: DRM:00000000:0000927c: init failed with -16 > -nouveau 0000:00:06.0: timeout at /build/linux-UEAD6s/linux-4.9.144/drive= rs/gpu/drm/nouveau/nvkm/engine/disp/dmacgf119.c:54/gf119_disp_dmac_fini()! > -nouveau 0000:00:06.0: disp: ch 1 fini: c2071088 > -nouveau 0000:00:06.0: timeout at /build/linux-UEAD6s/linux-4.9.144/drive= rs/gpu/drm/nouveau/nvkm/engine/disp/dmacgf119.c:54/gf119_disp_dmac_fini()! > -nouveau 0000:00:06.0: disp: ch 1 fini: c2071088 > +[drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > +[drm] Driver supports precise vblank timestamp query. > +nouveau 0000:00:06.0: DRM: MM: using COPY for buffer copies > +nouveau 0000:00:06.0: DRM: allocated 1920x1080 fb: 0x60000, bo ffff96fdb= 39a1800 > +fbcon: nouveaufb (fb0) is primary device > -nouveau 0000:00:06.0: timeout at /build/linux-UEAD6s/linux-4.9.144/drive= rs/gpu/drm/nouveau/nvkm/engine/disp/coregf119.c:187/gf119_disp_core_fini() > -nouveau 0000:00:06.0: disp: core fini: 8d0f0088 > -[TTM] Finalizing pool allocator > -[TTM] Finalizing DMA pool allocator > -[TTM] Zone kernel: Used memory at exit: 0 kiB > -[TTM] Zone dma32: Used memory at exit: 0 kiB > -nouveau: probe of 0000:00:06.0 failed with error -16 > +Console: switching to colour frame buffer device 240x67 > +nouveau 0000:00:06.0: fb0: nouveaufb frame buffer device > +[drm] Initialized nouveau 1.3.1 20120801 for 0000:00:06.0 on minor 0 > > [1] https://devtalk.nvidia.com/default/topic/1028172/linux/titan-v-ubuntu= -16-04lts-and-387-34-driver-crashes-badly/post/5230898/#5230898 > > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free= bsd.org" From owner-freebsd-virtualization@freebsd.org Wed Apr 3 23:41:47 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 1FD7615592FE for ; Wed, 3 Apr 2019 23:41:47 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch [185.70.40.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E736728DF for ; Wed, 3 Apr 2019 23:41:45 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Wed, 03 Apr 2019 23:41:36 +0000 To: Ruslan Bukin From: Robert Crowston Cc: "freebsd-virtualization@freebsd.org" Reply-To: Robert Crowston Subject: Re: GPU passthrough: mixed success on Linux, not yet on Windows Message-ID: In-Reply-To: <20190328220234.GA52232@bsdpad.com> References: <20190328220234.GA52232@bsdpad.com> Feedback-ID: 2OVbcR1yHYpdkD8cgQllkFwcuMVZg_LiVMMPvptooFDfHD_03MuQO4ZaF626jWHZYFEhNR2cmIbZ53j4QGWMBQ==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.protonmail.ch X-Rspamd-Queue-Id: 8E736728DF X-Spamd-Bar: ------- X-Spamd-Result: default: False [-7.83 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; FREEMAIL_FROM(0.00)[protonmail.com]; DKIM_TRACE(0.00)[protonmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; MX_GOOD(-0.01)[cached: mailsec.protonmail.ch]; NEURAL_HAM_SHORT(-0.96)[-0.965,0]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-3.76)[ip: (-9.89), ipnet: 185.70.40.0/24(-4.90), asn: 19905(-3.92), country: US(-0.06)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ASN(0.00)[asn:19905, ipnet:185.70.40.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[132.40.70.185.list.dnswl.org : 127.0.5.1]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=default]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[] 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: Wed, 03 Apr 2019 23:41:47 -0000 To get Windows to boot I think the only hacks I needed were in bhyve/mem.c = (this is not production ready!) Diff'd against 12.0-release -- /tmp//sh-np.vFXFJd 2019-04-04 00:29:32.752990000 +0100 +++ mem.c 2019-03-02 22:27:14.500906000 +0000 @@ -101,20 +101,22 @@ } static int -mmio_rb_add(struct mmio_rb_tree *rbt, struct mmio_rb_range *new) +mmio_rb_add(struct mmio_rb_tree *rbt, struct mmio_rb_range *new_element) { struct mmio_rb_range *overlap; - overlap =3D RB_INSERT(mmio_rb_tree, rbt, new); + overlap =3D RB_INSERT(mmio_rb_tree, rbt, new_element); + printf("mmio_rb_add: %lx:%lx\n", new_element->mr_base, new_element-= >mr_end); + if (overlap !=3D NULL) { -#ifdef RB_DEBUG - printf("overlap detected: new %lx:%lx, tree %lx:%lx\n", - new->mr_base, new->mr_end, +//#ifdef RB_DEBUG + printf("overlap detected: new_element %lx:%lx, tree %lx:%lx= \n", + new_element->mr_base, new_element->mr_end, overlap->mr_base, overlap->mr_end); -#endif +//#endif - return (EEXIST); +// return (EEXIST); } return (0); @@ -336,6 +338,8 @@ assert((mr->flags & MEM_F_IMMUTABLE) =3D=3D 0); RB_REMOVE(mmio_rb_tree, &mmio_rb_root, entry); + printf("unregister: %lx:%lx\n", mr->base, mr->base+mr->size= ); + /* flush Per-vCPU cache */ for (i=3D0; i < VM_MAXCPU; i++) { if (mmio_hint[i] =3D=3D entry) @@ -348,7 +352,12 @@ if (entry) free(entry); - return (err); + if (err) + fprintf( stderr, "Unregister mem errno %d for range %lx:%lx= .\n", err, + memp->base, memp->base + memp->size ); + + return 0; + //return (err); } =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Thursday, 28 March 2019 22:02, Ruslan Bukin wrote: > Hi Robert: > > On Sun, Mar 17, 2019 at 04:22:29PM +0000, Robert Crowston via freebsd-vir= tualization wrote: > > > Is it worth me continuing to hack away at these problems---of course I'= m happy to share anything I come up with---or is there an official solution= to GPU support in the pipe about to make my efforts redundant :)? > > Could you share your patch/hacks somewhere? > I would like to try it with AMD graphics card and Windows. > > Ruslan From owner-freebsd-virtualization@freebsd.org Thu Apr 4 03:26:02 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 E76AF155FADF for ; Thu, 4 Apr 2019 03:26:01 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [65.103.231.193]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC931822F0 for ; Thu, 4 Apr 2019 03:26:00 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 87B7FCC312 for ; Wed, 3 Apr 2019 21:26:37 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id r4kuo0pSpBW1 for ; Wed, 3 Apr 2019 21:26:37 -0600 (MDT) Received: from photon.int.bluestop.org (unknown [65.103.231.197]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA for ; Wed, 3 Apr 2019 21:26:37 -0600 (MDT) To: freebsd-virtualization@freebsd.org From: Rebecca Cran Subject: Bhyve with UEFI edk2-stable201903 and CSM support - debugging the crash Message-ID: <9927beac-92cd-1059-298d-b7ffd9f34a42@bluestop.org> Date: Wed, 3 Apr 2019 21:25:52 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: DC931822F0 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.95 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(-2.99)[ip: (-9.88), ipnet: 65.100.0.0/14(-4.91), asn: 209(-0.09), country: US(-0.06)]; DKIM_TRACE(0.00)[bluestop.org:+]; DMARC_POLICY_ALLOW(-0.50)[bluestop.org,quarantine]; MX_GOOD(-0.01)[mail.bluestop.org]; NEURAL_HAM_SHORT(-0.95)[-0.947,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:209, ipnet:65.100.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[] 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: Thu, 04 Apr 2019 03:26:02 -0000 I've spent some time trying to figure out where and why the UEFI 2.70 firmware is crashing when built with CSM support under Bhyve. The first thing I noticed is that the code that builds the E820 table doesn't appear to be finding the location of the EBDA at 0x40E: the first entry should be something like 0x0 to 0x4cf00, but is 0-0 instead. E820[ 0]: 0x               0 ---- 0x               0, Type = 0x1 E820[ 1]: 0x               0 ---- 0x           A0000, Type = 0x2 E820[ 2]: 0x           E0000 ---- 0x          100000, Type = 0x2 E820[ 3]: 0x          100000 ---- 0x          406000, Type = 0x1 ... As an aside, I'm working on a patch to submit upstream to fix the output so it pads with zeros instead of spaces. I've also found that as was probably pretty obvious the system is crashing when trying to call into the CSM to initialize it. It gets as far as calling AsmThunk16 (AsmThunk.nasm), but never appears to reach CsmMain in BhyveCsm16.c. I'll see if I can work on it some more to narrow down the error. Another thing: the GNUmakefile in OvmfPkg/Csm/BhyveCsm16 has "CC ?= gcc", but it appears the build system already sets CC to "cc", which uses the system's clang compiler, which can't compile the assembly code. I don't know if we might want to either hard-code CC to "gcc" for now, or have users create a 'cc' symlinks in BaseTools/Bin/FreeBSD-amd64 ? -- Rebecca Cran From owner-freebsd-virtualization@freebsd.org Thu Apr 4 06:27:08 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 8E8921564851 for ; Thu, 4 Apr 2019 06:27:08 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 70A0087F9A for ; Thu, 4 Apr 2019 06:27:07 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x346R0UT031283; Wed, 3 Apr 2019 23:27:00 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x346R09b031282; Wed, 3 Apr 2019 23:27:00 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904040627.x346R09b031282@gndrsh.dnsmgr.net> Subject: Re: Bhyve with UEFI edk2-stable201903 and CSM support - debugging the crash In-Reply-To: <9927beac-92cd-1059-298d-b7ffd9f34a42@bluestop.org> To: Rebecca Cran Date: Wed, 3 Apr 2019 23:27:00 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 70A0087F9A X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.88 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.52)[0.521,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.01)[0.006,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.43)[0.431,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.03)[ip: (0.13), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.04), country: US(-0.06)] 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: Thu, 04 Apr 2019 06:27:08 -0000 > I've spent some time trying to figure out where and why the UEFI 2.70 > firmware is crashing when built with CSM support under Bhyve. > > The first thing I noticed is that the code that builds the E820 table > doesn't appear to be finding the location of the EBDA at 0x40E: the > first entry should be something like 0x0 to 0x4cf00, but is 0-0 instead. Since your building a bios there should be a table some place in some header or c file that builds the EBDA and puts a pointer to it at 0x40E. This should be someplace in the CSM legacy support stuff since the EBSA is a legacy bios thingy. You may want to look at the prior port of UEFI/CSM and see how this was done in that code, it may be a hard coded hack. > E820[ 0]: 0x?????????????? 0 ---- 0x?????????????? 0, Type = 0x1 > E820[ 1]: 0x?????????????? 0 ---- 0x?????????? A0000, Type = 0x2 > E820[ 2]: 0x?????????? E0000 ---- 0x????????? 100000, Type = 0x2 > E820[ 3]: 0x????????? 100000 ---- 0x????????? 406000, Type = 0x1 > > ... > > > As an aside, I'm working on a patch to submit upstream to fix the output > so it pads with zeros instead of spaces. > > > I've also found that as was probably pretty obvious the system is > crashing when trying to call into the CSM to initialize it. It gets as > far as calling AsmThunk16 (AsmThunk.nasm), but never appears to reach > CsmMain in BhyveCsm16.c. I'll see if I can work on it some more to > narrow down the error. Well I would think if the legacy memory region table is bogus that would be a good start point to fix. > > Another thing: the GNUmakefile in OvmfPkg/Csm/BhyveCsm16 has "CC ?= > gcc", but it appears the build system already sets CC to "cc", which > uses the system's clang compiler, which can't compile the assembly code. > > I don't know if we might want to either hard-code CC to "gcc" for now, > or have users create a 'cc' symlinks in BaseTools/Bin/FreeBSD-amd64 ? I would firmcode it, if CC=cc then CC=gcc, this would allow a person to override CC with something else and still have all the other stuff work out, except for this specific point that does infact need gcc. > Rebecca Cran -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Thu Apr 4 07:46:04 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 D2D4B1567276 for ; Thu, 4 Apr 2019 07:46:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 664158A9FC for ; Thu, 4 Apr 2019 07:46:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1D5061567274; Thu, 4 Apr 2019 07:46:04 +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 0B40A1567273 for ; Thu, 4 Apr 2019 07:46:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99C508A9F8 for ; Thu, 4 Apr 2019 07:46:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id CC50A1AC0C for ; Thu, 4 Apr 2019 07:46:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x347k27W019180 for ; Thu, 4 Apr 2019 07:46:02 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x347k23O019179 for virtualization@FreeBSD.org; Thu, 4 Apr 2019 07:46:02 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 235856] FreeBSD freezes on AWS EC2 t3 machines Date: Thu, 04 Apr 2019 07:46:02 +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: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ale@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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-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: Thu, 04 Apr 2019 07:46:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235856 --- Comment #5 from Alex Dupre --- Created attachment 203370 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D203370&action= =3Dedit dmesg with crash on t3.xlarge I've changed the instance from a t3.large to a t3.xlarge, and this is the latest crash I got. This time it wasn't a freeze, the machine rebooted. No issues on my c5 machines in the last month. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Apr 4 16:38:26 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 704F615763F2 for ; Thu, 4 Apr 2019 16:38:26 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 A3443817CB for ; Thu, 4 Apr 2019 16:38:25 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=Message-ID:Subject:To:From:Date:In-Reply-To; bh=NSOYFWdEd5bs0tTxOaXcypbYx3HQIN2+oJYLCBfcB2c=; b=UY/eHqXCne4ZlWq3j7emUb1nfR WxeOH1twKQwRLc26KXkBy4UtdeT9HO45Uvt3cQjAcmA9lcRJ4aRbWGoWPnY707atsjfF9w5aL/nOF FcymTWXLVKdx3M9C8NoPhJoP5lydPEnXiVqsPOxKAl3AvtwaEt3anM+GmljyLxvoAdm0=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hC5Ng-0008Nr-1n for freebsd-virtualization@freebsd.org; Thu, 04 Apr 2019 23:38:24 +0700 Date: Thu, 4 Apr 2019 23:38:24 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: running FreePBX SNG7 Official Distro Message-ID: <20190404163824.GA32075@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Thu, 04 Apr 2019 16:38:26 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dear Colleagues, Has anyone tried to run FreePBX under bhyve? That's what I get trying to start the vm after a successful automatic install from the ISO image: Boot Failed. EFI DVD/CDROM Failed to set MokListRT: Invalid Parameter Failed to open \EFI\BOOT\grubx64.efi - Not Found Failed to load image \EFI\BOOT\grubx64.efi: Not Found start_image() returned Not Found Boot Failed. EFI Misc Device =2E The vm config: uefi=3D"yes" cpu=3D1 memory=3D2G network0_type=3D"virtio-net" network0_switch=3D"main" disk0_type=3D"virtio-blk" disk0_name=3D"disk0" disk0_dev=3D"zvol" graphics=3D"yes" graphics_wait=3D"no" graphics_res=3D"1280x720" graphics_port=3D"5909" graphics_listen=3D"192.168.4.1" xhci_mouse=3D"yes" uuid=3D"4c1871cb-56f1-11e9-bdbf-5404a6b49a66" network0_mac=3D"58:9c:fc:0b:85:76" --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcpjMAAAoJEA2k8lmbXsY0mjcH/jfLL8nkANecRWjonjRzrP8t DHg9z7PUxCrWCympgNFfo+VGnzA4H6W7MVMljHFOrys5B7P0ELpjCtqEY4VQc/5c ZnPhEX3q0gcTZlOtQfD8PBmO61G7HIgVhmZ7M9nDLvceHPcEGxo97nFg/2ln2VTl X8sDdXJ7cjsC+Go+CatAD2FO9SW0ulj1QJdolW7YgVRts/l7bpi3AjsqWS6gnpjY styLTr1PsU1hPscAycyI2WP26w3VPjb4R6lYpsDbaOsnZgHFAWqQ7R5uOFp44GeN Oh7LPIshDb5sRW19o+6i8w8f2RBqP7vQYAxJH8WZ6MIKkORdnt7mtTcLS9moHZw= =lPtk -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From owner-freebsd-virtualization@freebsd.org Fri Apr 5 16:12:30 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 4610B1531946 for ; Fri, 5 Apr 2019 16:12:30 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 424B668480 for ; Fri, 5 Apr 2019 16:12:28 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=XLJ9fj28bD4MnH3HThgjBMg2FNf2IBclrBFNScKvhrA=; b=pfCKR+jkM75hu6jCZTrwlDv2c/ 4gAmckWMOYrzfxBHAGwq/GGqLk+n2lmj/8V2YYLWfRU5G24908U7PbaGHtlUIiF8oCFjeKyEHpmNe 8J6H4CE6IxC2CpuL/iLjb+SWqqFouVoJw76+q1ELHF3OdNOD515/h0JfCeQBcGLwYzeA=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hCRS7-000Jtn-OP for freebsd-virtualization@freebsd.org; Fri, 05 Apr 2019 23:12:27 +0700 Date: Fri, 5 Apr 2019 23:12:27 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: running FreePBX SNG7 Official Distro Message-ID: <20190405161227.GA73383@admin.sibptus.ru> References: <20190404163824.GA32075@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: <20190404163824.GA32075@admin.sibptus.ru> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Fri, 05 Apr 2019 16:12:30 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Victor Sudakov wrote: >=20 > Has anyone tried to run FreePBX under bhyve? That's what I get trying to > start the vm after a successful automatic install from the ISO image: >=20 > Boot Failed. EFI DVD/CDROM > Failed to set MokListRT: Invalid Parameter > Failed to open \EFI\BOOT\grubx64.efi - Not Found > Failed to load image \EFI\BOOT\grubx64.efi: Not Found > start_image() returned Not Found > Boot Failed. EFI Misc Device Below are the partitions the automatic installer has created (looking at them from another vm): root@mfsbsd:~ # gpart show vtbd1 =3D> 34 41942973 vtbd1 GPT (20G) 34 2014 - free - (1.0M) 2048 186368 1 efi (91M) 188416 4096000 2 ms-basic-data (2.0G) 4284416 37654528 3 linux-lvm (18G) 41938944 4063 - free - (2.0M) If I "mount_msdosfs /dev/vtbd1p1 /mnt/" I see that grubx64.efi is not where bhyve expects to find it: root@mfsbsd:~ # find /mnt/ -name grubx64.efi /mnt/EFI/centos/grubx64.efi Who is to blame, bhyve or FreePBX's installer? How can I tell bhyve's UEFI loader to look for grubx64.efi in a different place? Or look for a different loader? Who says that the image to load should be "\EFI\BOOT\grubx64.efi" and not "\EFI\BOOT\BOOTX64.EFI" for example? --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --0F1p//8PRICkK4MW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcp35rAAoJEA2k8lmbXsY0+UgIAIOfflioWoZ+kGVIk36jWWyJ KztbLycZSUtgZmqW8oDW+Ucdcbs05w1nAkMaog+JXw+LI0RSNUzAvdn/NNsOdkVC 6kzgswk75NW7ruXfonN1OA1xMV3r8oE+i9xSy5l0TLeZJro4WOZA6pV6DZoceZIx 3L3qaWqEru0kMabi3nc9y2dI0LoggQam15qFvfIZIVFwhESihHN4MKC/RsYLagda R4Xj3wLRGtyhl5HRl9XnLKzaqmxSkgV+qy5jy2fPJy3A6+PpAadtjC53jN6TdWjR Hqk7Tl7lbre8s7CVKRhYJSRF0E0yqoBn2tPOqNA5Q1bIWb41F3eNdeg6RAOns90= =A/qr -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- From owner-freebsd-virtualization@freebsd.org Fri Apr 5 18:40:52 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 243D71556902 for ; Fri, 5 Apr 2019 18:40:52 +0000 (UTC) (envelope-from ctuffli@gmail.com) Received: from mail-ot1-f66.google.com (mail-ot1-f66.google.com [209.85.210.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 368BF6EA8A for ; Fri, 5 Apr 2019 18:40:51 +0000 (UTC) (envelope-from ctuffli@gmail.com) Received: by mail-ot1-f66.google.com with SMTP id o74so6543575ota.3 for ; Fri, 05 Apr 2019 11:40:51 -0700 (PDT) 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=TTShiwIio7BCWyPFTVGgh2kvzySL5QZpS7U+ef1wam8=; b=INCvcsOcaj7OpQQCc1/mKjph+3RiEa+k3UvZJo5G/w/U9Uf34RpWKZKGD6txMhDhYm oExk181AcFMa7FeckA4Jiu6kRe+lVr+QsSKHQXqdHefBQ7MDCu9U+MeyNi3F8JX1mNIL 85UC3aLedsTsfsvDQVkWOGtVqBhECXrI0ZUL5HPrBaN0oOTrKL+rzOQ5mmDKt2n41JNn ZusgOmqfU4OvTupbXDoacS2y72KmRq/hnyfzdQCf4GYWomjx9YA36C41JoG0h9xh2JkF vZkkld7uwQlHZ7p7I7hJ/aWcspyyju3x2mg3LGPrASzcqoRk7KPVM/9T61wBtrnL1+Yl Cubw== X-Gm-Message-State: APjAAAU3f4zaz5+QhC8B8D0HorP+ytfiW/tneWfyEG+VqJjVMI3EM/lc dPBTcuumutelPfFY6mvGTWwRh26Z X-Google-Smtp-Source: APXvYqw/r9WIQQ+9vCleQJEdqf/mtOzhVM3QSw6GLxCqQtif31MZhPqP9F9/hxLXTbGQxM7hYEM2Iw== X-Received: by 2002:a9d:57c4:: with SMTP id q4mr9248907oti.151.1554487841695; Fri, 05 Apr 2019 11:10:41 -0700 (PDT) Received: from mail-oi1-f177.google.com (mail-oi1-f177.google.com. [209.85.167.177]) by smtp.gmail.com with ESMTPSA id r190sm8980243oie.43.2019.04.05.11.10.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Apr 2019 11:10:41 -0700 (PDT) Received: by mail-oi1-f177.google.com with SMTP id l203so5623434oia.3 for ; Fri, 05 Apr 2019 11:10:41 -0700 (PDT) X-Received: by 2002:aca:407:: with SMTP id 7mr7752502oie.90.1554487841200; Fri, 05 Apr 2019 11:10:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Chuck Tuffli Date: Fri, 5 Apr 2019 11:10:30 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: emulated PCI device BAR size To: Jason Tubnor Cc: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 368BF6EA8A X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of ctuffli@gmail.com designates 209.85.210.66 as permitted sender) smtp.mailfrom=ctuffli@gmail.com X-Spamd-Result: default: False [-4.17 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; RWL_MAILSPIKE_GOOD(0.00)[66.210.85.209.rep.mailspike.net : 127.0.0.18]; RCVD_COUNT_THREE(0.00)[4]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.94)[-0.938,0]; FORGED_SENDER(0.30)[chuck@freebsd.org,ctuffli@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[chuck@freebsd.org,ctuffli@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; IP_SCORE(-1.22)[ipnet: 209.85.128.0/17(-3.87), asn: 15169(-2.17), country: US(-0.06)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[66.210.85.209.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[] 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: Fri, 05 Apr 2019 18:40:52 -0000 On Sat, Mar 23, 2019 at 6:44 PM Jason Tubnor wrote: > > > > On Sun., 24 Mar. 2019, 6:35 am Chuck Tuffli, wrote: >> >> On Mon, Mar 18, 2019 at 10:15 AM Chuck Tuffli wrote: >> >> > >> > So my question is how to best fix this. The easiest would be to add a >> > check to the BAR size calculation in pci_nvme.c along the lines of: >> > #define NVME_MMIO_SPACE_MIN (1 << 14) >> > ... >> > pci_membar_sz = MAX( , >> > NVME_MMIO_SPACE_MIN); >> >> I went down this route and have a patch up for review >> (https://reviews.freebsd.org/D19676) if anyone is interested. >> >> --chuck > > > I've built and installed this patch on FreeBSD 12.0-STABLE-amd64-20190314-r345117. Testing occurred against Windows 10 Pro guest with a presented NVMe bhyve device and all IO transactions worked without issue. > > Can this be committed to head and MFD to 12-STABLE. Thanks! Committed with r345956. MFC in 2 weeks if nothing pops up. Thanks again for all your testing! --chuck https://svnweb.freebsd.org/changeset/base/345956 From owner-freebsd-virtualization@freebsd.org Fri Apr 5 19:20:23 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 E5DF01558A71 for ; Fri, 5 Apr 2019 19:20:22 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 52B5A6FF0F for ; Fri, 5 Apr 2019 19:20:21 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x35JKKMY040720; Fri, 5 Apr 2019 12:20:20 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x35JKKGL040719; Fri, 5 Apr 2019 12:20:20 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904051920.x35JKKGL040719@gndrsh.dnsmgr.net> Subject: Re: running FreePBX SNG7 Official Distro In-Reply-To: <20190405161227.GA73383@admin.sibptus.ru> To: Victor Sudakov Date: Fri, 5 Apr 2019 12:20:20 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 52B5A6FF0F 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.980,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] 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: Fri, 05 Apr 2019 19:20:23 -0000 -- Start of PGP signed section. > Victor Sudakov wrote: > > > > Has anyone tried to run FreePBX under bhyve? That's what I get trying to > > start the vm after a successful automatic install from the ISO image: > > > > Boot Failed. EFI DVD/CDROM > > Failed to set MokListRT: Invalid Parameter > > Failed to open \EFI\BOOT\grubx64.efi - Not Found > > Failed to load image \EFI\BOOT\grubx64.efi: Not Found > > start_image() returned Not Found > > Boot Failed. EFI Misc Device > > Below are the partitions the automatic installer has created (looking at > them from another vm): > > root@mfsbsd:~ # gpart show vtbd1 > => 34 41942973 vtbd1 GPT (20G) > 34 2014 - free - (1.0M) > 2048 186368 1 efi (91M) > 188416 4096000 2 ms-basic-data (2.0G) > 4284416 37654528 3 linux-lvm (18G) > 41938944 4063 - free - (2.0M) > > If I "mount_msdosfs /dev/vtbd1p1 /mnt/" I see that grubx64.efi is not > where bhyve expects to find it: > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi > /mnt/EFI/centos/grubx64.efi > > Who is to blame, bhyve or FreePBX's installer? > > How can I tell bhyve's UEFI loader to look for grubx64.efi in a > different place? Or look for a different loader? > > Who says that the image to load should be "\EFI\BOOT\grubx64.efi" and > not "\EFI\BOOT\BOOTX64.EFI" for example? I can not quickly answer that, but lets try the short quick fix and simply copy this file to the right place and see if that gets you up and running. That would also tell us that we have what is actually a common efi system failure problem in that stuff looks in the wrong place. I have read many an install instruction that just says copy this file to these too places as some bioses look for it in one place and others look for it someplace else. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Fri Apr 5 19:23:38 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 B3D9A1558F29 for ; Fri, 5 Apr 2019 19:23:38 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 C67CC70424; Fri, 5 Apr 2019 19:23:37 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x35JNZFg040752; Fri, 5 Apr 2019 12:23:35 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x35JNZbU040751; Fri, 5 Apr 2019 12:23:35 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904051923.x35JNZbU040751@gndrsh.dnsmgr.net> Subject: Re: emulated PCI device BAR size In-Reply-To: To: Chuck Tuffli Date: Fri, 5 Apr 2019 12:23:35 -0700 (PDT) CC: Jason Tubnor , "freebsd-virtualization@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: C67CC70424 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.95 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.03)[ip: (0.13), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.04), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.57)[0.574,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.17)[0.170,0]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; NEURAL_SPAM_LONG(0.29)[0.288,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[] 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: Fri, 05 Apr 2019 19:23:38 -0000 > On Sat, Mar 23, 2019 at 6:44 PM Jason Tubnor wrote: > > > > > > > > On Sun., 24 Mar. 2019, 6:35 am Chuck Tuffli, wrote: > >> > >> On Mon, Mar 18, 2019 at 10:15 AM Chuck Tuffli wrote: > >> > >> > > >> > So my question is how to best fix this. The easiest would be to add a > >> > check to the BAR size calculation in pci_nvme.c along the lines of: > >> > #define NVME_MMIO_SPACE_MIN (1 << 14) > >> > ... > >> > pci_membar_sz = MAX( , > >> > NVME_MMIO_SPACE_MIN); > >> > >> I went down this route and have a patch up for review > >> (https://reviews.freebsd.org/D19676) if anyone is interested. > >> > >> --chuck > > > > > > I've built and installed this patch on FreeBSD 12.0-STABLE-amd64-20190314-r345117. Testing occurred against Windows 10 Pro guest with a presented NVMe bhyve device and all IO transactions worked without issue. > > > > Can this be committed to head and MFD to 12-STABLE. Thanks! > > Committed with r345956. MFC in 2 weeks if nothing pops up. Thanks > again for all your testing! A small prod Chuck you should of mentioned Jason in the commit message for his testing work. I know it is easy to forget this, but it is the right thing to do. Jason, I'll thank you here, in a more personal maner, for working with Chuck on getting this fixed. Thanks, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Sat Apr 6 04:34:27 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 E0D57156BD4B for ; Sat, 6 Apr 2019 04:34:26 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 0DF058D3F7 for ; Sat, 6 Apr 2019 04:34:25 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=1BK4A59RaQF+sBeyuaWU7JGn1nyOijGZb3xKqISwqtQ=; b=Ix3U/r1wNyVpGDnq090YBTKFjs q+LdL82o1l9gd2Fo2V9WeoaZSzWu2eJqf9KVgrZdpkvFaR6SmgpHbAottnJdoqN8qBBmdQbY00sAV XPERoYfG1IXp3YmPjubehEL3x1DfqZ+u6SUvcJDFUC26hKb4uX9ZYpCnFFR5llDlyn14=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hCd28-000Fwc-KC for freebsd-virtualization@freebsd.org; Sat, 06 Apr 2019 11:34:24 +0700 Date: Sat, 6 Apr 2019 11:34:24 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: running FreePBX SNG7 Official Distro Message-ID: <20190406043424.GA59075@admin.sibptus.ru> References: <20190405161227.GA73383@admin.sibptus.ru> <201904051920.x35JKKGL040719@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <201904051920.x35JKKGL040719@gndrsh.dnsmgr.net> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Sat, 06 Apr 2019 04:34:27 -0000 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Rodney W. Grimes wrote: [dd] > >=20 > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi > > /mnt/EFI/centos/grubx64.efi > >=20 > > Who is to blame, bhyve or FreePBX's installer? > >=20 > > How can I tell bhyve's UEFI loader to look for grubx64.efi in a > > different place? Or look for a different loader? > >=20 > > Who says that the image to load should be "\EFI\BOOT\grubx64.efi" and > > not "\EFI\BOOT\BOOTX64.EFI" for example? >=20 > I can not quickly answer that, but lets try the short quick fix > and simply copy this file to the right place and see if that > gets you up and running.=20 Yes, copying grubx64.efi to "\EFI\BOOT\" does get the guest up and running (I used mfsbsd from a different VM to manipulate the EFI partition). Moreover, I waited (for a long time!) for the EFI interactive shell prompt and with a few commands: Shell> fs0 FS0:\> cd \EFI\centos FS0:\EFI\centos\> grubx64.efi =20 I also managed to boot the guest OS all right. But naturally, the latter fix worked till next reboot only, I don't know how to save the new EFI setup in the guest's configuration. The hardware UFI BIOSes I've seen so far (not many, I must admit) permitted me to save which efi binary I would prefer to boot next time. > That would also tell us that we have > what is actually a common efi system failure problem in that > stuff looks in the wrong place. It seems so. > I have read many an install > instruction that just says copy this file to these too places > as some bioses look for it in one place and others look for it > someplace else. I would very much appreciate a link to some such instruction about uefi-edk2-bhyve: namely how and where it looks for what on boot, and if I can create a menu for example, or change its startup procedure. I can guess that it looks for a FAT16 partition in the GPT with the type "efi" but the rest is a mystery for me. Why is it trying to find "grubx64.efi" and not the default "boot64.efi" (which is present), for example? --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcqCxQAAoJEA2k8lmbXsY0X9wIAIURyqCsKD03TytqspB8XQBs vdB86y4SEzndbRcFctYMp0dadZiouvJnaCM4uIwVrZ1A/IIc3wVuNVQp2YixDU2D h81AEBOh5DaiREsmkHhM3EMENPCvKNq7/d6EscktiwZydjUtzJEumkoKzq92NMBE JMrblazvmJB/g+7hUpQ6Z3XfGMNqNQy35z4i3DKJy0nz5Jq9u5DndNjwOUTNhyXu 3WDy+OwU9+6JAPmb0eQiQitKkbQmOYX3v2hsGnJs2X63A+aqJHTrcbj4Ts7EuHsR VEVAfBvZKOsQJxyxGt0kZKU7mrCGNuMHzW0TELivXIffJvFRv/PJGKYLJPAfiuc= =z84A -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- From owner-freebsd-virtualization@freebsd.org Sat Apr 6 08:05:24 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 A2C961579839 for ; Sat, 6 Apr 2019 08:05:24 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 1307B6DE3F for ; Sat, 6 Apr 2019 08:05:23 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3685JZe043782; Sat, 6 Apr 2019 01:05:19 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3685J6G043781; Sat, 6 Apr 2019 01:05:19 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904060805.x3685J6G043781@gndrsh.dnsmgr.net> Subject: Re: running FreePBX SNG7 Official Distro In-Reply-To: <20190406043424.GA59075@admin.sibptus.ru> To: Victor Sudakov Date: Sat, 6 Apr 2019 01:05:19 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 1307B6DE3F 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_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.981,0] 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: Sat, 06 Apr 2019 08:05:25 -0000 -- Start of PGP signed section. > Rodney W. Grimes wrote: > > [dd] > > > > > > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi > > > /mnt/EFI/centos/grubx64.efi > > > > > > Who is to blame, bhyve or FreePBX's installer? > > > > > > How can I tell bhyve's UEFI loader to look for grubx64.efi in a > > > different place? Or look for a different loader? > > > > > > Who says that the image to load should be "\EFI\BOOT\grubx64.efi" and > > > not "\EFI\BOOT\BOOTX64.EFI" for example? > > > > I can not quickly answer that, but lets try the short quick fix > > and simply copy this file to the right place and see if that > > gets you up and running. > > Yes, copying grubx64.efi to "\EFI\BOOT\" does get the guest up and > running (I used mfsbsd from a different VM to manipulate the EFI > partition). You can usually use the host by doing mdconfig -f gpart show md0 # Assuming mdconfig was unit 0 mount -t msdosfs /dev/md0p /mnt #The n comes from gpart, you want the efi partition Now you can manipulate /mnt/ all you want umount /mnt mdconfig -d -u 0 # Assuming mdconfig was unit 0 > Moreover, I waited (for a long time!) for the EFI interactive shell > prompt and with a few commands: Yes, the timeout is very long, and I do not know that we document anyplace that if you wait long enough at a failed boot you do get a EFI shell prompt eventually. > > Shell> fs0 > FS0:\> cd \EFI\centos > FS0:\EFI\centos\> grubx64.efi > > I also managed to boot the guest OS all right. > > But naturally, the latter fix worked till next reboot only, I don't know > how to save the new EFI setup in the guest's configuration. My recommedation at this time would be to simply copy grubx64.efi to the right place and leave it there so that it just boots without any other change. > > The hardware UFI BIOSes I've seen so far (not many, I must admit) > permitted me to save which efi binary I would prefer to boot next time. That is done with an efivar, as it stands right now bhyve efi has no persistant variable storage, a feature that needs to be implemented. > > That would also tell us that we have > > what is actually a common efi system failure problem in that > > stuff looks in the wrong place. > > It seems so. > > > I have read many an install > > instruction that just says copy this file to these too places > > as some bioses look for it in one place and others look for it > > someplace else. > > I would very much appreciate a link to some such instruction about > uefi-edk2-bhyve: namely how and where it looks for what on boot, and if I > can create a menu for example, or change its startup procedure. I do not know where that information is, others may be able to fill in more details. > I can guess that it looks for a FAT16 partition in the GPT with the type > "efi" but the rest is a mystery for me. Why is it trying to find > "grubx64.efi" and not the default "boot64.efi" (which is present), for > example? I suspect that what ever guest you installed installed something else someplace, either within the eft partition, or possibly in the MBR? -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Sat Apr 6 08:55:01 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 2DBA5157B177 for ; Sat, 6 Apr 2019 08:55:01 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 611F37030E for ; Sat, 6 Apr 2019 08:55:00 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=XWBqwSffoL9h4jvqw4G78swJGyuejMh5lsR+JqXDL0U=; b=o+7Oq2lpFfwVbnd37K3ZJi5fYC OUZhLYIB4u2est93rg72oiI8JePn2Co1MYXBBQJC0TC/k2CSbLnMeS+lHIg9Hhp3YEtvjssuaD3Xf QHCkhRcG1sb05okjd7gHJgD7tSnrWAQQejyuTPj0h52sKukUlvT6kYJ9FRjldJdIaAp4=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hCh6I-000NjL-U5 for freebsd-virtualization@freebsd.org; Sat, 06 Apr 2019 15:54:58 +0700 Date: Sat, 6 Apr 2019 15:54:58 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: running FreePBX SNG7 Official Distro Message-ID: <20190406085458.GA89832@admin.sibptus.ru> References: <20190406043424.GA59075@admin.sibptus.ru> <201904060805.x3685J6G043781@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <201904060805.x3685J6G043781@gndrsh.dnsmgr.net> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Sat, 06 Apr 2019 08:55:01 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Rodney W. Grimes wrote: > >=20 > > [dd] > >=20 > > > >=20 > > > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi > > > > /mnt/EFI/centos/grubx64.efi > > > >=20 > > > > Who is to blame, bhyve or FreePBX's installer? > > > >=20 > > > > How can I tell bhyve's UEFI loader to look for grubx64.efi in a > > > > different place? Or look for a different loader? > > > >=20 > > > > Who says that the image to load should be "\EFI\BOOT\grubx64.efi" a= nd > > > > not "\EFI\BOOT\BOOTX64.EFI" for example? > > >=20 > > > I can not quickly answer that, but lets try the short quick fix > > > and simply copy this file to the right place and see if that > > > gets you up and running.=20 > >=20 > > Yes, copying grubx64.efi to "\EFI\BOOT\" does get the guest up and > > running (I used mfsbsd from a different VM to manipulate the EFI > > partition). >=20 > You can usually use the host by doing mdconfig -f Unfortunately mdconfig does not work with zvols: root@vas:~ # mdconfig -a -f /dev/zvol/d02/vm/freepbx/disk0=20 mdconfig: /dev/zvol/d02/vm/freepbx/disk0 is not a regular file > > Moreover, I waited (for a long time!) for the EFI interactive shell > > prompt and with a few commands: >=20 > Yes, the timeout is very long, and I do not know that we > document anyplace that if you wait long enough at a failed > boot you do get a EFI shell prompt eventually. Can I press some key to escape to the EFI shell? > > Shell> fs0 > > FS0:\> cd \EFI\centos > > FS0:\EFI\centos\> grubx64.efi =20 > >=20 > > I also managed to boot the guest OS all right. > >=20 > > But naturally, the latter fix worked till next reboot only, I don't know > > how to save the new EFI setup in the guest's configuration. >=20 > My recommedation at this time would be to simply copy grubx64.efi > to the right place and leave it there so that it just boots without > any other change. That's what I have done for now. > >=20 > > The hardware UFI BIOSes I've seen so far (not many, I must admit) > > permitted me to save which efi binary I would prefer to boot next time. >=20 > That is done with an efivar, as it stands right now bhyve efi has > no persistant variable storage, a feature that needs to be implemented. I see. [dd] >=20 > > I can guess that it looks for a FAT16 partition in the GPT with the type > > "efi" but the rest is a mystery for me. Why is it trying to find > > "grubx64.efi" and not the default "boot64.efi" (which is present), for > > example? >=20 > I suspect that what ever guest you installed installed something > else someplace, either within the eft partition, or possibly in > the MBR? Do you mean to say, the guest installing something else someplace can influence the boot sequence of bhyve efi? --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcqGliAAoJEA2k8lmbXsY0MbMIAINlLEzRMZZ+0gK1E1xAX4BL KHWOMpXkqjEBMwpcehkR3NvB/wUos3v4eq/Zxo9x73fJ7i7qGCVQgHBYJtXH0gZ7 82B64pNL+JUbo2YSrT2BgzsVlRZF9/BPjFlpCwItDqZ3WNgCIiLS9SpK1O7ClVXH Jm4sbwm+7Pkfc6/UCYFYhnoNIwuEWlF7vR3nlmJsXIVGJZl5I/9lBI3xUPVYB0zN sjhz8HMe4sOR9dpOajb4tpx7xTVj/IP8KMJl7Q9HMAj+COr03c6F7Cwlr4w4gqm5 uAL3QdRY1vdIbhY/zeU6uO5uv+NMHCy+ZbWA/mYPuYoJhz592dfZNywv8PJ+7xE= =st07 -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1-- From owner-freebsd-virtualization@freebsd.org Sat Apr 6 10:02:14 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 C1A5915313D3 for ; Sat, 6 Apr 2019 10:02:14 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 207EE7253F for ; Sat, 6 Apr 2019 10:02:13 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x36A2BHK044705; Sat, 6 Apr 2019 03:02:11 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x36A2BZE044704; Sat, 6 Apr 2019 03:02:11 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904061002.x36A2BZE044704@gndrsh.dnsmgr.net> Subject: Re: running FreePBX SNG7 Official Distro In-Reply-To: <20190406085458.GA89832@admin.sibptus.ru> To: Victor Sudakov Date: Sat, 6 Apr 2019 03:02:11 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 207EE7253F X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.989,0] 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: Sat, 06 Apr 2019 10:02:15 -0000 > Rodney W. Grimes wrote: > > > > > > [dd] > > > > > > > > > > > > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi > > > > > /mnt/EFI/centos/grubx64.efi > > > > > > > > > > Who is to blame, bhyve or FreePBX's installer? > > > > > > > > > > How can I tell bhyve's UEFI loader to look for grubx64.efi in a > > > > > different place? Or look for a different loader? > > > > > > > > > > Who says that the image to load should be "\EFI\BOOT\grubx64.efi" and > > > > > not "\EFI\BOOT\BOOTX64.EFI" for example? > > > > > > > > I can not quickly answer that, but lets try the short quick fix > > > > and simply copy this file to the right place and see if that > > > > gets you up and running. > > > > > > Yes, copying grubx64.efi to "\EFI\BOOT\" does get the guest up and > > > running (I used mfsbsd from a different VM to manipulate the EFI > > > partition). > > > > You can usually use the host by doing mdconfig -f > > Unfortunately mdconfig does not work with zvols: > > root@vas:~ # mdconfig -a -f /dev/zvol/d02/vm/freepbx/disk0 > mdconfig: /dev/zvol/d02/vm/freepbx/disk0 is not a regular file If its a zvol cant you just do gpart show /dev/zvol/d02/vm/freepbx/disk0 and mount -t msdosfs /dev/zvol/d02/vm/freepbx/disk0p2 > > > > Moreover, I waited (for a long time!) for the EFI interactive shell > > > prompt and with a few commands: > > > > Yes, the timeout is very long, and I do not know that we > > document anyplace that if you wait long enough at a failed > > boot you do get a EFI shell prompt eventually. > > Can I press some key to escape to the EFI shell? Not that I am aware of. > > > Shell> fs0 > > > FS0:\> cd \EFI\centos > > > FS0:\EFI\centos\> grubx64.efi > > > > > > I also managed to boot the guest OS all right. > > > > > > But naturally, the latter fix worked till next reboot only, I don't know > > > how to save the new EFI setup in the guest's configuration. > > > > My recommedation at this time would be to simply copy grubx64.efi > > to the right place and leave it there so that it just boots without > > any other change. > > That's what I have done for now. > > > > > > > The hardware UFI BIOSes I've seen so far (not many, I must admit) > > > permitted me to save which efi binary I would prefer to boot next time. > > > > That is done with an efivar, as it stands right now bhyve efi has > > no persistant variable storage, a feature that needs to be implemented. > > I see. > > [dd] > > > > > > I can guess that it looks for a FAT16 partition in the GPT with the type > > > "efi" but the rest is a mystery for me. Why is it trying to find > > > "grubx64.efi" and not the default "boot64.efi" (which is present), for > > > example? > > > > I suspect that what ever guest you installed installed something > > else someplace, either within the eft partition, or possibly in > > the MBR? > > Do you mean to say, the guest installing something else someplace can > influence the boot sequence of bhyve efi? The guest created all of the bits on that zvol, it can influence many things. There is probably a tiny initial stub that efi loads that has this bath to grubx64.efi codded in it and that is what is causing this issue. -- Rod Grimes rgrimes@freebsd.org