Please, can you confirm which is the ESX release or build with the fix
implemented?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654319
Title:
kernel BUG at /build/linux-
_qw1uB/linux-4
This is an issue in the vmxnet3 device emulation (ESX 6.5) and will be
fixed in the next update.
In the meantime, suggested workaround:
- disable rx data ring: ethtool -G eth? rx-mini 0
The issue should not be hit if using HW version 12 or older (with any
kernel) or with kernel older than 4.8 (a
My VMs are running hwversion 13 on 6.5 (for several days now), but
haven't hit this issue yet.
Thanks for the vmss, cryptz.
To analyze this, also need access to ex.vmem, could you please provide
that? It should have been created in the same directory as vmss when you
suspended the VM.
Do you how
vmss file is posted here: http://98.115.67.171/ex.zip
had to zip, webserver wouldnt serve the file otherwise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654319
Title:
kernel BUG at /build/linux
also i saw your other thread where there is mention of the # of cpus
being a factor. In my case i have 1 socket with 2 cpus assigned to each
vm. I have 2 identical vms running haproxy. for whatever reason the
primary typically locks up 2-3 times a day, the secondary is only once
or twice a week.
-
Just to confirm your test, are you running a hw version 13 vm with
kernel ~4.8? I am also using the driver provided in vmware tools 10.1.5
it is my understanding that hw version 11 is fine.
of note the system can run for a day but generally speaking it only runs
for an hour or 2 before the lockup
I could not repro this issue locally despite running traffic for several
hours.
If you hit the issue again, could you please generate vmss file when the
VM is in the panic state? It can be obtained by suspending the VM in the
panic state and then locating the vmss file in the director of the
virtu
Im seeing this as well, from other posts ive seen the following is true:
1. Doesnt exist in kernel 4.4
2. Only affects esxi 6.5 with HW version 13. HW version 11 is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Bug watch added: Linux Kernel Bug Tracker #191201
http://bugzilla.kernel.org/show_bug.cgi?id=191201
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=191201
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member o
Is this still incomplete? I also think that importance should be higher
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654319
Title:
kernel BUG at /build/linux-
_qw1uB/linux-4.8.0/drivers/net/vmxn
This is a fresh installation.
I've tested
Linux version 4.10.0-041000rc4-generic (kernel@gloin) (gcc version 6.2.0
20161005 (Ubuntu 6.2.0-5ubuntu12) ) #201701152031 SMP Mon Jan 16 01:33:39 UTC
2017
First of all, I had problem booting this kernel on VMWare. The screen
goes black after few secon
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10 kernel[
12 matches
Mail list logo
