[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633634
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633634
Title:
sr-iov not working on ubuntu 16.04 kvm
To manage notifications
I replayed the bisect results and it looks like the following commit
also needs to be tested:
[92923ca3aacef63c92dc297a75ad0c6dfe4eab37] mm: meminit: only set page
reserved in the memblock region
Were you able to also test this commit?
--
You received this bug notification because you are a
Hi Joseph,
This is my kernel bisect result
$ git checkout bisect/bad
Previous HEAD position was 92923ca... mm: meminit: only set page reserved in
the memblock region
HEAD is now at d70ddd7... mm: page_alloc: pass PFN to __free_pages_bootmem
$ git bisect log
git bisect start
# bad:
I started a kernel bisect between v4.1 final and v4.2-rc1. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
4570a37169d4b44d316f40b2ccc681dc93fedc7b
The test kernel can be downloaded from:
Thanks for the testing results, Hua! I'll start a bisect between 4.1
and 4.2-rc1. That will tell us the commit that introduced this
regression. I'll post a test kernel shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I also hit the same problem [1], so I perform a kernel bisect among the
following versions:
4.4.0-45 - doesn't work
4.3 - doesn't work
4.2 - failed to start my compute, this is a bad release
4.0 - work
3.14 - failed with the error 'vfio: error, group 9 is not viable,
That's fine but I go on holiday tomorrow for a couple of weeks so it
will have to wait till I get back. Will let you know as soon as I have
the results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for the delay, and thanks for testing. It looks like we have to
test older kernels to find the last good one and first bad one. Can you
test the following:
3.14: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/
4.0: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/
4.2:
Kernel 4.5-wily => same result as 4.4.0-42 and 4.4.25 for both vfio and
kvm
Kernel 4.6-yakkety => same result as 4.7 for vfio (as I said earlier vm
starts but with no networking and logs of errors in logs) and same as
4.5-wily for kvm
Kernel 4.7 => same as 4.6-yakkety for both vfio and kvm
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first
Kernel 4.8.4 is exactly the same as 4.9-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633634
Title:
sr-iov not working on ubuntu 16.04 kvm
To manage notifications about this bug go to:
Can you give the latest upstream 4.8 kernel a try as well? It is available
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.4/
We may have to perform a kernel bisect between the 3.13 and 4.4 kernels
if the bug is not fixed in 4.8.4.
--
You received this bug notification because you
Update:
I left the server on kernel 4.9-rc1 and everything was fine for an hour
until I tried to create a snapshot of one of the VM's and it froze. I
lost my SSH connection and a ping of the IP address failed, there was
also no video output from the host though all the VM's continued to run
and
With kernel 4.9-rc1 the default vfio option still fails with the same
errors but with the virtual machine starts
absolutely fine even though the vm log still shows
/var/log/libvirt/qemu/devsrv.log
2016-10-20T21:03:04.432081Z qemu-system-x86_64: -device pci-
If the bug still exists in 4.9-rc1, we can perform a kernel bisect to
identify the commit that introduced the regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633634
Title:
sr-iov not
It would also be good to test the latest mainline kernel to see if this
bug is already fixed there. It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633634
Title:
sr-iov not working on
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
19 matches
Mail list logo
