So I have freshly installed Windows 10 2004 and Fedora 32 last night. What I want to do is have My Fedora Install run in the background under Windows, so that my docker containers and any services (like Emby Server) I have continue to function. I do the same with Windows inside Fedora using KVM and that part is working great.
The part that I am having trouble with is booting the Fedora disk. I keep running into Warning: /dev/disk/by-uuid/<hash> does not exist
upon booting (it is for my /
mount point partition). I tried changing from UUID’s to PARTUUID’s in /etc/fstab
and then rebuilding the initramfs image but that seemed to have no effect.
I’m using Hyper-V Gen 2.0 VM with Secure Boot disabled and Physical Drive Passthrough. The Boot drive for Fedora is NVMe - however Hyper-V passes it through as a SCSI device which I believe is the root of the problem, but I’m unsure.
Anyone know how to overcome this problem?
Update: I got it to try and boot using the partuuid but it fails with the same error Warning/disk/by-partuuid/<uuid> does not exist
I check the logs and they don’t seem to contain any useful details
Update 2:
Have made the discovery that it is related to the initramfs image. The rescue image works all the time - Both bare metal and in Hyper-V. If i boot into Rescue from Hyper-V and recompile the initramfs using dracut -f -v
then the normal boot image will begin working, however if I go back to bare metal, the image will no longer boot. Again - recompile the image and bare metal will work and hyper-V will not. Need to find a way to configure it to work in both situations.