KVM launched on FC host

Community Support General
1

I have a simple KVM template/image (Ubuntu bionic) that works flawlessly until I added a FC host. Now, the same template got launch on the FC host, even when the template specifically specifies hypervisor as kvm. Anyone seeing the same thing?

2

Hello @jbuggie,

Could you share your VM template (onetemplate show -x <tmpl_id>)?

3 
<VMTEMPLATE>
  <ID>1</ID>
  <UID>0</UID>
  <GID>0</GID>
  <UNAME>oneadmin</UNAME>
  <GNAME>oneadmin</GNAME>
  <NAME>Ubuntu Minimal 18.04 - KVM</NAME>
  <PERMISSIONS>
    <OWNER_U>1</OWNER_U>
    <OWNER_M>1</OWNER_M>
    <OWNER_A>0</OWNER_A>
    <GROUP_U>0</GROUP_U>
    <GROUP_M>0</GROUP_M>
    <GROUP_A>0</GROUP_A>
    <OTHER_U>0</OTHER_U>
    <OTHER_M>0</OTHER_M>
    <OTHER_A>0</OTHER_A>
  </PERMISSIONS>
  <REGTIME>1598462023</REGTIME>
  <TEMPLATE>
    <CONTEXT>
      <NETWORK><![CDATA[YES]]></NETWORK>
      <SSH_PUBLIC_KEY><![CDATA[$USER[SSH_PUBLIC_KEY]]]></SSH_PUBLIC_KEY>
    </CONTEXT>
    <DISK>
      <IMAGE_ID><![CDATA[15]]></IMAGE_ID>
    </DISK>
    <GRAPHICS>
      <LISTEN><![CDATA[0.0.0.0]]></LISTEN>
      <TYPE><![CDATA[VNC]]></TYPE>
    </GRAPHICS>
    <HYPERVISOR><![CDATA[kvm]]></HYPERVISOR>
    <INPUTS_ORDER><![CDATA[]]></INPUTS_ORDER>
    <LOGO><![CDATA[images/logos/ubuntu.png]]></LOGO>
    <LXD_SECURITY_PRIVILEGED><![CDATA[true]]></LXD_SECURITY_PRIVILEGED>
    <MEMORY><![CDATA[768]]></MEMORY>
    <MEMORY_UNIT_COST><![CDATA[MB]]></MEMORY_UNIT_COST>
    <NIC>
      <NETWORK><![CDATA[Bridge]]></NETWORK>
      <NETWORK_UNAME><![CDATA[oneadmin]]></NETWORK_UNAME>
      <SECURITY_GROUPS><![CDATA[0]]></SECURITY_GROUPS>
    </NIC>
    <NIC_DEFAULT>
      <MODEL><![CDATA[virtio]]></MODEL>
    </NIC_DEFAULT>
    <OS>
      <ARCH><![CDATA[x86_64]]></ARCH>
      <BOOT><![CDATA[]]></BOOT>
    </OS>
  </TEMPLATE>
</VMTEMPLATE>
6

Note that the HYPERVISOR attribute for the VM template does not set any scheduler requirement, currently it just allow Sunstone interface to customize the views depending on the hypervisor. I’ve opened a GitHub issue to automatically creates a scheduling requirement if this attribute is set.

Until this is implemented, you will need to define the requirement manually in the VM template, you can find more information here: http://docs.opennebula.io/5.12/operation/references/template.html#template-placement-section