incorrect hypervisor and virtualization type reported in compat mode guest

Bug #1764628 reported by bugproxy on 2018-04-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Ubuntu-power-systems project
Medium
Canonical Foundations Team
util-linux (Ubuntu)
Medium
Canonical Foundations Team

Bug Description

---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 ?

Default Comment by Bridge

tags: added: architecture-ppc64le bugnameltc-166459 severity-medium targetmilestone-inin---
Changed in ubuntu:
assignee: nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
affects: ubuntu → util-linux (Ubuntu)
Changed in ubuntu-power-systems:
importance: Undecided → Medium
assignee: nobody → Canonical Foundations Team (canonical-foundations)
status: New → Triaged
Steve Langasek (vorlon) wrote :

There seems to be no reason for https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 to fix this bug, since that is a targeted bugfix; and I understand your bug report to be asking if it's reproducible with this version, rather than telling that it is not.

What are the values you expect in the output of lscpu for the "Hypervisor vendor" and "Virtualization type" fields that you highlight? In what upstream version of util-linux is this known to be fixed?

Changed in util-linux (Ubuntu):
status: New → Incomplete

------- Comment From <email address hidden> 2018-04-18 01:24 EDT-------
(In reply to comment #13)
> There seems to be no reason for
> https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 to fix
> this bug, since that is a targeted bugfix; and I understand your bug report
> to be asking if it's reproducible with this version, rather than telling
> that it is not.
>
> What are the values you expect in the output of lscpu for the "Hypervisor
> vendor" and "Virtualization type" fields that you highlight? In what
> upstream version of util-linux is this known to be fixed?

We have not seen this issue in https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 version.
So we could like to know if you could include this version in 16.04.04 Ubuntu version..

The expected value is

Hypervisor vendor: KVM
Virtualization type: para

root@guest:~/util-linux# ./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: KVM
Virtualization type: para
L1d cache: 32K
L1i cache: 32K
NUMA node0 CPU(s): 0,1

We downloaded the below upstream code and did not see the issue.

https://github.com/Distrotech/util-linux

tags: added: triage-a
Steve Langasek (vorlon) wrote :

it is not at all clear, based on the source changes included, why https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 would fix this issue.

2.27.1-6ubuntu3.5 is also currently blocked from being released to xenial-updates because the update failed verification. https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1732865

Changed in ubuntu-power-systems:
status: Triaged → Incomplete
Manoj Iyer (manjo) on 2018-06-25
Changed in util-linux (Ubuntu):
assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → Canonical Foundations Team (canonical-foundations)
importance: Undecided → Medium
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2018-06-27 01:45 EDT-------
(In reply to comment #16)
> Srikanth, Seeteena,
>
> Canonical has asked for an update to this bug. Could you provide one?
> Specifically, their question is... "please can you provide some more details
> why this is fixed with this util-linux version?" Thanks.

Barry, I am not able to see any commit that went with util-linux_2.27.1-6ubuntu3.5 version. but from the testing perspective we are able to recreate the issue with the util-linux package that comes with 16.04.04.
Later we checked with upstream/util-linux_2.27.1-6ubuntu3.5 level and not able to see the issue. Hence we mirror this bug to canonical to pick or use this package for 16.04.04.

http://launchpadlibrarian.net/356140271/util-linux_2.27.1-6ubuntu3.5_source.changes

Changed in ubuntu-power-systems:
status: Incomplete → Triaged
Manoj Iyer (manjo) wrote :

IBM, Xenial-updates is currently on version (https://packages.ubuntu.com/xenial-updates/util-linux) util-linux (2.27.1-6ubuntu3.6) could you please retest and confirm that this is now fixed ?

Changed in ubuntu-power-systems:
status: Triaged → Incomplete
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2018-12-18 01:25 EDT-------
(In reply to comment #18)
> IBM, Xenial-updates is currently on version
> (https://packages.ubuntu.com/xenial-updates/util-linux) util-linux
> (2.27.1-6ubuntu3.6) could you please retest and confirm that this is now
> fixed ?

No. Issue still present:

root@guest:~# dpkg -l | grep util-linux
ii util-linux 2.27.1-6ubuntu3.6 ppc64el miscellaneous system utilities
root@guest:~# lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 64
On-line CPU(s) list: 0-63
Thread(s) per core: 4
Core(s) per socket: 8
Socket(s): 2
NUMA node(s): 1
Model: 2.0 (pvr 004d 0200)
Model name: POWER8 (architected), altivec supported
Hypervisor vendor: horizontal
Virtualization type: full
L1d cache: 64K
L1i cache: 32K
NUMA node0 CPU(s): 0-63

Dimitri John Ledkov (xnox) wrote :

I'm confused reading this bug report. As the comments repeatedly mention identical version numbers, stating that both the issue is present and not present, requesting to pick up the version that is already in xenial, and later stating again that things are not fixed.

Clearly v2.27.1-6ubuntu3.6 is still affected and is not the one that is needed.

Do you have upstream git commit ids that resolve the issue for you?

What does "Later we checked with upstream/util-linux_2.27.1-6ubuntu3.5 level and not able to see the issue." mean? i do not understand the meaning of this sentence. Which upstream git commit, or git tag, or released version number appear to work correctly?

Dimitri John Ledkov (xnox) wrote :

Upstream for util-linux is at https://github.com/karelzak/util-linux

Has this been reported as an issue there before, and now fixed?
Can you find the relevant versions that fix this in that repository?

bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2018-12-19 23:26 EDT-------
Upstream testing with util-linux [@ https://github.com/karelzak/util-linux]

1. Tested version: util-linux 2.26.2

Result:

root@guest:/home/srik/util-linux# ./lscpu -V
lt-lscpu from util-linux 2.26.2
root@guest:/home/srik/util-linux# ./lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 64
On-line CPU(s) list: 0-63
Thread(s) per core: 4
Core(s) per socket: 8
Socket(s): 2
NUMA node(s): 1
Model: IBM pSeries (emulated by qemu)
L1d cache: 64K
L1i cache: 32K
NUMA node0 CPU(s): 0-63

2. Tested version: util-linux 2.27.1

Result:

root@guest:/home/srik/util-linux# ./lscpu -V
lt-lscpu from util-linux 2.27.1
root@guest:/home/srik/util-linux# ./lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 64
On-line CPU(s) list: 0-63
Thread(s) per core: 4
Core(s) per socket: 8
Socket(s): 2
NUMA node(s): 1
Model: IBM pSeries (emulated by qemu)
> Hypervisor vendor: KVM --> correct
> Virtualization type: para --> correct
L1d cache: 64K
L1i cache: 32K
NUMA node0 CPU(s): 0-63

On Ubuntu 16.04.5 :

#lscpu -V
lscpu from util-linux 2.27.1

root@guest:~# dpkg -l | grep util-linux
ii util-linux 2.27.1-6ubuntu3.6 ppc64el miscellaneous system utilities

Result:
root@guest:~# lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 64
On-line CPU(s) list: 0-63
Thread(s) per core: 4
Core(s) per socket: 8
Socket(s): 2
NUMA node(s): 1
Model: 2.0 (pvr 004d 0200)
Model name: POWER8 (architected), altivec supported
> Hypervisor vendor: horizontal --> not ok
> Virtualization type: full --> not ok
L1d cache: 64K
L1i cache: 32K
NUMA node0 CPU(s): 0-63

I hope its clear now.

------- Comment From <email address hidden> 2018-12-19 23:27 EDT-------
I am on:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial

Dimitri John Ledkov (xnox) wrote :

This is very clear now, thank you!

Changed in util-linux (Ubuntu):
status: Incomplete → New
Changed in ubuntu-power-systems:
status: Incomplete → New
Manoj Iyer (manjo) on 2019-01-07
Changed in ubuntu-power-systems:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments