With i3.large machine in AWS EC2, there's 1 x 475 NVMe SSD. ----------------------------------------------------------------------- The normal layout on our copr builder i3.large machines (Fedora 35) is: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS xvda 202:0 0 6G 0 disk ├─xvda1 202:1 0 1M 0 part ├─xvda2 202:2 0 500M 0 part /boot ├─xvda3 202:3 0 100M 0 part /boot/efi ├─xvda4 202:4 0 4M 0 part └─xvda5 202:5 0 5.4G 0 part /home / nvme0n1 259:0 0 442.4G 0 disk ├─nvme0n1p1 259:1 0 16G 0 part /var/lib/copr-rpmbuild └─nvme0n1p2 259:2 0 426.4G 0 part [SWAP] ----------------------------------- After upgrade to F37, there's just: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS xvda 202:0 0 6G 0 disk ├─xvda1 202:1 0 1M 0 part ├─xvda2 202:2 0 500M 0 part /boot ├─xvda3 202:3 0 100M 0 part /boot/efi ├─xvda4 202:4 0 4M 0 part └─xvda5 202:5 0 5.4G 0 part /home / But this is reproducible even with a freshly started Fedora 37 machine, just go to https://alt.fedoraproject.org/en/cloud/ , start a i3.large machine from Fedora 37 x86_64 Cloud Base AMIs - and the nvme machine is not visible. ----------------- Nvme list output: [root@aws-x86-64-spot-prod-02737160-20221118-150640 ~]# nvme list -v Subsystem Subsystem-NQN Controllers ---------------- ------------------------------------------------------------------------------------------------ ---------------- nvme-subsys0 nqn.2014.08.org.nvmexpress:1d0f0000AWS1044FA12A37704484Amazon EC2 NVMe Instance Storage nvme0 Device SN MN FR TxPort Address Subsystem Namespaces -------- -------------------- ---------------------------------------- -------- ------ -------------- ------------ ---------------- nvme0 AWS1044FA12A37704484 Amazon EC2 NVMe Instance Storage 0 pcie 0000:00:1e.0 nvme-subsys0 Device Generic NSID Usage Format Controllers ------------ ------------ -------- -------------------------- ---------------- ---------------- Tested kernels, the same behavior with all of them: kernel-core-6.0.7-300.fc37.x86_64 kernel-core-6.0.8-300.fc37.x86_64 kernel-core-6.0.9-300.fc37.x86_64 (updates-testing) How reproducible: 100%
I just tested F37 Cloud with i4i.large, and nvme controller works fine there.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.