Closed chaudron closed 4 years ago
This sounds a lot like an issue I had with more recent Gentoo boxes. In my case, it ended up being a missing module to support SCSI.
Could you open your VM configuration through something like virt-manager
and try different bus types (i.e. SATA, maybe even VirtIO)?
Interesting! changing it to SATA completed the boot process.
This seems to be an issue on multiple boxes.
I've been building all the boxes that are using a SCSI/libvirt combo over the last 24 hours, I'll go through them and figure out which of those have boot issues (and fix them if possible). I assume the most common cause is that the specific SCSI driver is located as a module on the disk, which obviously can't be loaded afterwards.
EDIT: Why this suddenly broke now I have no idea.
I opened #125 to track this accross multiple boxes.
We'll use the more generic issue in #125 to fix this...
I tried to install a simple fedora31 box on a fedora 31 machine and it's failing (even tried a brand new install). It seems to work fine on RHEL8 which is the only alternative I had available (or on OSX with the virtual box provider).
Version information:
Replication step, install latest fedora 31 with updates:
It's waiting for the IP forever, on the console for the VM I can see it's waiting for start job to complete (see attachment).