This bug was fixed in the package linux-azure - 4.18.0-1011.11
---------------
linux-azure (4.18.0-1011.11) cosmic; urgency=medium
* linux-azure: 4.18.0-1011.11 -proposed tracker (LP: #1816081)
* 4.15.0-1037 does not see all PCI devices on GPU VMs (LP: #1816106)
- Revert "PCI: hv: Make sure the bus domain is really unique"
linux-azure (4.18.0-1009.9) cosmic; urgency=medium
* Allow I/O schedulers to be loaded with modprobe in linux-azure
(LP: #1813211)
- [Config] linux-azure: Enable all IO schedulers as modules
* [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() (LP: #1802021)
- srcu: Lock srcu_data structure in srcu_gp_start()
* CONFIG_SECURITY_SELINUX_DISABLE should be disabled on 4.15/4.18 Azure
(LP: #1813866)
- [Config]: disable CONFIG_SECURITY_SELINUX_DISABLE
[ Ubuntu: 4.18.0-15.16 ]
* Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555)
- Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5"
* Userspace break as a result of missing patch backport (LP: #1813873)
- tty: Don't hold ldisc lock in tty_reopen() if ldisc present
-- Stefan Bader <[email protected]> Fri, 15 Feb 2019 17:16:24
+0100
** Changed in: linux-azure (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1816106
Title:
4.15.0-1037 does not see all PCI devices on GPU VMs
Status in linux-azure package in Ubuntu:
Fix Released
Bug description:
Host changes have altered how the PCI GUID is presented to the guest
and the patches for PCI IDs in 4.15.0-1037 do not properly handle the
new condition.
Impact:
Instances with multiple GPUs are only seeing one.
Workaround:
4.15.0-1036 does not have this behavior.
Additional info:
The commit in 4.15.0-1037 responsible is " - PCI: hv: Make sure the
bus domain is really unique"
The immediate action requested is to back out this patch on 4.15.0 (azure):
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=master-next&id=b9ae54076a78d01659c4d0f0a558cdb4056f0d13
The same thing on 4.18:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=azure-edge-next&id=29927dfb7f69bcf2ae7fd1cda10997e646a5189c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1816106/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
