adding 'lspci -vnvn' output and
```
$ cat /proc/version_signature
Ubuntu 4.15.0-47.50-generic 4.15.18
```
** Attachment added: "lspci_output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823994/+attachment/5254524/+files/lspci-vnvn.log
--
You received this bug notification because
Public bug reported:
1. linux-generic-hwe-18.04-edge from bionic-updates is installed:
`linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65
arm64 [installed]`
```
$ dpkg -l |grep linux-generic
ii linux-generic-hwe-18.04-edge 4.18.0.16.65
I think it worth mentioning, as the machine above that we are not able
to deploy Disco is a Gigabyte(gbt-mt30)Cavium ThunderX 88XX, I've
decided to test Disco in other machine, not Gigabyte, but Cavium
ThunderX 88XX(CRB-2s) and I've noticed that in one machine Disco is
successfully deployed and in
- it fails in a machine where it has more than one disk - in this case an USB
stick. (machine nominated as recht)
curtin: curtin_recht_failed_disco https://paste.ubuntu.com/p/NVkPnxVDn5/
** Attachment added: "syslog_recht_failed_disco"
- it is deployed in a machine where it has just one disk. (machine nominated as
wright)
curtin: curtin_wright_success_disco https://paste.ubuntu.com/p/7CmYw57Rn6/
** Attachment added: "syslog_wright_success_disco"
just for the record:
BMC WEB UI - settings/date and time settings; select `Manually set date and
time` and then change the `time owner` to SPLIT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837443
Title:
[Power9][Witherspoon dd2.3] unable to set hwclock
To
Ok. I was able to reproduce the error and then I've followed the instructions
from comment #2
Step 1 (### With busctl on BMC), but I've got this output:
`An enumeration mapping was attempted for which no valid enumeration value
exists.` which I think it didn't work.
But what I understood from
Ryan,
Sorry for delay, we had a BMC issue and it required a manual intervention to
fix it.
I've tested Eoan in that machine and it also fails, it doens't show the same
curtin error as Disco shows, but Eoan is not deployed.
It get stuck and MAAS shows `Marking node failed - Node operation
** Description changed:
+ Description:
+ system does not boot after installing
linux-generic-hwe-18.04-edge/bionic-proposed
+
+ System:
Board Model:gbt-mt30
Board name: MT30-GS1-00
System name:R120-T33-00
SKU: CN8890-2000BG2601-AAP-Y-G
1) Ubuntu 18.04.3 LTS
Public bug reported:
Description:
system is stuck in a loop after installing
linux-generic-hwe-18.04-edge/bionic-proposed
System:
Cavium CN88XX
Board Model:crb-1s
SKU: CN8890-2000BG2601-AAP-PR-Y-G
1) Ubuntu 18.04.3 LTS (GNU/Linux 5.0.0-23-generic aarch64)
Description:Ubuntu 18.04.3
adding machine console log after 'sudo reboot':
https://paste.ubuntu.com/p/wYP45XV8xH/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845820
Title:
arm64: loop on boot after installing
adding the console log 25minutes after 'sudo reboot':
https://paste.ubuntu.com/p/nPzYPfHkwT/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845818
Title:
arm64: system does not boot after
Public bug reported:
Board Model:gbt-mt30
Board name: MT30-GS1-00
System name:R120-T33-00
SKU: CN8890-2000BG2601-AAP-Y-G
1) Ubuntu 18.04.3 LTS (GNU/Linux 5.0.0-23-generic aarch64)
Description:Ubuntu 18.04.3 LTS
Release:18.04
2) ((enable -proposed archive))
I'm marking as incomplete while we are waiting a response
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852057
Title:
The
attaching Console log
** Attachment added: "console_log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+attachment/5306902/+files/console_lippmann_kernel_panic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Description:
kernel panic while trying to deploy Bionic 18.04.3 Linux version
4.15.0-70-generic on Cavium ThunderX CN88XX (arm64)
System:
Board Model: gbt-mt30
Board name: MT30-GS0
System name:MT30-GS0
SKU: CN8890-2000BG2601-AAP-Y22-G
** Affects: linux (Ubuntu)
tested it in a 10 times loop and yes, it always have the same - it get
stuck here:
`[ 18.640574] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x000b `
`[ 18.641172] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x000b `
`[
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
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
You received this bug notification because you
** Changed in: ubuntu-power-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854071
Title:
Backport In-Memory Collection Counters (IMC) trace-mode patches
To
*** This bug is a duplicate of bug 1845820 ***
https://bugs.launchpad.net/bugs/1845820
adding console log
** Attachment added: "console_log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845818/+attachment/5295197/+files/gigabyte_bionic_hwe-edge-proposed_console_log
--
You
** Description changed:
- -- Problem Description --
- drmgr command is failing while trying to open console for IBMi.
+ SRU Justification:
- Log snap shot:
- Please make sure you have specified a valid locale (check your NLSPATH and
LANG environment variables. Your application will use
built and tested kernel versions available on:
https://people.canonical.com/~patriciasd/kernel-lp1893897/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893897
Title:
[Regression] Do not initiate
Ok. I see the patch got upstream accepted (commit
`63ffcbdad738e3d1c857027789a2273df3337624`).
We believe this need to be SRUed to Groovy, Focal, Bionic and Xenial. Do you
agree?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- == Comment: #0 - VASANT HEGDE - 2020-09-02 01:00:25
==
- --Problem Description---
- Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event. Instead wait for
predefined time before initiating shtudown.
-
- Contact Information = Vasant hegde
- Date: Thu Aug 20
I can verify on the same servers I've tested before.
Please let me know when the new image is available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890803
Title:
Groovy amd64 / arm64 / PowerPC
Ok. I see what I might have made wrong: trying to resurrect the session
(pressing 'r')
I was able to reproduce it just this way:
After it asks for upgrade:
```
If you select 'y' the system will be restarted.
Brian, answering comment#18, server upgraded has finished ~ 15h30`:
from logs: `=== Command detached from window (Tue Jul 21 15:23:36 2020) ===`
I just noticed it had bionic entries on sources.list when I was
installing bridge-utils:
```
Start-Date: 2020-07-21 16:28:23
Commandline: apt install
tested image from 20200819.1 - 19-Aug-2020 for arm64 and ppc64le and it
works now:
`Welcome to Ubuntu Groovy Gorilla (development branch) (GNU/Linux
5.4.0-42-generic aarch64)`
`Welcome to Ubuntu Groovy Gorilla (development branch) (GNU/Linux
5.4.0-42-generic ppc64le)`
--
You received this bug
Here the patch applied to Xenial-GA kernel:
https://people.canonical.com/~patriciasd/kernel-lp1892546/kernel_custom_xenial_ga/
Added some information about the system where I have tested/installed it and
how:
https://people.canonical.com/~patriciasd/kernel-lp1892546/notes
Let me know if you
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
release upgrader can restore
Thanks. I've tested upgrading from focal to groovy:
`ubuntu-release-upgrader-core/focal-proposed 1:20.04.25 all [upgradable
from: 1:20.04.24]`
```patricia@f-g:~$ dpkg -l |grep ubuntu-release
ii ubuntu-release-upgrader-core 1:20.04.25 all manage release
upgrades
```
Now, I
** 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/1890803
Title:
Groovy amd64 / arm64 / PowerPC deployment seems not
Thierry, thanks. Did you check it on Bionic ? (comment #15)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892546
Title:
Novalink (mkvterm command failure)
To manage notifications about this bug
thanks again Ryan.
manually adding serial to uvtool's virtio disk makes them work again - able to
deploy via MAAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895922
Title:
maas could not
Ryan, thanks. I tried adding curtin's daily PPA. I've added this to MAAS'
curtin_userdata
```
add_repo: ["add-apt-repository", "-y", "ppa:curtin-dev/daily"]
update: ["sh", "-c", "apt-get update"]
install: ["sh", "-c", "apt install -y curtin"]
```
I can see on MAAS' logs latest curtin was
hi Vasant,
according to:
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895031
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895328
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893115
"powerpc/pseries: Do not initiate shutdown when system is running on UPS" has
some info about this issue:
1. when it was working (able to deploy the enlisted VMs) we had MAAS 2.8.1 and
curtin version `curtin: Installation started.
(19.3-26-g82f23e3d-0ubuntu1~18.04.1)`.
2. it is possible to deploy VMs created via MAAS KVM host type virsh.
3. the VMs that we can not deploy
Robie, I just added uvtool because we cannot deploy anymore enlisted VMs
created via uvtool, which previously were working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895922
Title:
maas could
** Attachment added: "apt-clone_system_state.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1888916/+attachment/5399432/+files/apt-clone_system_state.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Brian, sorry, I noticed that I've sent the wrong 'main.log' file
from `/var/log/dist-upgrade/20200721-1523/` instead of
`/var/log/dist-upgrade/`.
I'm attaching the correct one. Sorry!
** Attachment added: "/var/log/dist-upgrade/main.log"
How did you detach from the screen session?
I was able to reproduce the issue in a container pressing `x` on the screen
session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
just wondering something, now we have the point release 20.04.1, when
I've upgraded the server it was not released yet, so I ran with `-d`:
`do-release-upgrade -d`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sure. Comment #1 has screenlog.0. I'm adding the main.log:
** Attachment added: "main.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1888916/+attachment/5398909/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Brian, yes:
Configure to always ask for the hostname:
```
/etc/molly-guard/rc:
ALWAYS_QUERY_HOSTNAME=true
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to
attaching dist-upgrade/screenlog.0
** Attachment added: "attaching dist-upgrade/screenlog.0"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1888916/+attachment/5395637/+files/screenlog.0
** Summary changed:
- upgrade from bionic to focal in a server with molly-guard
Public bug reported:
I've upgraded a server via `do-release-upgrade` from Ubuntu Bionic to
Focal, with molly-guard installed on it - molly-guard configured to
always ask for the hostname.
After it has finished:
```
System upgrade is complete.
Restart required
To finish the upgrade, a restart
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904906
Title:
5.10 kernel fails to boot with secure boot disabled
To manage
Thanks Waiki!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902694
Title:
Undetected Data corruption in MPI workloads that use VSX for
reductions on POWER9 DD2.1 systems
To manage notifications
Hi Waiki, thanks for raising this bug.
Please, could you share a test scenario for the verification of these patches -
how it can be tested? This is needed for every kernel SRU. Thanks in advance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
- == Comment: #0 - Waiki Wright - 2020-11-02 17:00:07
- ==
+ SRU Justification:
- ---Problem Description---
+ [Impact]
- A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52 and
- 20.10 - 5.8.0-26 kernel on Power 9. The root cause is found in the
-
** Changed in: ubuntu-power-systems
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Patricia Domingues (patriciasd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Vasant, thanks for the verification on this bug.
Could you also check the other opal-prd bug which also needs verification,
please:
```
"Ubuntu 20.04: opal-prd fails to start on 20.04"
https://bugs.launchpad.net/bugs/1905393
```
--
You received this bug notification because you are a member
Hi Thierry thanks again for testing this,
>From your crash files, I noticed you're using an image built on October
>-2020-10-22 14:33
>(url=http://cdimage.ubuntu.com/releases/20.10/release/ubuntu-20.10-live-server-ppc64el.iso)
> and also subiquity is an old version:
` 2021-01-26 08:10:48,735
Thanks again Thierry, there's a new subiquity version available.
Please, could you try with Hirsute/21.04 -
This URL:
`http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/hirsute-live-server-ppc64el.iso`
and you do not need to add `subiquity-channel=...` on kernel command line.
--
You
** Summary changed:
- [21.10] gnutls28 asm accelerated crypto
+ [22.04] gnutls28 asm accelerated crypto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839493
Title:
[22.04] gnutls28 asm
Po-Hsu Lin,
Thanks for the info.
I was able to reproduce the issue on other 2 Power8 servers, but just running
the `reuseport_bpf_cpu test` more than once (as you mentioned on comment#3).
I've tested this with focal-hwe (Linux thiel 5.11.0-27-generic) and hirsute
(5.11.0-31-generic).
steps:
** Attachment added: "lscpu_gulpin"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524415/+files/lscpu_gulpin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927076
** Attachment added: "lscpu_thiel"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524414/+files/lscpu_thiel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927076
Title:
Krzysztof, you were on a PowerVM LPAR (P8LPAR05), just let me know if
there's anything that need to be tested
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927076
Title:
IPv6 TCP in
Also re-ran on
`entei` it is also a POWER8 (8335-GTA) with Hirsute latest kernel
(5.11.0-34-generic)
hit the same error - second run of `reuseport_bpf_cpu`:
```
[ 232.349547] Oops: Exception in kernel mode, sig: 4 [#1]
[ 232.349647] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
Ok I've re-ran the test with latest kernel versions on the same systems:
`thiel` (8001-22C) with focal-hwe (5.11.0-34-generic):
```
[ 3255.763649] Oops: Exception in kernel mode, sig: 5 [#1]
[ 3255.763723] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
```
And
`gulpin` (8335-GTA) with
** Attachment added: "lscpu_entei"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524453/+files/lscpu_entei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927076
Title:
Cascardo, I was trying to reproduce the issue as Po-Hsu Lin has mentioned (#3),
but the hotplug leaves the system in the same state (shows this output):
```
./cpu-hotplug/cpu-on-off-test.sh
pid 21291's current affinity mask:
pid 21291's new affinity mask: 1
CPU
Public bug reported:
I've upgraded a server via `do-release-upgrade` from Ubuntu Bionic to
Focal. It was ENI configured (since Ubuntu 12.04 Precise):
```
auto lo
iface lo inet loopback
# The primary network interface
iface eth0 inet manual
# The primary bridge interface
auto br0
iface br0
I know it could be a special case where bridge-utils was not manually
installed and you are still using ENI instead of netplan, but other
people may hit the same problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
kernel with the patches:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1959532
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959532
Title:
[22.04 FEAT] Transparent PCI device recovery
To
built kernel available and tested:
https://people.canonical.com/~patriciasd/kernel-lp1959532/
```
ubuntu@s1lp13:~$ uname -a
Linux s1lp13 5.15.0-23-generic #23 SMP Wed Mar 16 00:21:04 UTC 2022 s390x s390x
s390x GNU/Linux
```
--
You received this bug notification because you are a member of
** Changed in: ubuntu-power-systems
Status: New => 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/1960255
Title:
Prevent do-release-upgrades on P8 systems from focal or impish to
** 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/1961425
Title:
22.04: FTBFS due to test failure
To manage
** Summary changed:
- [22.04] gnutls28 asm accelerated crypto
+ [22.10] gnutls28 asm accelerated crypto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839493
Title:
[22.10] gnutls28 asm
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Committed
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
if we try to create a VM with less than the min req it will raise a
warning:
a) trying a jammy/22.04 VM:
WARNING Requested memory 1024 MiB is less than the recommended 2048 MiB for
OS ubuntu22.04
b) trying a noble/24.04 VM:
WARNING Requested memory 2048 MiB is
Hello IBM, we have now a bootstrapped .NET 8 build for ppc64el in this
PPA:
Our toolchain team has added this PPA for testing:
https://launchpad.net/~mateus-morais/+archive/ubuntu/dotnet8-ppc64el-ppa
Please, could you try it and let us know? thank you.
--
You received this bug notification
** 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/2064345
Title:
Power guest secure boot with key management: userspace
** 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/2064321
Title:
Power guest secure boot with key management: kernel
** 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/2064319
Title:
Power guest secure boot with key management: GRUB2
Public bug reported:
After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le
Power9 or Power10 :
error: out of memory.
Press any key to continue...
OF stdout device is: /vdevice/vty@3000
Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003)
This is happening with Kernel 6.8 (currently available image noble-live-
server-ppc64el.iso `2024-03-05 09:03`). I was able to install noble on
the same systems last week, when Noble still had kernel 6.6.
I'm also able to install Jammy 22.04.4 on both mentioned LPARs - P9 and
P10.
The issue is
re-tested with today's image http://cdimage.ubuntu.com/ubuntu-
server/daily-live/20240307/ - same
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056491
Title:
not able to install noble on PowerVM
Paolo,
I was able to install it (image from March 1st `20240301`) , update to the
bootstrap kernel from the PPA you sent:
patricia@noble-1mar:~$ cat /var/log/installer/media-info
Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily ppc64el
(20240301)patricia@noble-1mar:~$
patricia@noble-1mar:~$
Hi Chavez, thanks for checking it. I see this output:
```
Memory Keyboard Network Speaker ok
0 > printenv real-base
-- Partition: common Signature: 0x70 ---
real-basec0 c0
ok
0 >
```
I'm able to install
updating subiquity to Version `22.02.2+git2100.4fba6aa7` - I'm now able
to import my launchpad' SSH key.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055702
Title:
installer crashes after
I was able to successfully install and boot PowerVM partitions - Power9
and Power10 with the latest kernel `6.8.0-20.20` (today's image -
20240405) :
POWER10 LPAR:
```
patricia@noble-a5:~$ cat /var/log/installer/media-info
Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily ppc64el
I was checking this and there's no issue for having virtual machines on
Power9 bare metal, tried jammy and noble VMs on a host with Noble+
kernel 6.8 (currently -proposed).
For the nested virtualization scenario, on the Power10 PowerVM system -
we don't have the required firmware for it, but I
86 matches
Mail list logo
