Bug 1979902 - CPU type is empty if the vdsm version of rhv node is 4.40.70
Summary: CPU type is empty if the vdsm version of rhv node is 4.40.70
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.40.70.6
Hardware: x86_64
OS: Unspecified
high
high
Target Milestone: ovirt-4.4.7
: ---
Assignee: Milan Zamazal
QA Contact: meital avital
URL:
Whiteboard:
Depends On: 1961558
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-07 11:25 UTC by mxie@redhat.com
Modified: 2021-07-13 06:58 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-12 08:24:17 UTC
oVirt Team: Virt
Embargoed:
sbonazzo: ovirt-4.4+
michal.skrivanek: blocker+

Attachments (Terms of Use)
cpu-type-empty-rhv-node.png (167.89 KB, image/png)
2021-07-07 11:25 UTC, mxie@redhat.com 		no flags Details
View All

Description mxie@redhat.com 2021-07-07 11:25:03 UTC 
Created attachment 1799069 [details]
cpu-type-empty-rhv-node.png

Description of problem:
CPU type is empty if the vdsm version of rhv node is 4.40.70

Version-Release number of selected component (if applicable):
vdsm-4.40.70.6-1.el8ev.x86_64
libvirt-7.0.0-14.1.module+el8.4.0+11095+d46acebf.x86_64
qemu-kvm-5.2.0-16.module+el8.4.0+10806+b7d97207.x86_64
rhv-4.4.7.6-0.11.el8ev


How reproducible:
100%

Steps to Reproduce:
1.Existing rhv server version is 4.4.6-8, the vdsom version of rhv node is vdsm-4.40.60.7-1.el8ev.x86_64, rhv server and rhv node work well at this time

2. Update rhv server from 4.4.6-8 to 4.4.7.6, rhv server can be updated successfully

3. Then update rhv node, but found rhv node can't be updated successfully because CPU type shows empty after vdsm-4.40.70.6-1.el8ev.x86_64 is installed rhv node, rhv noded moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all


Actual results:
As above description

Expected results:
CPU type shows correct if the vdsm version of rhv node is 4.40.70

Additional info:
Comment 4 Arik 2021-07-07 19:14:04 UTC 
Please provide the output of virsh capabilities and virsh domcapabilities on that host
Comment 5 Arik 2021-07-07 19:23:19 UTC 
Sounds similar to what happened on your setup recently that was solved by downgrading edk2-ovmf to 20200602gitca407c7246bf-4.el8_4.1, right?

