Back in May/2023 I lost all VMs except dom0. So I pulled an old SSD with win10 in and used my PC while qubes OS SSD sat in the package. Back in May/2023 I was able to boot into dom0 and run some qubes commands to list VMs etc.
Over these month I didnot do any bios updates.
Now I am trying to repain the VMs from Qubes SSD. I put SSD back into same PC and it is not booting. It is going to a boot loop.
Error I am seeing(two types of error depending on the item I pick in boot menu)
If command contain multiboot I am getting no multiboot header found
If command contain multiboot2 PC gives a blank screen and reboots after printing Loading initial ramdisk ...
Xen version 4.1.4.3
Linux kernal version: 5.10.76-1
Note: This is the only SSD in the PC and Qubes is the only OS in the SSD
So I removed the lines module2 --nounzip /initram-5.10.76-1.......img line hoping to get a prompt but it rebooted after printing Loading initial ramdisk ....
This makes me wonder is it is crashing while loading a module in line module2 /vmlinuz...
Is there a way to set breakpoint in grub and fall into prompt to see what modules are loaded?
You can also enable some more debug output in grub along with removing quite:
For Xen command line (multiboot2 line): loglvl=all guest_loglvl=all vga=,keep
For kernel command line (first module2 line): console=hvc0 earlyprintk=xen
Originally PC came with windows preinstalled and I bought a new SSD for Qube OS and only ever installed Qube OS in it.
There is only one SSD bay on the motherboard so, never had multiple SSD simultaneously on the PC either.
However, I did try to boot this Qubes OS SSD on a different PC last week, with (older 2017 i5) spec and that did not work either. I assume older PC is just not compatible to Qubes.