User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Firefox/91.0
Build Identifier: 

I have Tumbleweed installed on an external 250G drive.  Tumbleweed 64-bit is
working fine, and uses an encrypted LVM.  Tumbleweed 32-bit is giving problems.
 It's root file system is unencrypted, but it uses "/home" and swap from the
same encrypted LVM.

Everything worked pretty well up through kernel 5.15.x.  But I have been having
problems with 5.16 and 5.17 kernels.  It is possible that this is actually a
dracut issue (missing module).

Background: I mostly use this with a KVM virtual machine (i.e. using
"libvirt").  I normally start the VM, then click ESC to get a boot menu.  I
then plug in the USB external drive, and restart the machine (often with
sending it CTRL-ALT-DEL).  I again use the ESC key to get a boot menu and
select the entry for the USB device.

The kernel is loaded, and there is a message recognizing the USB drive.  But
often it stops there with no further progress.  If I wait long enough (several
minutes) I see dracut timeout messages.  It looks as if the system is unable to
access what is on that drive.

Sometimes it boots normally.  In that case, may 1-2 seconds after I see that
initial screen, I am prompted for the LUKS password.  But when it does not boot
normally, I am never prompted for that LUKS password.

I have attempted to setup up a similarly configured system in a separate VM,
without using that external drive.  And that works just fine.  It seems that
the problem is related to the USB external drive, with the USB being redirected
from the KVM host machine to the VM.  The KVM host is running Leap 15.4.

If I instead try booting this on my laptop, so that the external drive is
connected to a real machine rather than a VM, then everything seems to work
normally.

I never have problems with 64-bit Tumbleweed, on the same external drive.  It
is only with 32-bit Tumbleweed that I have problems.

If I first boot into 32-bit Tumbleweed, and then reboot to 32-bit Tumbleweed
(without shutting down the machine), then that usually works.  But if my first
boot is to 32-bit Tumbleweed, that usually fails.

Reproducible: Sometimes