<domain type='kvm' id='48'>
<name>i-2-2850-VM</name>
<uuid>0d7468be-7e21-4c73-ad34-ebed22e58087</uuid>
<description>Windows Server 2022 (64-bit)</description>
<memory unit='KiB'>16777216</memory>
<currentMemory unit='KiB'>16777216</currentMemory>
<vcpu placement='static'>4</vcpu>
<cputune>
<shares>453</shares>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<sysinfo type='smbios'>
<system>
<entry name='manufacturer'>Apache Software Foundation</entry>
<entry name='product'>CloudStack KVM Hypervisor</entry>
<entry name='uuid'>0d7468be-7e21-4c73-ad34-ebed22e58087</entry>
</system>
</sysinfo>
<os>
<type arch='x86_64' machine='pc-i440fx-6.2'>hvm</type>
<boot dev='cdrom'/>
<boot dev='hd'/>
<smbios mode='sysinfo'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<cpu mode='custom' match='exact' check='full'>
<model fallback='forbid'>qemu64</model>
<topology sockets='1' dies='1' cores='4' threads='1'/>
<feature policy='require' name='x2apic'/>
<feature policy='require' name='hypervisor'/>
<feature policy='require' name='lahf_lm'/>
<feature policy='disable' name='svm'/>
</cpu>
<clock offset='localtime'>
<timer name='hypervclock' present='yes'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source
file='/mnt/f9d87835-9017-31a8-9395-cba230a4ab0b/a8239352-ffab-40ac-878c-d40448af3de6'
index='2'/>
<backingStore type='file' index='3'>
<format type='qcow2'/>
<source
file='/mnt/f9d87835-9017-31a8-9395-cba230a4ab0b/b1d196e5-9b96-4df3-b7b1-cedf56eb0dc9'/>
<backingStore/>
</backingStore>
<target dev='hda' bus='ide'/>
<serial>a8239352ffab40ac878c</serial>
<alias name='ide0-0-0'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu'/>
<target dev='hdc' bus='ide'/>
<readonly/>
<alias name='ide0-1-0'/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
</disk>
<controller type='usb' index='0' model='piix3-uhci'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<controller type='ide' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
function='0x1'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04'
function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='02:04:00:db:00:0b'/>
<source bridge='brvx-9000030'/>
<bandwidth>
<inbound average='25600' peak='25600'/>
<outbound average='25600' peak='25600'/>
</bandwidth>
<target dev='vnet66'/>
<model type='e1000'/>
<link state='up'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/7'/>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/7'>
<source path='/dev/pts/7'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='unix'>
<source mode='bind'
path='/var/lib/libvirt/qemu/i-2-2850-VM.org.qemu.guest_agent.0'/>
<target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='tablet' bus='usb'>
<alias name='input0'/>
<address type='usb' bus='0' port='1'/>
</input>
<input type='mouse' bus='ps2'>
<alias name='input1'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input2'/>
</input>
<graphics type='vnc' port='5905' autoport='yes' listen='10.35.61.236'>
<listen type='address' address='10.35.61.236'/>
</graphics>
<audio id='1' type='none'/>
<video>
<model type='cirrus' vram='16384' heads='1' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02'
function='0x0'/>
</video>
<watchdog model='i6300esb' action='none'>
<alias name='watchdog0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06'
function='0x0'/>
</watchdog>
<memballoon model='virtio'>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05'
function='0x0'/>
</memballoon>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+0</label>
<imagelabel>+0:+0</imagelabel>
</seclabel>
</domain>
Windows 2022 Template, but is the same with ubuntu machines. In the
Windows Machines we have qemu-guest-tools installed and virtio
Regards
thanks in advance
On Wed, Jan 8, 2025 at 2:11 PM pavan aravapalli
<[email protected]> wrote:
>
> Hi,
>
> Can you paste the entire virsh dumpxml for the guest vm here. And template
> details of a vm too.
>
> Thanks & Regards,
> Pavan.
>
> On Wed, 8 Jan 2025 at 14:46, Francisco Arencibia Quesada <
> [email protected]> wrote:
>
> > This is the exact problem I have
> >
> > https://superuser.com/questions/651305/unknown-os-hostname-and-product-in-virt-manager
> > no answers in that thread.
> >
> >
> > On Tue, Jan 7, 2025 at 5:28 PM Francisco Arencibia Quesada
> > <[email protected]> wrote:
> > >
> > > this is the os section taken using virsh
> > >
> > > <os>
> > >
> > > <type arch='x86_64' machine='pc-i440fx-6.2'>hvm</type>
> > >
> > > <boot dev='cdrom'/>
> > >
> > > <boot dev='hd'/>
> > >
> > > <smbios mode='sysinfo'/>
> > >
> > > </os>
> > >
> > > regards
> > >
> > > On Mon, Jan 6, 2025 at 6:31 AM pavan aravapalli
> > > <[email protected]> wrote:
> > > >
> > > > 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 <
> > > > [email protected]> 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 <[email protected]> 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
> > > > >
> > >
> > >
> > >
> > > --
> > > Francisco Arencibia Quesada.
> > > DevOps Engineer
> >
> >
> >
> > --
> > Francisco Arencibia Quesada.
> > DevOps Engineer
> >
--
Francisco Arencibia Quesada.
DevOps Engineer
