LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Virtualization and Cloud (http://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/)
-   -   migrating from vmware to kvm, lvm partitioned guest failed to boot (http://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/migrating-from-vmware-to-kvm-lvm-partitioned-guest-failed-to-boot-832551/)

chakoshi 09-16-2010 07:26 AM

migrating from vmware to kvm, lvm partitioned guest failed to boot
 
I'm trying hard to convert some of my VMs from vmware ESX to KVM on ubuntu 10.04 server. the guests are fedora 10, they have a ext3 /boot partition and /root and swap file systems are on a lvm. I tried all these three:
1- trying to boot vmdk disk image directly (kvm now supports vmdk)
2- convert vmdk to raw then boot
3- convert vmdk to qcow2 and boot

in all these three scenarios, the grub loads (so /boot is found succesfully from the disk) but after the grub menu, there is an error message:

""could not detect stabilization....
volume group "volgroup00" not found
unable to access resume device /dev/volgroup00/logvol01""

I've tried all three scenarios by using ide and scsi, nothing changed. I have also installed an ubuntu vm, and add this disk image as a secondary disk to it, the ubuntu can see all /boot , /root and swap on the disk image. so the disk is alright but the fedora kernel, when booted on kvm cant see the lvm partition, on vmware it works with no problem.
can any one give me some hints or solutions?

chakoshi 09-16-2010 12:55 PM

Problem Solved! one nasty mistake of mine! that was trying to boot an i686 fedora installation by a x86_64 VM architecture!

archtoad6 01-02-2011 02:04 PM

Good job!

Not only did you find your own solution, you posted as well. You have added to the LQ archive of answers, Thank you +6.

kheldar 03-20-2011 05:34 PM

Same problem - different cause?
 
Quote:

Originally Posted by chakoshi (Post 4099617)
Problem Solved! one nasty mistake of mine! that was trying to boot an i686 fedora installation by a x86_64 VM architecture!

Unfortunately I get the same problem having migrated from an x86_64 image on an x86_64 VMWare server, to an x86_64 KVM server. The only difference I can see, is that the VMWare server is AMD running Centos 5.5, and the KVM server is Intel running Fedora 14.

I've started a new thread here as I shouldn't really have posted to a solved thread.


All times are GMT -5. The time now is 10:11 AM.