This was a glibc vs qemu-emulation issue.
Glibc versions in >=Eoan failed with the Qemu versions <=Focal.
In coordination with IBM everyone agreed that emulation isn't a primary
use case and that backports would therefore not be SRUed as the risk to
break something for more common use cases outwei
** Tags removed: targetmilestone-inin1910
** Tags added: targetmilestone-inin2004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan VM fails to insta
** Changed in: ubuntu-power-systems
Assignee: bugproxy (bugproxy) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64
** Changed in: glibc (Ubuntu Focal)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan VM fails to install
To manage
Default installer for Focal will be subiquity, not d-i.
** Changed in: debian-installer (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoa
Waiting on focal's adoption of glibc 2.31.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan VM fails to install
To manage notifications about this
Yes, that was the background - we wanted to know if the new instructions were
in glibc 2.30 and/or glibc 2.31 or not.
First to adjust the status of that ticket accordingly,
second to push another ticket (if needed) that discusses the upgrade to glibc
2.31 in focal.
Qemu 4.2 recently arrived in f
>From comment #25, is the required glibc support in either glibc 2.30
and/or glibc 2.31?
** Changed in: glibc (Ubuntu Focal)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Marking bionic debian-installer as "invalid", as the qemu changes will
not be pulled back to bionic.
** Changed in: debian-installer (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Marking eoan glibc as "invalid" as the qemu changes will not be pulled
back to eoan.
** Changed in: glibc (Ubuntu Eoan)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Done in Focal, but I'm not planning to backport emulation related
changes where most of the people don't care and the regression risk we
trigger might still be huge.
** Changed in: qemu (Ubuntu Eoan)
Status: Triaged => Won't Fix
** Changed in: qemu (Ubuntu Bionic)
Status: Triaged =>
** Changed in: ubuntu-power-systems
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan VM fails to install
T
This bug was fixed in the package qemu - 1:4.2-1ubuntu1
---
qemu (1:4.2-1ubuntu1) focal; urgency=medium
* Merge with Debian testing, Among many other things this fixes LP Bugs:
LP: #1847806 - add mff* instructions to not break on ppc64 with newer glibc
LP: #1812822 - avoid c
** Changed in: debian-installer (Ubuntu Disco)
Status: New => Won't Fix
** Changed in: qemu (Ubuntu Disco)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847
** Changed in: glibc (Ubuntu Eoan)
Status: New => Confirmed
** Changed in: glibc (Ubuntu Focal)
Status: New => Confirmed
** Changed in: qemu (Ubuntu Disco)
Status: New => Triaged
** Changed in: qemu (Ubuntu Eoan)
Status: Confirmed => Triaged
** Changed in: qemu (Ubun
@ pac...@us.ibm.com please let me summarize - you're comment numbers
(that probably refer to bugzilla numbers) seem to be differently
numbered that the ones here in the LP ticket (since #20 here is a
attached crash file).
So based on this LP we have some partly unanswered questions in 10, 17
and 1
While not having the priority for an upload on their own. If easy to
backport we should even consider older versions of qemu.
** Also affects: debian-installer (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Disco)
Importance: Undecided
Status:
In order to check that this issue is limited to qemu emulation.
I've tested ppc64le KVM guests on a ppc64le Ubuntu Eoan (19.10) host on a
POWER9 bare metal - PowerNV 9006-12P.
- Guests: Ubuntu Bionic (18.04); Ubuntu Disco (19.04); Ubuntu Eoan (19.10).
Also tested these guests on a ppc64le Ubuntu
> I added TCG support for mffsl, mffscrn, mffscrni, mffsce to QEMU, and I
> think they will appear in QEMU 4.2, which is not yet released.
Yeah I have found these.
> I found that the support for these instructions were missing because of
> my efforts to test work I did for GLibC to use those inst
** Tags added: architecture-ppc64le bugnameltc-181908 severity-low
targetmilestone-inin1910
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan VM fail
** Attachment added: "_usr_bin_find.0.crash"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1847806/+attachment/5297146/+files/_usr_bin_find.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Attachment added: "_usr_bin_apt.0.crash"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1847806/+attachment/5297148/+files/_usr_bin_apt.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Attachment added: "_usr_bin_dd.0.crash"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1847806/+attachment/5297147/+files/_usr_bin_dd.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Attached a few crash files (which already had retraces ran) if someone
needs them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan VM fails to inst
** Attachment added: "_usr_bin_gawk.0.crash"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1847806/+attachment/5297145/+files/_usr_bin_gawk.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Biggest question to IBM probably is, are there p9 HW machines out there that
lack mffsl?
Like a DD1.0 or a other PVR that is P9 but lacks the mffsl and would fail the
same way the TCG does?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
=>
https://git.qemu.org/?p=qemu.git;a=commit;h=31eb7dddacc242af24479885c3497b515e9f
maybe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan VM f
All fails I had were on sysdeps/powerpc/fpu/get-rounding-mode.h:30 which
is:
27 static inline int
28 get_rounding_mode (void)
29 {
That isn't even in 4.1 but it might be related as it is about mffsl.
There might be much more needed than just that, so I'm waiting for a
comment by IBM now that I identified the instruction that fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
To get a better hold of the actual bad instruction I installed Ubuntu
19.10 in a guest using the 3.1 based machine type. Then after the full
install (much more capable than the busybox of the installer) I switched
the machine type and booted up with the new machine type that also
implies the power9
No objection from me Thierry, the odd part is that e.g. find has failed
(we see that in syslog) but when I later run find it works just fine. So
the problem is how to exactly to trigger the issue for further
debugging.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Need to investigate to find which P9 instructions is said to be invalid
- then investigation in TCG code to ensure it is yet supported will be
done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184780
** Changed in: ubuntu-power-systems
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan VM fails to install
To manage
** Tags added: ppc64el
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => bugproxy (bugproxy)
** Changed in: ubuntu-power-systems
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan VM fails to insta
And as assumed before, it clearly isn't a D-I issue - mark that task as
invalid.
** Changed in: debian-installer (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Step #1 - repro:
Repro the case as is - running ppc64el install in TCG on Eoan with all settings
on default.
The system reports (proc/cpuinfo) POWER9 2.0 pvr 004e 1200 (just as expected).
And I have a bunch of illegal instructions hitting 4 binaries but essentially
always being in libc2.30.so.
B
While not too important if it only affects running under qemu's
emulation, I added a glibc task as someone maybe should take a look at
this on bare metal to be sure that the p9 code in glibc isn't generally
broken (there could be issues that just didn't surface yet).
--
You received this bug noti
The most likely theory that matches the above results would be that:
1. glibc in Eoan has some "if P9, then new code"
2. qemu TCG for ppc64el fails on that new code
TCG never was very important (it always is best effort and non production use),
and users seem to have a workaround by configuring f
Trying to help with the cpu type here - the default for the mentioned config
will be:
/usr/bin/qemu-system-ppc64le -name
guest=ubuntu19.10-ppc64le-test,debug-threads=on ...
-machine pseries-eoan,accel=tcg,usb=off,dump-guest-core=off ...
Without an explicit -cpu option set.
The libvirt XML jus
I was using the pseries-eoan virt-manager machine type, not sure what
that maps to as a CPU though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
Title:
eoan: ppc64el install on pseries-eoan
I'm not sure what to think about this failure; what's clear is it's not
'ubiquity', because we're dealing with debian-installer, but I'm not
sure what component. In fact, it looks more subtle than this, some sort
of more obscure failure:
Oct 11 18:42:06 base-installer: 'Ubuntu-Server 19.10 _Eoan E
** Attachment added: "/var/log/syslog log"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847806/+attachment/5296624/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
T
Seems like we hit an illegal instruction in libc. I used to be able to
install previous releases in a VM, so maybe gcc is emitting code that
the qemu can't emulate correctly.
Oct 11 18:42:46 localechooser: Generation complete.
Oct 11 18:42:46 kernel: [ 820.757132] debconf-set-sel[11139]: illegal
** Attachment added: "/var/log/media-info file"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847806/+attachment/5296622/+files/media-info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Attachment added: "/var/log/partman log"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847806/+attachment/5296623/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847806
46 matches
Mail list logo
