** Description changed:

  [IMPACT]
  
  In xenial lscpu prints the wrong "Hypervisor vendor" and "Virtualization
  type" on PowerVM or KVM systems. Incorrect hypervisor and virtualization
  type reported in ubuntu 16.04.04 guest running in P8compat mode on P9
  boston-LC.
  
  [TEST]
  
  Curent output:
  
  ubuntu@P8lpar3:~$ dpkg -l "*util-linux*"
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name           Version      Architecture Description
  +++-==============-============-============-=================================
  ii  util-linux     2.31.1-0.4ub ppc64el      miscellaneous system utilities
  un  util-linux-loc <none>       <none>       (no description available)
  
  ubuntu@P8lpar3:~$ lscpu
  Architecture:        ppc64le
  Byte Order:          Little Endian
  CPU(s):              128
  On-line CPU(s) list: 0-127
  Thread(s) per core:  8
  Core(s) per socket:  1
  Socket(s):           16
  NUMA node(s):        2
  Model:               2.1 (pvr 004b 0201)
  Model name:          POWER8 (architected), altivec supported
- Hypervisor vendor:   pHyp
- Virtualization type: para
+ Hypervisor vendor: horizontal
+ Virtualization type: full
  L1d cache:           64K
  L1i cache:           32K
- NUMA node0 CPU(s):   
+ NUMA node0 CPU(s):
  NUMA node4 CPU(s):   0-127
- ubuntu@P8lpar3:~$ 
+ ubuntu@P8lpar3:~$
  
  Expected Output:
  
- $ lscpu 
+ $ lscpu
  Architecture:          ppc64le
  Byte Order:            Little Endian
  CPU(s):                128
  On-line CPU(s) list:   0-127
  Thread(s) per core:    8
  Core(s) per socket:    1
  Socket(s):             16
  NUMA node(s):          2
  Model:                 2.1 (pvr 004b 0201)
  Model name:            POWER8 (architected), altivec supported
  Hypervisor vendor:     pHyp
  Virtualization type:   para
  L1d cache:             64K
  L1i cache:             32K
- NUMA node0 CPU(s):     
+ NUMA node0 CPU(s):
  NUMA node4 CPU(s):     0-127
  
  [Potential Regression]
  The fix changes the logic to how lscpu-dmi returns from read_hypervisor_dmi() 
this could introduce potential regression in platforms  that has incorrect DMI 
information.
  
  [Other Info]
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
  
  Machine Type = boston-LC
  
  ---Debugger---
  A debugger is not configured
  
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:
  
  root@guest:/tmp# lscpu
  Architecture:          ppc64le
  Byte Order:            Little Endian
  CPU(s):                2
  On-line CPU(s) list:   0,1
  Thread(s) per core:    2
  Core(s) per socket:    1
  Socket(s):             1
  NUMA node(s):          1
  Model:                 2.2 (pvr 004e 1202)
  Model name:            POWER8 (architected), altivec supported
  >> Hypervisor vendor:     horizontal
  >> Virtualization type:   full
  L1d cache:             32K
  L1i cache:             32K
  NUMA node0 CPU(s):     0,1
  
  Stack trace output:
   no
  
  Oops output:
   no
  
  We test what is coming along with distro. If you are not able to see
  issue with : https://launchpad.net/ubuntu/+source/util-
  linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764628

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to