Yeah we can, kernel had the fixes a while now.
It was a bit complex in this case as we had fix A, fix B and all 4 combinations
thereof.
Thanks Jeff!
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix
Also verified that the SRU resolves the issue on the previously failing
hardware (POWER8NVL).
This was tested on Xenial w/ 4.4 kernel
Can we set the Ubuntu and Xenial tasks to Fix Released now?
--
You received this bug notification because you are a member of Kernel
Packages, which is
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.13
---
qemu (1:2.5+dfsg-5ubuntu10.13) xenial; urgency=medium
* debian/patches/ubuntu/vvfat-fix-volume-name-assertion.patch:
Fix the volume name assertion in vvfat rw mode (LP: #1684239)
qemu
On Mon, May 15, 2017 at 5:10 PM, Jeff Lane
wrote:
> Call it pebkac. It's possible I missed the package when I manually
> updated the qemu-* packages.
>
I call it "thank you for sticking on and working through it"!
So as I understand we can set v-done now.
** Tags
Call it pebkac. It's possible I missed the package when I manually
updated the qemu-* packages.
--
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/1656112
Title:
Power S822LC (8335-GTB)
OK, THAT worked. Sorry for the worry. I have no idea why qemu-system-
ppc was skipped over when I upgraded everything, but I did retry and
indeed it does now pass the virt test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
So I thought that was a bit weird, so look below:
First, I wanted to see what was installed:
ubuntu@fesenkov:~$ apt-cache policy qemu-system-ppc*
qemu-system-ppcemb:
Installed: (none)
Candidate: (none)
Version table:
qemu-system-ppc: ###this is what I had installed, and I'm not entirely
Hi Jeff,
this bug always was and seems to stay an interesting one - as on the ppc
part this is actually identical to what mike tested successfully before.
Yet I think the dpkg listing you posted holds the answer.
It seems only some of the qemu packages got updated.
The fix needed would be in
I've tested the updated qemu in proposed and it fails.
ubuntu@fesenkov:~$ sudo qemu-system-ppc64 -m 1024 -display none -nographic -net
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm
-machine pseries,usb=off -cpu host -drive
ubuntu@fesenkov:~$ dpkg -l |grep qemu | awk '{print $2"\t\t"$3}'
ipxe-qemu 1.0.0+git-20150424.a25a16d-1ubuntu1
qemu-block-extra:ppc64el 1:2.5+dfsg-5ubuntu10.13
qemu-slof 20151103+dfsg-1ubuntu1
qemu-system 1:2.5+dfsg-5ubuntu10.13
qemu-system-arm
Additionally, as noted above, qemu-block-extra modules fail to load:
Failed to initialize module: /usr/lib/powerpc64le-linux-gnu/qemu/block-iscsi.so
Note: only modules from the same build can be loaded.
Failed to initialize module: /usr/lib/powerpc64le-linux-gnu/qemu/block-curl.so
Note: only
Due to security cert work, we won't be able to get to this until next
week. I've got this on my list to test out on Monday.
--
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/1656112
Title:
Hello Mike, or anyone else affected,
Accepted qemu into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-
5ubuntu10.13 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Re-prepared, and merged with another SRU that was ready now.
Pushed to SRU unapproved queue.
P.S. Since I pretest a lot one can already look at [1]. Please do note
that the iscsi dep8 test is a notorious noisy transient issue that is
not related to the update, but will likely be seen in -proposed
FYI - Recent security update burned the version number that this was
supposed to be, re-preparing an adapted version now.
--
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/1656112
Title:
** Tags removed: kernel-da-key
--
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/1656112
Title:
Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
failed: Invalid
So I think this is ready for SRU now:
- Template complete
- Updated triaging states to match reality
- Xenial SRU queue free of older qemu
- Minimized the patches down to the SRU'ed case
- Tested on ppa to work
- bileto dep8 tests are all good
- ppa checked on regressions (once more with
** Changed in: qemu (Ubuntu Xenial)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
** Changed in: qemu (Ubuntu)
Status: In Progress => Fix Released
** Description changed:
[Impact]
- * Some newer Power8 derivates fail to work correctly e.g. Power S822LC
- (8335-GTB)
I have tested the qemu-system-ppc package from both PPA's and both work
without issue.
--
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/1656112
Title:
Power S822LC (8335-GTB) fails KVM
Hi,
thank you a lot Daniel to identify the potentially missing two patches.
I wonder thou if we really need all 7 then, or maybe just the two new ones.
While the extra 5 are valid fixes in general I'm not sure they are 100% needed
as Xenial seems to be fine without and at least according to Mike
** Changed in: qemu (Ubuntu)
Status: Fix Released => In Progress
--
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/1656112
Title:
Power S822LC (8335-GTB) fails KVM guest cert test
** Summary changed:
- Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed:
Invalid argument
+ Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed:
Invalid argument
--
You received this bug notification because you are a member of Kernel
22 matches
Mail list logo