Hi,
On Sat, Apr 19, 2025 at 10:28:11AM -0400, Joshua Lee wrote:
> Package: src:linux
> Version: 6.1.133-1
> Followup-For: Bug #1102914
>
> Dear Maintainer,
>
>
> * What led up to the situation?
>
> I use a VM to handle my NAS and use PCIe passthrough to pass a
Package: src:linux
Version: 6.1.133-1
Followup-For: Bug #1102914
Dear Maintainer,
* What led up to the situation?
I use a VM to handle my NAS and use PCIe passthrough to pass a HBA
controller through to the VM, woke up today after an automagic
upgrade to lots of wonderful
Hi,
For those following these bugs: A patch is now submitted upstream at
https://lore.kernel.org/stable/20250416202441.3911142-1-alex.william...@redhat.com/
and we are waiting that it get accepted for beeing queued for 6.1.y.
Thanks again to Milan for doing the bisection work and testing.
Regard
Hi,
I tried upstream stable git and bisect, this is the conclusion:
- upstream 6.1.134 is still broken
- bisect points to this patch
(Patch cannot be easily reverted, it need some other patches, anyway, it can be
used as reference what need to be backported)
476c1dfefab8b98ae9c3e3ad283c2ac10d
Hi Milan,
On Tue, Apr 15, 2025 at 05:01:15PM +0200, Milan Broz wrote:
> Hi,
>
> I tried upstream stable git and bisect, this is the conclusion:
>
> - upstream 6.1.134 is still broken
>
> - bisect points to this patch
> (Patch cannot be easily reverted, it need some other patches, anyway, it can
On 4/14/25 8:58 PM, Salvatore Bonaccorso wrote:
As asked in #1102889 as well, would it be possible to get a full
kernel log as well please?
I cannot share log from this machine, but I just went through this and in the
moment
libvirt failed there is nothing logged...
I can see it only tried to
Hi,
On Mon, Apr 14, 2025 at 02:01:07PM +0200, Milan Broz wrote:
> Hi,
>
> we have the same issue with 6.1.133-1 (previous 6.1.129-1 works fine).
>
> We use passthrough of NVMe device, VM start now fails with
>
> qemu-system-x86_64: -device
> {"driver":"vfio-pci","host":":03:00.0","id":"hos
Hi,
we have the same issue with 6.1.133-1 (previous 6.1.129-1 works fine).
We use passthrough of NVMe device, VM start now fails with
qemu-system-x86_64: -device
{"driver":"vfio-pci","host":":03:00.0","id":"hostdev0","bus":"pci.3","addr":"0x0"}:
VFIO_MAP_DMA failed: Cannot allocate memory
Got same issue on my VM system.
Just wanted to make it known it isn't just single system specific.
For me too just reverting to previous kernel works.
/proc/iomem doesn't show anything reserving the VF.
Also tried with the host ixgbevf driver loaded, which I have normally
blacklisted with no chan
Control: reassign -1 src:linux
Control: forcemerge 1102914 -1
On Sun, Apr 13, 2025 at 08:53:13AM +0200, Bernd Rinn wrote:
> Package: linux-image-amd64
> Version: 6.1.133-1
>
> Description:
> I noticed a regression with the most recent kernel 6.1.0-33 (6.1.133) of
> Debian Bookworm:
> libvirtd VM
Package: linux-image-amd64
Version: 6.1.133-1
Description:
I noticed a regression with the most recent kernel 6.1.0-33 (6.1.133) of Debian
Bookworm:
libvirtd VMs don't start up anymore when they are being passed through a PCI device (in my case the
PCI device is a network card). The error messa
11 matches
Mail list logo
