Option of "kvm.guest.os.machine.type" on VM/template not working in this case

[harikrishna-patnala]

problem

Adding this issue based on @rajujith 's comment here #12414 (comment)

When setting machine type q35 in "kvm.guest.os.machine.type", the option added is passed to KVM but its not useful in the use case yet due to incorrect controller type set for q35 machine type:

[resource.wrapper.LibvirtStartCommandWrapper] (AgentRequest-Handler-2:[]) (logid:feb005a8) LibvirtException org.libvirt.LibvirtException: unsupported configuration: IDE controllers are unsupported for this QEMU binary or machine type at org.libvirt.ErrorHandler.processError(Unknown Source) at org.libvirt.ErrorHandler.processError(Unknown Source) at org.libvirt.Connect.domainCreateXML(Unknown Source) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:2241)

<type arch='x86_64' machine='pc-q35-rhel9.6.0'>hvm</type>

--
--
<disk device='cdrom' type='file'>
  <driver name='qemu' type='raw' />
  <source file=''/>
  <target dev='hdc' bus='ide'/>
</disk>

The rootDiskController is set to "scsi".

versions

The versions of ACS, hypervisors, storage, network etc..

The steps to reproduce the bug

No response

What to do about it?

@rajujith please add your comment, if you think there is a way to address issue.

[harikrishna-patnala]

@rajujith please add your comment, if you think there is a way to address issue.

[rajujith]

@harikrishna-patnala I believe CloudStack needs to configure the domain XML according to the machine type. cc @nvazquez

[nvazquez]

@harikrishna-patnala @rajujith I think configuring the XML domain based on the selected machine type can be hard to achieve, I would suggest we give flexibility to select other settings related to the machine type (in this case it seems the IDE controller has been hardcoded, it would be helpful if it can be configurable as well)