Hi, I suggest checking virsh edit output with <machine> tags for finding the OS info. Usually When a VM's deployed on KVM with given spec, in case the respective Guest OS is not mapped (or) not supported on KVM host, by default default OS [ Other ] is configured.
Thanks & Regards, Pavan. On Fri, 3 Jan 2025 at 18:57, Francisco Arencibia Quesada < arencibia.franci...@gmail.com> wrote: > Hi Nux, > > All that is okay. It seems cloudstack and KVM are like not syncing the > os mapping, it is really weird thing, if I run virsh edit vmid, I see > the problem, but from CS all looks okay. > > Regards > > On Fri, Jan 3, 2025 at 2:18 PM Nux <n...@li.nux.ro> wrote: > > > > How are you deploying VMs? From template? Did you specify the right OS > > type in the template setting? > > Cloudstack will not do any autodiscovery of what's inside, it will only > > apply things based on the OS type of the template/ISO that you have > > specified. > > > > HTH > > > > On 2025-01-03 11:42, Francisco Arencibia Quesada wrote: > > > Good morning guys, > > > > > > I am currently facing an issue with OS mapping on KVM. It appears that > > > the system is not correctly detecting the operating system running on > > > the virtual machines. Each time a new VM is deployed, it is identified > > > as "generic" instead of recognizing the actual operating system > > > installed. > > > > > > This misdetection affects several functionalities that depend on > > > accurate OS identification. Has anyone encountered a similar problem? > > > Any guidance or suggestions to resolve this would be greatly > > > appreciated. > > > > > > Looking forward to your input. > > > > > > Best regards, > > > Thanks in advance > > > > -- > Francisco Arencibia Quesada. > DevOps Engineer >
