Just an update else then the bug. I found the reason the for the issue. I installed Docker from the main Docker repo as opposed to docker.io package from Ubuntu. It resulted in a scenario which something goes wrong and the kernel start's doing something weird. I do not know the exact in-depth details of the issue but I believe that this is the root cause since the same issue appeared on a fresh CentOS kvm hypervisor after adding the official Docker package.
All The Bests, Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: [email protected] -----Original Message----- From: Robie Basak [mailto:[email protected]] Sent: Monday, March 13, 2017 12:03 PM To: Eliezer Croitoru <[email protected]> Cc: [email protected] Subject: Re: where do I file a bug with xenial 4.4.0-66-generic issue on a kvm hypervisor ? Hi Eliezer, On Mon, Mar 13, 2017 at 11:52:14AM +0200, Eliezer Croitoru wrote: > And worked fine for quite some time. > The latest Xenial kernel from the upgrade (4.4.0-66-generic) causes a very > specific issue. > VM's with virtio nic cannot contact the network.(e1000 works fine) > I have not delved to see if tcpdump sees the packets or something similar in > the hypervisor level and bumped the kernel to 4.6 which I have tested long > ago to work fine. > > Where do I file the bug report? > I am pretty sure it's a very series bug but not sure who should be aware of > it and how to debug if it's a machine local one or a wider issue. Thank you for this report. You should be able to verify that the bug is in the kernel by switching only the version of the kernel to see if you can introduce and fix the bug as you switch kernels. If this turns out to be correct, please file a bug against the "linux" package (you can use https://bugs.launchpad.net/ubuntu/+source/linux/+filebug) and tag it "regression-update". Thanks! -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
