Public bug reported:

[email protected] contacted me about a possible regression (if it
is indeed a regression it probably came from the upstream and might be
related to https://bugs.launchpad.net/ubuntu/+source/linux-
lowlatency/+bug/2117334).

Fabian's mail:

--------------------------------------------------------------------------------------------------------

The recent Kernel 6.8.0-64.67 update [1] for Noble 24.04 seems to have changed 
something under the hood, preventing a vanilla LXD setup from launching 
QEMU-based VMs with SR-IOV network interfaces [2].
A temporary rollback via GRUB to 6.8.0-63.66 fixes the problem instantly.
I went through the diff [3], but haven’t found anything concrete (yet).

Fortunately (or unfortunately in this case), I‘m not alone with this
issue, as even downstream projects like Proxmox are now affected [4 &
5].

What do you think? Any hints?

[1] https://launchpad.net/ubuntu/+source/linux/6.8.0-64.67

[2] Error: Failed setting up device via monitor: Failed setting up
device "eth0": Failed adding NIC device: vfio 0000:2b:0a.1: error
getting device from group 59: Permission denied

[3]
https://launchpad.net/ubuntu/+archive/primary/+files/linux_6.8.0-63.66_6.8.0-64.67.diff.gz

[4] https://forum.proxmox.com/threads/kernel-6-8-12-12-pve-update-
results-in-vfio-pci-passthrough-issues.168519

[5] https://forum.proxmox.com/threads/regression-cannot-start-vms-with-
kernel-6-8-12-12-pve-and-6-14-8-1-bpo12-pve-and-pci-passthrough-sr-
iov-x710-vf.168514

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Package changed: linux-lowlatency (Ubuntu) => linux (Ubuntu)

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Description changed:

  [email protected] contacted me about a possible regression (if it
  is indeed a regression it probably came from the upstream and might be
  related to https://bugs.launchpad.net/ubuntu/+source/linux-
  lowlatency/+bug/2117334):
+ 
+ 
--------------------------------------------------------------------------------
+ 
  
  The recent Kernel 6.8.0-64.67 update [1] for Noble 24.04 seems to have 
changed something under the hood, preventing a vanilla LXD setup from launching 
QEMU-based VMs with SR-IOV network interfaces [2].
  A temporary rollback via GRUB to 6.8.0-63.66 fixes the problem instantly.
  I went through the diff [3], but haven’t found anything concrete (yet).
  
  Fortunately (or unfortunately in this case), I‘m not alone with this
  issue, as even downstream projects like Proxmox are now affected [4 &
  5].
  
  What do you think? Any hints?
- 
  
  [1] https://launchpad.net/ubuntu/+source/linux/6.8.0-64.67
  
  [2] Error: Failed setting up device via monitor: Failed setting up
  device "eth0": Failed adding NIC device: vfio 0000:2b:0a.1: error
  getting device from group 59: Permission denied
  
  [3]
  
https://launchpad.net/ubuntu/+archive/primary/+files/linux_6.8.0-63.66_6.8.0-64.67.diff.gz
  
  [4] https://forum.proxmox.com/threads/kernel-6-8-12-12-pve-update-
  results-in-vfio-pci-passthrough-issues.168519
  
  [5] https://forum.proxmox.com/threads/regression-cannot-start-vms-with-
  kernel-6-8-12-12-pve-and-6-14-8-1-bpo12-pve-and-pci-passthrough-sr-
  iov-x710-vf.168514

** Description changed:

  [email protected] contacted me about a possible regression (if it
  is indeed a regression it probably came from the upstream and might be
  related to https://bugs.launchpad.net/ubuntu/+source/linux-
- lowlatency/+bug/2117334):
+ lowlatency/+bug/2117334).
  
- 
--------------------------------------------------------------------------------
+ Fabian's mail:
  
+ 
--------------------------------------------------------------------------------------------------------
  
  The recent Kernel 6.8.0-64.67 update [1] for Noble 24.04 seems to have 
changed something under the hood, preventing a vanilla LXD setup from launching 
QEMU-based VMs with SR-IOV network interfaces [2].
  A temporary rollback via GRUB to 6.8.0-63.66 fixes the problem instantly.
  I went through the diff [3], but haven’t found anything concrete (yet).
  
  Fortunately (or unfortunately in this case), I‘m not alone with this
  issue, as even downstream projects like Proxmox are now affected [4 &
  5].
  
  What do you think? Any hints?
  
  [1] https://launchpad.net/ubuntu/+source/linux/6.8.0-64.67
  
  [2] Error: Failed setting up device via monitor: Failed setting up
  device "eth0": Failed adding NIC device: vfio 0000:2b:0a.1: error
  getting device from group 59: Permission denied
  
  [3]
  
https://launchpad.net/ubuntu/+archive/primary/+files/linux_6.8.0-63.66_6.8.0-64.67.diff.gz
  
  [4] https://forum.proxmox.com/threads/kernel-6-8-12-12-pve-update-
  results-in-vfio-pci-passthrough-issues.168519
  
  [5] https://forum.proxmox.com/threads/regression-cannot-start-vms-with-
  kernel-6-8-12-12-pve-and-6-14-8-1-bpo12-pve-and-pci-passthrough-sr-
  iov-x710-vf.168514

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2117335

Title:
  Noble 6.8.0-64.67 update prevents vanilla LXD setup from launching
  QEMU-based VMs with SR-IOV network interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2117335/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to