KVM to Proxmox convert initramfs failed boot centos7

[mahesh.w]

Currently my VM's are running on KVM.
Now, we want to migrate on Proxmox. So, i created VM and imported qcow file from KVM to Proxmox.
But, when i start this VM getting error that "You might want to save /run/initramfs/rdsosreport.txt".

How to resolve this ?

 

[ness1602]

try with: dracut -f --regenerate-all and then restart

 

[mahesh.w]

try with: dracut -f --regenerate-all and then restart

Tried with your command. but system showing that command not found

 

[mahesh.w]

Also, sysroot is available but i cant go change rw permission

 

[ness1602]

What linux distro is this then?

 

[mahesh.w]

this kvm was running on CentOS 7.9

 

[jdancer]

For RHEL and derivatives, on the original VM run the following:

# dracut --force --verbose --no-hostonly

The above was required to migrate from ESXi to KVM. Should work for KVM to KVM.

 

[mahesh.w]

For RHEL and derivatives, on the original VM run the following:

# dracut --force --verbose --no-hostonly

The above was required to migrate from ESXi to KVM. Should work for KVM to KVM.

Thank you so much. Issue has been resolve.

 

[Proximate]

For RHEL and derivatives, on the original VM run the following:

# dracut --force --verbose --no-hostonly

The above was required to migrate from ESXi to KVM. Should work for KVM to KVM.

I know this is old but I'm still struggling with this also.
Are you saying to run this before importing to proxmox?
If this is done and the vm doesn't completely run on proxmox, does it make it broken on vmware?

 

[jdancer]

I know this is old but I'm still struggling with this also.
Are you saying to run this before importing to proxmox?
If this is done and the vm doesn't completely run on proxmox, does it make it broken on vmware?

Run it before importing.

 

[Proximate]

Sure but that doesn't answer my question. If the import doesn't work and you have to keep it on esx for a while longer, will it still start/run ok on esx after running the commands? Obviously, backing up or snapshot before making the change is the best idea but some might not remember to do that.

 

[jdancer]

Sure but that doesn't answer my question. If the import doesn't work and you have to keep it on esx for a while longer, will it still start/run ok on esx after running the commands? Obviously, backing up or snapshot before making the change is the best idea but some might not remember to do that.

I used this guide https://unixcop.com/migrate-virtual-machine-from-vmware-esxi-to-proxmox-ve for migrating ESXi VMs to Proxmox.

You still need to run dracut to include all the drivers before migration.

I use the 'qm importdisk' command on the .vmdk file itself which is the metadata file which describes the flat.vmdk virtual disk.

The flat.vmdk is the actual virtual disk from ESXi which is the correct one to use for the 'qemu-image' convert command.

 

[Proximate]

Understood. Never had to use dracut for anything newer than 7.9 so I assume this is for older versions only.
Either way, it worked perfectly thanks to this thread so thank you.

 

[TI-Expert]

I would like to thank those involved in the topic and would like to add:

In my situation, I was importing a .vmdk VM to proxmox, and it presented the initialization error when I used Virtio SCSI, but when I ran it in sata mode, it did not present the error.

So with the help of this topic, it was suggested to run the command # dracut --force --verbose --no-hostonly before importing.

But as the system started in Sata mode, I started the system and ran the command # dracut --force --verbose --no-hostonly, then turned off the VM, changed it to Virtio SCSI and it started normally.

 

[RoCE-geek]

For RHEL and derivatives, on the original VM run the following:

# dracut --force --verbose --no-hostonly

The above was required to migrate from ESXi to KVM. Should work for KVM to KVM.

Valid even for Hyper-V to Proxmox path (for UEFI Linux VM with VirtIO SCSI Single + SCSI disks + i440fx). Approved.