I'm a long time Linux user who is just getting started with UnRaid.

 

I was running a Fedora 35 server on my hardware (physical/bare silicon), and have used qemu-img to image the SSD into a .img file.  I would like to run that image within unRaid in a VM as it has a number of services configured.  I created a new Fedora VM with a fresh .img file within the webgui, and then stopped the VM and edited VM to point to my Fedora.img file.

 

When I try to start up the VM, I can see the grub boot menu with the correct kernels from my Fedora 35 install, but then it gets stuck after that.  I suspect that a setting in the image needs to be adjusted so that the image can boot.

 

is there a manual or guide on how to convert a Linux server to an img file and set it up to boot from within unRaid?  Or can someone tell me what I need to change to get my Fedora VM to boot?

 

(Eventually, I will migrate various services off of this Fedora server into unRaid, but I need to keep the current Fedora server running during the current transition period to minimize downtime of other services.)

21 hours ago, shadowlord said:

When I try to start up the VM, I can see the grub boot menu with the correct kernels from my Fedora 35 install, but then it gets stuck after that

Sounds like a problem with previous video drivers, in fact you can see the grub menu, but it fails to display anything when it's trying to load video drivers.

This could be if you are using qxl video drivers+vnc for the vm and you used a real gpu on bare installation.

Is this the case?

If it's so, you have 2 options:

1) Passthrough the same gpu to the vm in a multifunction device, so that the drivers are correctly loaded and you get a video output on the monitor

2) Delete gpu drivers inside the vm and use qxl+vnc

 

You may also want to check that the uuid are correct in the fstab file (if you set it with uuid(s)) in the img clone.

Edited February 26, 20224 yr by ghost82

Because the VM gets stuck after boot, I can't even SSH into the VM in order to update the fstab file nor change the video drivers.  I have a hunch that the issue may be disk/fstab related and that needs editing.

 

In the meantime, I have created a fresh Fedora VM from scratch and making a clean install from the ISO, which is working, although obviously the services have to be reinstalled and reconfigured.  From this experience, I suspect that the issue in the migrated-VM is with the UUID.

 

For the next step, I will attempt to edit the /etc/fstab file externally to adjust the UUID.

14 minutes ago, shadowlord said:

I can't even SSH into the VM in order to update the fstab file nor change the video drivers

You need to chroot into the disk, boot from the installer media and chroot into the disk.