[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
This bug is awaiting verification that the linux- azure-5.15/5.15.0-1033.40~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-azure-5.15 verification-needed-focal -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-azure source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
This bug was fixed in the package linux-azure - 5.19.0-1016.17 --- linux-azure (5.19.0-1016.17) kinetic; urgency=medium * kinetic/linux-azure: 5.19.0-1016.17 -proposed tracker (LP: #1999735) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts [ Ubuntu: 5.19.0-28.29 ] * kinetic/linux: 5.19.0-28.29 -proposed tracker (LP: #1999746) * mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 (LP: #1999094) - fix coredump breakage linux-azure (5.19.0-1015.16) kinetic; urgency=medium * kinetic/linux-azure: 5.19.0-1015.16 -proposed tracker (LP: #1999417) * Azure: Jammy fio test hangs, swiotlb buffers exhausted (LP: #1998838) - SAUCE: scsi: storvsc: Fix swiotlb bounce buffer leak in confidential VM * Azure: MANA New Feature MANA XDP_Redirect Action (LP: #1998351) - net: mana: Add support of XDP_REDIRECT action linux-azure (5.19.0-1014.15) kinetic; urgency=medium * kinetic/linux-azure: 5.19.0-1014.15 -proposed tracker (LP: #1997782) * Jammy/linux-azure: CONFIG_BLK_DEV_FD=n (LP: #1972017) - [Config] azure: CONFIG_BLK_DEV_FD=n * remove circular dep between linux-image and modules (LP: #1989334) - [Packaging] remove circular dep between modules and image * [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks (LP: #1995408) - PCI: hv: Only reuse existing IRTE allocation for Multi-MSI * [Azure][Arm64] Unable to detect all VF nics / Failing provisioning (LP: #1996117) - PCI: hv: Fix the definition of vector in hv_compose_msi_msg() * Kinetic update: v5.19.9 upstream stable release (LP: #1994068) // Kinetic update: v5.19.15 upstream stable release (LP: #1994078) // Kinetic update: v5.19.17 upstream stable release (LP: #1994179) - [Configs] azure: Updates after rebase * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.19.0-27.28 ] * kinetic/linux: 5.19.0-27.28 -proposed tracker (LP: #1997794) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.11.14) * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - [Config] Disable selftests/net/bpf/nat6to4 * Expose built-in trusted and revoked certificates (LP: #1996892) - [Packaging] Expose built-in trusted and revoked certificates * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * Add cs35l41 firmware loading support (LP: #1995957) - ASoC: cs35l41: Move cs35l41 exit hibernate function into shared code - ASoC: cs35l41: Add common cs35l41 enter hibernate function - ASoC: cs35l41: Do not print error when waking from hibernation - ALSA: hda: cs35l41: Don't dereference fwnode handle - ALSA: hda: cs35l41: Allow compilation test on non-ACPI configurations - ALSA: hda: cs35l41: Drop wrong use of ACPI_PTR() - ALSA: hda: cs35l41: Consolidate selections under SND_HDA_SCODEC_CS35L41 - ALSA: hda: hda_cs_dsp_ctl: Add Library to support CS_DSP ALSA controls - ALSA: hda: hda_cs_dsp_ctl: Add apis to write the controls directly - ALSA: hda: cs35l41: Save codec object inside component struct - ALSA: hda: cs35l41: Add initial DSP support and firmware loading - ALSA: hda: cs35l41: Save Subsystem ID inside CS35L41 Driver - ALSA: hda: cs35l41: Support reading subsystem id from ACPI - ALSA: hda: cs35l41: Support multiple load paths for firmware - ALSA: hda: cs35l41: Support Speaker ID for laptops - ALSA: hda: cs35l41: Support Hibernation during Suspend - ALSA: hda: cs35l41: Read Speaker Calibration data from UEFI variables - ALSA: hda: hda_cs_dsp_ctl: Add fw id strings - ALSA: hda: cs35l41: Add defaulted values into dsp bypass config sequence - ALSA: hda: cs35l41: Support Firmware switching and reloading - ALSA: hda: cs35l41: Add module parameter to control firmware load - Revert "ALSA: hda: cs35l41: Allow compilation test on non-ACPI configurations" - ALSA: hda/realtek: More robust component matching for CS35L41 - [Config] updateconfigs for SND_HDA_CS_DSP_CONTROLS * Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700) - net: wwan: t7xx: Add AP CLDMA * Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] (LP: #1995573) - drm/mgag200: Optimize damage clips - drm/mgag200: Add FB_DAMAGE_CLIPS support - drm/mgag200: Enable atomic gamma lut update * TEE Support for CCP driver (LP: #1991608) - crypto: ccp: Add support for TEE for PCI ID 0x14CA * AMD Cezanne takes 5 minutes to wake up from suspend (LP: #1993715) - platform/x86/amd: pmc: Read SMU version during suspend on Cezanne systems * Fix ath11k deadlock on WCN6855 (LP: #1995041) - wifi: ath11k: avoid deadlock during regulatory update in
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
This bug was fixed in the package linux-azure - 5.15.0-1030.37 --- linux-azure (5.15.0-1030.37) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1030.37 -proposed tracker (LP: #1999425) * Azure: Jammy fio test causes panic (LP: #1996806) - scsi: storvsc: Fix unsigned comparison to zero * Azure: Jammy fio test hangs, swiotlb buffers exhausted (LP: #1998838) - SAUCE: scsi: storvsc: Fix swiotlb bounce buffer leak in confidential VM * Azure: hv_netvsc: Fix race between VF offering and VF association message from host (LP: #1994974) - hv_netvsc: Fix race between VF offering and VF association message from host * [Azure][Arm64] Unable to detect all VF nics / Failing provisioning (LP: #1996117) - PCI: hv: Fix the definition of vector in hv_compose_msi_msg() * Azure: MANA New Feature MANA XDP_Redirect Action (LP: #1998351) - net: mana: Add support of XDP_REDIRECT action [ Ubuntu: 5.15.0-57.63 ] * jammy/linux: 5.15.0-57.63 -proposed tracker (LP: #1997737) * Packaging resync (LP: #1786013) - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/2022.11.14) * Expose built-in trusted and revoked certificates (LP: #1996892) - [Packaging] Expose built-in trusted and revoked certificates * TEE Support for CCP driver (LP: #1991608) - crypto: ccp: Add support for TEE for PCI ID 0x14CA * alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec (LP: #1996121) - ASoC: cs35l41: Add one more variable in the debug log - ASoC: cs35l41: Fix an out-of-bounds access in otp_packed_element_t * Fix ath11k deadlock on WCN6855 (LP: #1995041) - wifi: ath11k: avoid deadlock during regulatory update in ath11k_regd_update() * [UBUNTU 20.04] boot: Add s390x secure boot trailer (LP: #1996071) - s390/boot: add secure boot trailer * Fix rfkill causing soft blocked wifi (LP: #1996198) - platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Distribute available resources for root buses, too - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * md: Replace snprintf with scnprintf (LP: #1993315) - md: Replace snprintf with scnprintf * input/keyboard: the keyboard on some Asus laptops can't work (LP: #1992266) - ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA - ACPI: resource: Add ASUS model S5402ZA to quirks * Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU (LP: #1991365) - tools/power turbostat: Add support for RPL-S * pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) (LP: #1988797) - PCI/PTM: Cache PTM Capability offset - PCI/PTM: Add pci_upstream_ptm() helper - PCI/PTM: Separate configuration and enable - PCI/PTM: Add pci_suspend_ptm() and pci_resume_ptm() - PCI/PTM: Move pci_ptm_info() body into its only caller - PCI/PTM: Preserve RsvdP bits in PTM Control register - PCI/PTM: Reorder functions in logical order - PCI/PTM: Consolidate PTM interface declarations - PCI/PM: Always disable PTM for all devices during suspend - PCI/PM: Simplify pci_pm_suspend_noirq() * Fix RPL-S support on powercap/intel_rapl (LP: #1990161) - x86/cpu: Drop spurious underscore from RAPTOR_LAKE #define - x86/cpu: Add new Alderlake and Raptorlake CPU model numbers - x86/cpu: Add new Raptor Lake CPU model number - powercap: intel_rapl: add support for RaptorLake - powercap: intel_rapl: Add support for RAPTORLAKE_P - powercap: intel_rapl: Add support for RAPTORLAKE_S * AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking (LP: #1991974) - drm/amd/display: Fix for link encoder access for MST. - drm/amd/display: Fix MST link encoder availability check. - drm/amd/display: FEC configuration for dpia links - drm/amd/display: FEC configuration for dpia links in MST mode - drm/amd/display: Add work around for tunneled MST. * Jammy update: v5.15.74 upstream stable release (LP: #1995638) - nilfs2: fix use-after-free bug of struct nilfs_root - nilfs2: fix leak of nilfs_root in case of writer thread creation failure - nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure - ceph: don't truncate file in atomic_open - random: restore O_NONBLOCK support - random: clamp credited irq bits to maximum mixed - ALSA: hda: Fix position reporting on Poulsbo - efi: Correct Macmini DMI match in uefi cert quirk - USB: serial: qcserial: add new usb-id for Dell branded EM7455 -
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
I've tested linux-azure/5.15.0-1030.37 in jammy-proposed and confirmed it has fixed the issue gerald@myvm-j1:~$ uname -a Linux myvm-j1 5.15.0-1030-azure #37-Ubuntu SMP Mon Dec 12 19:17:45 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux all VFs can be detected and VM boot successfully ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
This bug is awaiting verification that the linux-azure/5.15.0-1030.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
Hi Tim, I've tested kinetic azure kernel and it works perfectly but when I check jammy azure kernel, this patch seems not in the git tree has it been merged to the jammy azure kernel too? Thanks, Gerald -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
I've tested linux-azure/5.19.0-1014.15 in kinetic-proposed and confirmed it fixes the issue uname -a Linux myvm-k 5.19.0-1014-azure #15-Ubuntu SMP Mon Nov 28 19:54:09 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux steps: create an ARM64 VM on azure create 8 VFs and attach to the VM with 5.19.0-1014-azure, VM can boot successfully without any issue ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
This bug is awaiting verification that the linux-azure/5.19.0-1014.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure verification-needed-kinetic -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Committed -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
** Also affects: linux-azure (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu) Assignee: Tim Gardner (timg-tpi) => (unassigned) -- 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/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Kinetic: In Progress Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
