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 t
Ah no, turns out I had disabled the gpu passthrough, when i re-enabled
it i just got a kernel panic from 5.8.0-rc5
On 19/07/2020 00:34, Simon John wrote:
I tried mainline 5.8.0-rc5 and I couldn't even get into gnome shell
after the gdm3 password prompt, just a black screen!
I tried running vi
I tried mainline 5.8.0-rc5 and I couldn't even get into gnome shell
after the gdm3 password prompt, just a black screen!
I tried running virsh start which worked but my monitor never got a
signal. It also didn't crash the host or qemu though, although virsh
destroy finished instantly, so i ass
Where would I look for some follow-up on this - upstream kernel.org?
--
Simon John
Done some more digging.
I can boot my macos vm using QXL instead of a passthrough GPU, even if i
passthrough the USB device (not pci controller). So its definitely only
passing through PCI devices like graphics cards that breaks things.
So this works in qemu terms:
-usb -device usb-host,
On Sun, 28 Jun 2020 10:41:41 +0200 Salvatore Bonaccorso
wrote:
Hi Simon,
Hi Salvatore, thanks for looking into this.
On Sun, Jun 28, 2020 at 01:01:01AM +0100, Simon John wrote:
> This looks a likely culprit:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=207489
The issue you are seeing n
Hi Simon,
On Sun, Jun 28, 2020 at 01:01:01AM +0100, Simon John wrote:
> This looks a likely culprit:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=207489
The issue you are seeing now seems different, though afaics.
The fixing commit from the above reference, 8be8f932e3db ("kvm:
ioapic: Restri
This looks a likely culprit:
https://bugzilla.kernel.org/show_bug.cgi?id=207489
--
Simon John
Bug still exists in today's 5.7 kernel, however it took long enough to
trigger that it managed to write some logs:
https://gist.github.com/sej7278/766043a69c76308f84cfa14b3f3a924f
"BUG: soft lockup - CPU#0 stuck for 22s!" seems to go back to 2013 or
earlier e.g. https://bugzilla.redhat.com/sho
I tried to get some sort of useful logging today, best I could do was
running strace.
So I noticed that virsh exited 0 but didn't instantly crash, it took 2-3
seconds more.
Photo of screen with strace output here:
https://i.imgur.com/kOSEXXA.jpg
Managed to install 5.5.0-2 from snaps
The new linux-image-5.6.0-2-amd64 (5.6.14-2) from today is no better,
only change is its signed I guess?
Also I noticed the 5.3/5.4/5.5 kernels have all been removed from my
system and the servers so I have no way to boot back into a kernel that
doesn't break VFIO.
Has this issue been looked
On Wed, 27 May 2020 21:31:46 +0200 Salvatore Bonaccorso
wrote:
Source: linux
Version: 5.6.7-1
Control: submitter -1 deb...@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
Source: linux
Version: 5.6.7-1
Control: submitter -1 deb...@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
13 matches
Mail list logo
