Solaris 10 VM goes into reboot loop after being converted from VMWare to KVM
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Solaris 10 VM goes into reboot loop after being converted from VMWare to KVM
I have an old VMWare Server 2 VM using Solaris 10 for x86 (10/09) which goes into a reboot loop early in the boot process.
I converted it to a single file VMDK (it was split into 2GB chunks).
Converted it to raw with qemu-img convert. I got an error while converting but no info about what actually went wrong. It also went from a 10Gb VMDk to a 127GB raw file!?
I created a VM in Proxmox 1.9 which created a 20GB raw LV in my LVM. Then I dded the raw file to the LV.
I don't get far past the GRUB menu and Failsafe seems to take slightly longer to fail, does anyone know what may be causing this?
The fact that you got an error during conversion and ended up with a 127GB disk is slightly worrying, I'd start looking at that before attempting to boot whatever the result contained.
It does look suspicious but I can't find any kind of debug or logging option on qemu-img convert that will tell me what it's doing so I tried converting with VBoxManage. I decided to stop it when the raw file is generated reached about 95GB from the original 10! I suspect that it's because 127GB is the max size I set the VMDK to grow to. Is there any way of converting what's only been used?
Last edited by Mark_667; 02-09-2012 at 06:42 AM.
Reason: typo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.