Quantcast
Channel: VMware Communities : Discussion List - Virtual Machine, Guest OS and VM Tools
Viewing all articles
Browse latest Browse all 1961

Unable to start a Linux Nested KVM on a P2V ESXi 5.5 Machine

$
0
0

I did a P2V of a 64bit RHEL6.3 box but am unable to start the kvm vm with the error, "

 

Error,

"Error polling connection qemu:///system: internal error Cannot find suitable emulator for x86_64."

 

 

The i5 processor checks out, "Intel(R) VT-x with Extended Page Tables: Yes" (Using Intel Processor Identification Utility)

# esxcfg-info |grep "HV Support"

         |----HV Support............................................3

            |----World Command Line.................................grep HV Support

 

 

I upgraded to hardware version 10 and then backed it down to 9 with a text edit and add vm  back to inventory.

I have the vm Virtual settings to use:

Use Intel VT-x for instructions and

Use Intel for MMU virtualization

 

 

If I understand this correctly I need the following to run a Linux kvm vm in a Linux Guest vm:

Hardware with VT-x, CHECK.

 

 

Hardware version 9 or 10, version 9, CHECK.

 

One or more additional lines in the *.vmx file.

 

 

vhv.enable ="TRUE"

hypervisor.cpuid.v0 = FALSE

 

I also heard this could help:

apic.xapic.enabled="FALSE"

 

Secondly the kvm vm is on a LVM volume that also has the root partition. If I am not able to run the kvm vm then another option would be to copy that vm out and do a separate p2v and run as a separate vm if you have any suggestions there.

 

Thank you in advance for any assistance you are able to provide.

Mark

 

Reference Links:

https://communities.vmware.com/docs/DOC-8970

http://virtuallylg.wordpress.com/2011/09/16/nested-vmware-64bit-vms-time-to-run-hyper-v-or-kvm-inside-vmware-esxi5-0-and-workstation-8-0/

 

 

 

http://mkamaleldin.blogspot.com/2013/05/KVMinVMWARE.html


Viewing all articles
Browse latest Browse all 1961

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>