[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#961676: marked as done (5.6 kernel crashes host when using VFIO on KVM guests)



Your message dated Sun, 19 Jul 2020 18:02:00 +0200
with message-id <20200719160200.GB234193@photino.stro.at>
and subject line Re: Bug#961676: 5.6 kernel crashes host when using VFIO on KVM guests
has caused the Debian Bug report #961676,
regarding 5.6 kernel crashes host when using VFIO on KVM guests
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
961676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961676
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.6.7-1
Control: submitter -1 debian@the-jedi.co.uk

Forwarding this report as bug in the BTS.

On Mon, May 25, 2020 at 09:03:43PM +0100, Simon John wrote:
> Sorry to email directly but I've tried reportbug but it doesn't seem to work
> with the kernel packages.

What exactly did not work?

> The 5.6.0-1 kernel in Sid when used in conjunction with VFIO (PCI
> passthrough) guests in Qemu-KVM causes KVM to crash with no useful logs -
> the guest partially starts. Eventually the host slows down and needs to be
> powered off. Doesn't affect non-VFIO guests using spice/headless, only when
> passing through a PCIe graphics card or USB keyboard/mouse.
> 
> 5.6.0-2 that just landed makes this infinitely worse - as soon as you start
> a VFIO guest the host hard crashes.
> 
> 5.3/5.4/5.5 kernels do not have this problem with the same version of Qemu
> and reverting from qemu 5.0 to 4.2 doesn't help, so it must be the 5.6
> kernel causing the issue.
> 
> Not sure what logs or any useful information I can supply you, there's some
> interesting comments on this reddit thread suggesting a couple of bugs that
> have fixes upstream:
> 
> https://www.reddit.com/r/VFIO/comments/glfgqs/qemu_5_vfio_no_longer_works_on_debian/
> 
> I'm using macos catalina and win10 guests to reproduce the issue, and using
> Intel not AMD chips.
> 
> Cheers.
> 
> -- 
> Simon John

Regards,
Salvatore

--- End Message ---
--- Begin Message ---
Version: 5.7.6-1
done

On Sun, Jul 19, 2020 at 04:49:24PM +0100, Simon John wrote:
> I think we can close this as #notabug.
> 
> I did a fresh install and its working on 5.7
> 
> It worked 100% fine on qemu, but when I imported it into virt-manager it
> crashed, until i removed all of the clock bits, so i think maybe there's a
> bug in the clock/pit parts of libvirt that qemu doesn't seem to use.

ok thanks for the feedback.

closing.

--- End Message ---

Reply to: