From nobody Tue Feb 13 17:05:12 2024 X-Original-To: freebsd-virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TZ74L13KDz59Gqt for ; Tue, 13 Feb 2024 17:05:22 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from mx2.shrew.net (mx2.shrew.net [204.27.62.58]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4TZ74K2mQpz4tcJ for ; Tue, 13 Feb 2024 17:05:21 +0000 (UTC) (envelope-from mgrooms@shrew.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=shrew.net header.s=default header.b=ErpAX3fu; dmarc=none; spf=pass (mx1.freebsd.org: domain of mgrooms@shrew.net designates 204.27.62.58 as permitted sender) smtp.mailfrom=mgrooms@shrew.net Received: from mail.shrew.net (mail1.shrew.prv [10.26.2.18]) by mx2.shrew.net (8.17.1/8.17.1) with ESMTP id 41DH5DSD097086; Tue, 13 Feb 2024 11:05:13 -0600 (CST) (envelope-from mgrooms@shrew.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shrew.net; s=default; t=1707843913; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4k7tMTDsHWyeZFYvyA5HAx5GT3J6K5juDfnZttX9bBs=; b=ErpAX3fuGTXJwCnUsj6tzj8U/bQZ+LwAb04uNK9jnjv0fhksT/sOsvjhOFZ8FUvqaPyWO+ qjgsATVrUwDZqbauI37QYsgyP7r+GRSLmRgJ6DuNhDxJPBYZLfomJs9dzaEO5kVyfWhyuj 8HDL+Ydp5T4ZxO12Z/wsisXel1HOpjb7V6UzTeMyqyX7z0/7qMdx6ghLc3Yb0rO1yVE0T2 8u5q7gAaNHbr+fPcaVCDPEtGDBhY1ASbGfA/4puePqzMVBeBexoY+zvyQr3UIMXn8YPIfv ZSLcnKtb5Pwm8G83+uzcw2V7Q2hbXFylLH2ww3fUMyTJlTARQkomi/V4w0ruZg== Received: from [10.22.200.32] (unknown [136.62.156.42]) by mail.shrew.net (Postfix) with ESMTPSA id 7641F3B578; Tue, 13 Feb 2024 11:05:13 -0600 (CST) Message-ID: <0e7fb763-43e1-4b79-8e1e-ee97e664ac29@shrew.net> Date: Tue, 13 Feb 2024 11:05:12 -0600 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: 14R bhyve RHEL9+NVME Content-Language: en-US To: Jason Tubnor , FreeBSD virtualization References: <678ac1d2-d00c-450e-bc2e-f9d979d19340@shrew.net> <20240212012559.Horde.aH5FMCkNv4j7GfULz1fq5rn@drive.tubnor.net> From: Matthew Grooms In-Reply-To: <20240212012559.Horde.aH5FMCkNv4j7GfULz1fq5rn@drive.tubnor.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.48 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; R_DKIM_ALLOW(-0.20)[shrew.net:s=default]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; DMARC_NA(0.00)[shrew.net]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:19969, ipnet:204.27.56.0/21, country:US]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; DKIM_TRACE(0.00)[shrew.net:+] X-Rspamd-Queue-Id: 4TZ74K2mQpz4tcJ On 2/11/24 19:25, Jason Tubnor wrote: > Hi Matthew, > > There is some underlying bug post 9.1 when it comes to Anaconda and the presented NVMe storage. I can't reproduce it with newer version of Anaconda that is present in Fedora. > > Uplifting in place from 9.1 to 9.3, there are no issues once the operating system is up and running, so it isn't a RHEL thing, just the installer. > > Cheers, > > Jason. > > "Matthew Grooms" mgrooms@shrew.net – 12 February 2024 11:32 AM >> Hey All, >> >> Has anyone had experience installing either Rocky or Alma Linux 9.3 >> using virtual NVME disks on a FreeBSD 14R host? I have no problem using >> VirtIO block devices or if I downgrade to an 8.9 variant. However, using >> NVME with a 9.3 variant will cause the installer to consistently fail on >> my system. I'm not sure how to gather more data at this point as the >> installer displays a wall of text that I'm not sure how to extract. I've >> already burned a few hours on this so I thought I'd reach out to the >> list to see if anyone else has already dug into this. If not, I'll see >> what I can do to gather more info. For reference, here are the ISOs I've >> tried installing from so far ... >> >> AlmaLinux-8.9-x86_64-boot.iso >> AlmaLinux-9.3-x86_64-boot.iso >> Rocky-9.3-x86_64-minimal.iso >> >> Thanks, >> >> -Matthew Thanks for the info. I was able to install with 9.1 and upgrade to 9.3 without an issue. -Matthew