VM migration from vmware to proxmox : Kernel Panic

mamatov

Member
Jan 16, 2015
35
0
6
Hi,

I need to move a VM Centos 5.5 from vmware esxi 6.0.0 to proxmox 3.4.

So according to proxmox recommandation :

1 - I used vmware-vdiskmanager.exe to have only one vmdk file => OK
2 - I imported the vmdk to proxmox
3 - I created a new vm with the right disk size
4 - I copied my vmdk to vm-id-disk-1.vmdk
5 - I started my VM, the boot is running correctly (GRUB) but then I have a Kernel panic :

kernel_panic.jpg

For information the disk device is SCSI.

I don't understand why the vm is running correctly from vmware and not from proxmox.

I also tried

*to convert the vmdk to raw file but still the same issue.
*to boot in rescue mode and play with fstab (change label to /dev/sdax)

Any advice to fix it ?

Thanks in advance for your help
 
Check the grub entry line, the `root=` option might be different between vmware and qemu.
Also, did you do a suspend-to-disk on the VM before moving the vmdk to proxmox? The log seems to indicate that... which might be an issue.
If you move VMs around always be sure to perform a clean and complete shutdown.
 
Thanks for your help.

The VM was stopped before to move the vmdk to proxmox.
I tried to change the grub line using the label

grub append> ro root=LABEL=/

But still the same issue. Please find below the grub, fstab and fdisk :

fdisk.pngfstab.pnggrub.png
 
pls post your VM config:

> qm config VMID
 
The VM config :

boot: cdn
bootdisk: scsi0
cores: 2
ide2: local:iso/CentOS-5.11-i386-bin-DVD-1of2.iso,media=cdrom,size=4017616K
memory: 1024
name: horoquartz
net0: e1000=D2:E5:F7:76:29:69,bridge=vmbr0,link_down=1
numa: 0
ostype: l26
scsi0: vm-datastore:111/vm-111-disk-1.vmdk,format=vmdk,size=30G
smbios1: uuid=a769d7ed-9449-4ca5-b6cf-1493c38b45c0
sockets: 1
tablet: 0
 
looks ok. (I thought you use virtio, which would cause boot issues on centos 5).
 
To fix this issue I boot to a centos iso and start an operating system upgrade.
With the new kernel the boot process is ok.

Thanks a lot for your support.
 
We have done this also often. We used the easy way:

Linux:
- Create new VM depending on the VM on VMware or other VE
- Start every VM with an ilvedisc
- Copy the hole disk with rsync
- right grub on target VM
- Start VM

Windows
- deinstall all VMwarebased drivers
- Set NIC to DHCP
- Execute mergeide.reg on VMware or other VM
- shutdown the VMware VM
- build new VM on the targetost depending on the Vware VM
- Start the migrationprocess with Clonezilla on both sides.
- Start the new VM, basicdriver where automaticliy installed in Winows
- Install KVM and specialdrivers from Best practice in the PVE Wiki
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!