VMware vSphere

 View Only

  • 1.  Kernel panic - not syncing: Attempted to kill init!

    Posted May 14, 2013 02:59 PM


    Using converter standalone 5.1 converting RHEL 5 to use with VMware workstation. I get the below error.



  • 2.  RE: Kernel panic - not syncing: Attempted to kill init!

    Posted May 14, 2013 03:13 PM

    What did you convert to workstation? Was it a powered off VM? Converter can't convert powered on machines to workstation, only to VC/ESX.



  • 3.  RE: Kernel panic - not syncing: Attempted to kill init!

    Posted May 14, 2013 03:15 PM

    Yes, it was powered off virtual machine.



  • 4.  RE: Kernel panic - not syncing: Attempted to kill init!

    Posted May 14, 2013 04:11 PM

    The conversion itself completes without any errors... But then when trying to boot the VM with workstation or player, is when I get the above error.



  • 5.  RE: Kernel panic - not syncing: Attempted to kill init!

    Posted May 14, 2013 04:42 PM

    So if I understand correctly, you are cloning a VM from under ESX to WS? What are the ESX version and the Player version?

    Generally, what converter does in this case is just copy the vmdk files, assuming the virtual hardware should work. There is something unusual in this case. Can you share some more info about the machine configuration - what kind of disks are there - IDE, SCSI, RAID?

    The message "stat /proc/bus/usb/devices: No such file or directory" looks strange to me. I suppose there are no boot or system partition on USB disks. Only locally attached disks are being converted.

    If it were P2V I would suppose there could be some missing module or some misconfiguration of the initrd. In case of V2V this should not be the case, but if nothing helps, you could try rebuilding the initrd image on the destination VM (e.g. by booting from a live CD)



  • 6.  RE: Kernel panic - not syncing: Attempted to kill init!

    Posted May 14, 2013 04:48 PM


    Yes, you are correct. ESX 5.1 and I have tried the conversion to both WS 7 and Player 5. Here is some info about the machine that  is being converted:

    It has one SCSI hard disk.



  • 7.  RE: Kernel panic - not syncing: Attempted to kill init!

    Posted May 16, 2013 10:15 AM

    ESX 5.1 supports hardware version 9, while WS 7 - i think hw version 7. The only meaningful difference I can think of is LSI Logic SAS support but IIRC it should be supported by hwv 7 too. Check with a newer player just to be on the safe side.



  • 8.  RE: Kernel panic - not syncing: Attempted to kill init!

    Posted May 16, 2013 03:48 PM

    So I think I have found a difference with this machine as opposed to others that will export just fine with hardware version 9. The one that is having issues, the SCSI controller is set to Paravirtual, while the other machines that export fine are LSI Logic SAS. Would Paravirtual prevent the machine from booting once exported?



  • 9.  RE: Kernel panic - not syncing: Attempted to kill init!

    Posted May 16, 2013 04:29 PM

    That's quite possible. Converter has created the destination VM with LSI Logic controller (if i am not mistaken; you can check it in the .vmx file - look for scsi0.virtualDev or scsi1.virtualDev). If the source machine doesn't have driver for LSI Logic it wouldn't boot.

    You may try this the hack from this article http://v-reality.info/2012/02/paravirtual-adapters-with-vmware-workstation/ and set 'pvscsi' in the vmxl if you are lucky it may power on.

    Another way would be to do a P2V. Power on the source VM and convert it as a physical machine.

    HTH

    Plamen