Sorry for responding so late, I've been using the workaround of setting
the device model of the virtual NIC to use "virtio" instead of "e1000e"
for the last several months for some critical production work and I
didn't want to rock the boat.
I'm currently running kernel: 5.3.0-26-generic and I'm
Hi,
5.3.0-24 fixed this issue for me.
BTW, system with i7-4790 was affected, while i7-3820 was NOT affected. was
tested by attaching the same disk to both computers.
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi
I've faced a similar problem on Debian.
My system is a Ryzen 1700 and I use windows and OSX VMs for work, and
after I upgraded to Debian 10 I started getting random host freezes some
time after booting the VMs. Strangely, I have a linux VM with almost
identical config as the Windows 10 one
Hi, the package from eoan-proposed linux version 5.3.0-24 should fix the
issue. Can anyone test it?
Thanks.
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
KVM
@Rafael - Regarding comment #39
The win10.xml dump was after I switched from "e1000e" to "virtio" NIC
To reiterate:
Freeze happens while using e1000e
NO freeze while using virtio
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
https://bugzilla.kernel.org/show_bug.cgi?id=205173
This other report seems to be the one that is fixed by the referred
upstream commit, as they have the same reporter name. I am very
confident this might be the fix here.
Cascardo.
** Bug watch added: Linux Kernel Bug Tracker #205173
I am suspicious upstream commit e7a409c3f46cb0dbc7bfd4f6f9421d53e92614a5
("ipv4: fix IPSKB_FRAG_PMTU handling with fragmentation") might fix
this. It has been queued in eoan tree as part of 5.3.10 update.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: qemu (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
KVM with e1000e and
https://bugzilla.kernel.org/show_bug.cgi?id=205247
This could be related. That means, it's a problem on the networking
code.
** Bug watch added: Linux Kernel Bug Tracker #205247
https://bugzilla.kernel.org/show_bug.cgi?id=205247
--
You received this bug notification because you are a member
On Tue, Nov 12, 2019 at 5:35 AM Zach Graceffa
<1849...@bugs.launchpad.net> wrote:
>
> @Christian - 5.4-rc7 worked for both e1000e and virtio NICs. No crash as
> of about 15 minutes.
Great, thanks Zach for the check!
@kernel-team, that means there likely is something in 5.3 -> 5.4 that
you could
@Christian - 5.4-rc7 worked for both e1000e and virtio NICs. No crash as
of about 15 minutes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
KVM with e1000e and WinGuest
I switched my networking interface from e1000e to virtio and ran the VM
on kernel 5.3.0-19-generic and had no issues with the VM. Networking
worked for both the host and the VM. When I compared this to a clone of
the machine with the e1000e networking interface, I had the system
freezing issue.
I did a retry on my own as well (kernel 5.3, virtual e1000e card, win
server guest), but it just won't fail for me. That confirmed Rafaels
much more various tests :-/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Rafael - IIRC you said all combinations you tried didn't trigger anything for
you - is that correct?
If so please state it here and mark the bug on the qemu task invalid and
unassign yourself as it seems much more a kernel issue right now.
Or did you have combinations left to try?
--
You
@Kernel Team - this has enough affected people that I'd rate this at least high
severity.
Unfortunately none of "us" could reproduce it on our side yet to bisect on our
own.
As you see above affected users were so kind to test mainline kernels and
identified 5.2.21-050221 - 5.3.0-050300
I bisected them tonight and found the issue between
5.2.21-050221-generic and 5.3.0-050300-generic. As far as I can tell
there are no versions between, so it seems it starts at 5.3.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I can confirm this issue with Eoan Ermine (5.3.0-19-generic). I tried
disabling AppArmor (security_driver=none), but my laptop still locks up
at the Windows login screen (Windows 10).
Using the virtio NIC does work around the problem though.
(root) ~ uname -a
Linux pi.aqdx.us 5.3.0-19-generic
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: dror 1780 F pulseaudio
/dev/snd/controlC0: dror 1780 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
@Christian, I'll try some more kernels over the weekend and let you know
the results.
I can confirm that switching my NIC to "virtio" from "e1e" allows me
to run my vm on kernel 5.3.0-20-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is
This doesn't need kernel logs at this state of the bug, bot pleas stop
spamming :-)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
20 matches
Mail list logo
