hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi

Bug #1755384 reported by vmware-gos-Yuhua
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux
Confirmed
Undecided
Unassigned
linux (Ubuntu)
Fix Released
High
Joseph Salisbury

Bug Description

hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi.

Reproduce:
---------------------
1. create VM with default setting in ESXi 6.5 / on-developing ESXi build 7940658

2. install geustOS zyh-ubuntu16.04.4-dsktop-64 image.

3. reboot it after finish installation

4. edit VM setting and enable hot-add CPU and memory

5. open a terminal and type command "ls /sys/devices/system/memory",
   find memory0 -- memory7 listed.

6. edit VM setting and set default 1024M memory to 2048M

7. type command "ls /sys/devices/system/memory", it still lists memory0-memory7.
   No more memoryX is added.

   The hot-add memory can't be recognized.

Expect:
For step 7, it should list memory8--memory15 when type "ls /sys/devices/system/memory".

Tags: cscc
vmware-gos-Yuhua (yhzou)
affects: tripleo → kernel
vmware-gos-Yuhua (yhzou)
Changed in kernel:
status: New → Confirmed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1755384

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This bug was initially opened for Artful, but it is now EOL as is the 4.13 kernel. Can you confirm this bug still exists in Bionic(18.04)?

Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → High
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

This issue doesn't exist when check ubuntu18.04.1-desktop64.
Ubuntu-18.04.1-desktop has kernel 4.15.0-32-generic.

Changed in linux (Ubuntu):
status: Triaged → Fix Released
Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.