[1] https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D47YYGMGJZIOM3QTDRVNBMRDEPK4ZMCQ/
Comment 6 mxie@redhat.com 2021-07-08 05:06:31 UTC 
(In reply to Arik from comment #4)
> Please provide the output of virsh capabilities and virsh domcapabilities on
> that host

#  virsh capabilities
Please enter your authentication name: test
Please enter your password: 
<capabilities>

  <host>
    <uuid>2294e584-cff3-4681-ab0a-2cc756fc12eb</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>Skylake-Client-IBRS</model>
      <vendor>Intel</vendor>
      <microcode version='214'/>
      <counter name='tsc' frequency='2904000000' scaling='no'/>
      <topology sockets='1' dies='1' cores='4' threads='2'/>
      <feature name='ds'/>
      <feature name='acpi'/>
      <feature name='ss'/>
      <feature name='ht'/>
      <feature name='tm'/>
      <feature name='pbe'/>
      <feature name='dtes64'/>
      <feature name='monitor'/>
      <feature name='ds_cpl'/>
      <feature name='vmx'/>
      <feature name='smx'/>
      <feature name='est'/>
      <feature name='tm2'/>
      <feature name='xtpr'/>
      <feature name='pdcm'/>
      <feature name='osxsave'/>
      <feature name='tsc_adjust'/>
      <feature name='clflushopt'/>
      <feature name='intel-pt'/>
      <feature name='md-clear'/>
      <feature name='stibp'/>
      <feature name='ssbd'/>
      <feature name='xsaves'/>
      <feature name='pdpe1gb'/>
      <feature name='invtsc'/>
      <pages unit='KiB' size='4'/>
      <pages unit='KiB' size='2048'/>
      <pages unit='KiB' size='1048576'/>
    </cpu>
    <power_management>
      <suspend_mem/>
      <suspend_disk/>
      <suspend_hybrid/>
    </power_management>
    <iommu support='no'/>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>tcp</uri_transport>
        <uri_transport>rdma</uri_transport>
      </uri_transports>
    </migration_features>
    <topology>
      <cells num='1'>
        <cell id='0'>
          <memory unit='KiB'>16168176</memory>
          <pages unit='KiB' size='4'>4042044</pages>
          <pages unit='KiB' size='2048'>0</pages>
          <pages unit='KiB' size='1048576'>0</pages>
          <distances>
            <sibling id='0' value='10'/>
          </distances>
          <cpus num='8'>
            <cpu id='0' socket_id='0' die_id='0' core_id='0' siblings='0,4'/>
            <cpu id='1' socket_id='0' die_id='0' core_id='1' siblings='1,5'/>
            <cpu id='2' socket_id='0' die_id='0' core_id='2' siblings='2,6'/>
            <cpu id='3' socket_id='0' die_id='0' core_id='3' siblings='3,7'/>
            <cpu id='4' socket_id='0' die_id='0' core_id='0' siblings='0,4'/>
            <cpu id='5' socket_id='0' die_id='0' core_id='1' siblings='1,5'/>
            <cpu id='6' socket_id='0' die_id='0' core_id='2' siblings='2,6'/>
            <cpu id='7' socket_id='0' die_id='0' core_id='3' siblings='3,7'/>
          </cpus>
        </cell>
      </cells>
    </topology>
    <cache>
      <bank id='0' level='3' type='both' size='8' unit='MiB' cpus='0-7'/>
    </cache>
    <secmodel>
      <model>selinux</model>
      <doi>0</doi>
      <baselabel type='kvm'>system_u:system_r:svirt_t:s0</baselabel>
      <baselabel type='qemu'>system_u:system_r:svirt_tcg_t:s0</baselabel>
    </secmodel>
    <secmodel>
      <model>dac</model>
      <doi>0</doi>
      <baselabel type='kvm'>+107:+107</baselabel>
      <baselabel type='qemu'>+107:+107</baselabel>
    </secmodel>
  </host>

  <guest>
    <os_type>hvm</os_type>
    <arch name='i686'>
      <wordsize>32</wordsize>
      <emulator>/usr/libexec/qemu-kvm</emulator>
      <machine maxCpus='240'>pc-i440fx-rhel7.6.0</machine>
      <machine canonical='pc-i440fx-rhel7.6.0' maxCpus='240'>pc</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.0.0</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.5.0</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.3.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.3.0</machine>
      <machine maxCpus='710'>pc-q35-rhel7.6.0</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.1.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.1.0</machine>
      <machine maxCpus='710'>pc-q35-rhel7.4.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.4.0</machine>
      <machine canonical='pc-q35-rhel8.4.0' maxCpus='710'>q35</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.4.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.2.0</machine>
      <machine maxCpus='710'>pc-q35-rhel7.5.0</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.2.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.0.0</machine>
      <machine maxCpus='255'>pc-q35-rhel7.3.0</machine>
      <domain type='qemu'/>
      <domain type='kvm'/>
    </arch>
    <features>
      <pae/>
      <nonpae/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
      <cpuselection/>
      <deviceboot/>
      <disksnapshot default='on' toggle='no'/>
    </features>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name='x86_64'>
      <wordsize>64</wordsize>
      <emulator>/usr/libexec/qemu-kvm</emulator>
      <machine maxCpus='240'>pc-i440fx-rhel7.6.0</machine>
      <machine canonical='pc-i440fx-rhel7.6.0' maxCpus='240'>pc</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.0.0</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.5.0</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.3.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.3.0</machine>
      <machine maxCpus='710'>pc-q35-rhel7.6.0</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.1.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.1.0</machine>
      <machine maxCpus='710'>pc-q35-rhel7.4.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.4.0</machine>
      <machine canonical='pc-q35-rhel8.4.0' maxCpus='710'>q35</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.4.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.2.0</machine>
      <machine maxCpus='710'>pc-q35-rhel7.5.0</machine>
      <machine maxCpus='240'>pc-i440fx-rhel7.2.0</machine>
      <machine maxCpus='710'>pc-q35-rhel8.0.0</machine>
      <machine maxCpus='255'>pc-q35-rhel7.3.0</machine>
      <domain type='qemu'/>
      <domain type='kvm'/>
    </arch>
    <features>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
      <cpuselection/>
      <deviceboot/>
      <disksnapshot default='on' toggle='no'/>
    </features>
  </guest>

</capabilities>


#  virsh domcapabilities 
Please enter your authentication name: test
Please enter your password: 
error: failed to get emulator capabilities
error: internal error: unknown feature amd-sev-es
Comment 7 Michal Skrivanek 2021-07-08 06:31:39 UTC 
(In reply to Arik from comment #5)
> Sounds similar to what happened on your setup recently that was solved by
> downgrading edk2-ovmf to 20200602gitca407c7246bf-4.el8_4.1, right?
> 
> [1]
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/
> D47YYGMGJZIOM3QTDRVNBMRDEPK4ZMCQ/

latest redhat-virtualization-host-4.4.7-20210705.0.el8_4 has edk2-ovmf-20200602gitca407c7246bf-4.el8_4.1.noarch

Please confirm the version you use on your system
Comment 8 Michal Skrivanek 2021-07-08 06:37:45 UTC 
(In reply to Michal Skrivanek from comment #7)
but I already see you're not using recent RHVH as your qemu-kvm version is older than qemu-kvm-5.2.0-16.module+el8.4.0+11536+725e25d9.2.x86_64 there
Comment 9 mxie@redhat.com 2021-07-08 06:56:45 UTC 
(In reply to Arik from comment #5)
> Sounds similar to what happened on your setup recently that was solved by
> downgrading edk2-ovmf to 20200602gitca407c7246bf-4.el8_4.1, right?
> 
> [1]
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/
> D47YYGMGJZIOM3QTDRVNBMRDEPK4ZMCQ/

You‘re right, rhv node can show CPU type normally after downgrading edk2-ovmf from 20210527gite1999b264f1f-1.el8.noarch to edk2-ovmf-20200602gitca407c7246bf-4.el8.noarch, do I need to move the bug to edk2-ovmf component?
Comment 10 Arik 2021-07-08 07:47:28 UTC 
(In reply to mxie from comment #9)
> (In reply to Arik from comment #5)
> > Sounds similar to what happened on your setup recently that was solved by
> > downgrading edk2-ovmf to 20200602gitca407c7246bf-4.el8_4.1, right?
> > 
> > [1]
> > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/
> > D47YYGMGJZIOM3QTDRVNBMRDEPK4ZMCQ/
> 
> You‘re right, rhv node can show CPU type normally after downgrading
> edk2-ovmf from 20210527gite1999b264f1f-1.el8.noarch to
> edk2-ovmf-20200602gitca407c7246bf-4.el8.noarch, do I need to move the bug to
> edk2-ovmf component?

No, that's ok, there's one already - bz 1961558
Comment 11 Michal Skrivanek 2021-07-12 07:33:30 UTC 
why is it still open? it's fixed, isn't it?
Comment 12 Arik 2021-07-12 07:42:34 UTC 
(In reply to Michal Skrivanek from comment #11)
> why is it still open? it's fixed, isn't it?

not yet on RHEL AV 8.4, I asked Yash for a backport
Comment 14 Arik 2021-07-12 09:08:24 UTC 
(In reply to Arik from comment #12)
> (In reply to Michal Skrivanek from comment #11)
> > why is it still open? it's fixed, isn't it?
> 
> not yet on RHEL AV 8.4, I asked Yash for a backport

should be fixed on u/s by the fix for bz 1961558
Note You need to log in before you can comment on or make changes to this bug.