kata-containers: enable memory hotplug
Bug #1777127 reported by
Julio Montes
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-kvm (Ubuntu) |
Fix Released
|
Undecided
|
Julio Montes | ||
Bionic |
Fix Released
|
Undecided
|
Kamal Mostafa |
Bug Description
Kata containers need memory hotplug support in the guest kernel, since container's resources can be updated dynamically
Changed in linux-kvm (Ubuntu): | |
assignee: | nobody → Julio Montes (devimc) |
Changed in linux-kvm (Ubuntu Bionic): | |
status: | New → Fix Committed |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
To post a comment you must log in.
This bug was fixed in the package linux-kvm - 4.15.0-1016.16
---------------
linux-kvm (4.15.0-1016.16) bionic; urgency=medium
* linux-kvm: 4.15.0-1016.16 -proposed tracker (LP: #1782180)
[ Ubuntu: 4.15.0-29.31 ]
* linux: 4.15.0-29.31 -proposed tracker (LP: #1782173) spa_remove_ pe to clarify it's action enable_ p9_wait( ) GET_METADATA IOCTL block_bitmap: 383: inode_bitmap: comm
* [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler
(LP: #1777716)
- ipmi_ssif: Fix kernel panic at msg_done_handler
* Update to ocxl driver for 18.04.1 (LP: #1775786)
- misc: ocxl: use put_device() instead of device_unregister()
- powerpc: Add TIDR CPU feature for POWER9
- powerpc: Use TIDR CPU feature to control TIDR allocation
- powerpc: use task_pid_nr() for TID allocation
- ocxl: Rename pnv_ocxl_
- ocxl: Expose the thread_id needed for wait on POWER9
- ocxl: Add an IOCTL so userspace knows what OCXL features are available
- ocxl: Document new OCXL IOCTLs
- ocxl: Fix missing unlock on error in afu_ioctl_
* Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after
suspend (LP: #1776887)
- ocxl: Document the OCXL_IOCTL_
* Hard LOCKUP observed on stressing Ubuntu 18 04 (LP: #1777194)
- powerpc: use NMI IPI for smp_send_stop
- powerpc: Fix smp_send_stop NMI IPI handling
* IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on
CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n (LP: #1773964)
- rtc: opal: Fix OPAL RTC driver OPAL_BUSY loops
* [Regression] EXT4-fs error (device sda2): ext4_validate_
comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709)
- SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_
stress-ng: Corrupt inode bitmap"
- SAUCE: ext4: check for allocation block validity with block group locked
[ Ubuntu: 4.15.0-28.30 ]
* linux: 4.15.0-28.30 -proposed tracker (LP: #1781433)
* Cannot set MTU higher than 1500 in Xen instance (LP: #1781413)
- xen-netfront: Fix mismatched rtnl_unlock
- xen-netfront: Update features after registering netdev
linux-kvm (4.15.0-1015.15) bionic; urgency=medium
* linux-kvm: 4.15.0-1015.15 -proposed tracker (LP: #1781068)
[ Ubuntu: 4.15.0-27.29 ]
* linux: 4.15.0-27.29 -proposed tracker (LP: #1781062) inode_bitmap: 99: inode_bitmap: comm stress-ng: Corrupt inode
* [Regression] EXT4-fs error (device sda1): ext4_validate_
comm stress-ng: Corrupt inode bitmap (LP: #1780137)
- SAUCE: ext4: fix ext4_validate_
bitmap
linux-kvm (4.15.0-1014.14) bionic; urgency=medium
* linux-kvm: 4.15.0-1014.14 -proposed tracker (LP: #1780119)
[ Ubuntu: 4.15.0-26.28 ]
* linux: 4.15.0-26.28 -proposed tracker (LP: #1780112) 4.15.0- 24-generic (LP: #1779827) // Cloud-
* failure to boot with linux-image-
init causes potentially huge boot delays with 4.15 kernels (LP: #1780062)
- random: Make getrandom() ready earlier
linux-kvm (4.15.0-1013.13) bionic; urgency=medium
* linux-kvm: 4.15.0-1013.13 -proposed tracker (LP: #1779363)
* test_190_ config_ kernel_ fortify in kernel security test failed with 4.15 KVM
kernel (LP: #1766774)
...