** Also affects: qemu
Importance: Undecided
Status: New
** No longer affects: qemu
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-
Changing the affected package from "linux (Ubuntu)" (kernel) to "qemu
(Ubuntu)" as affected package, since the attached patch set is for qemu.
** Package changed: linux (Ubuntu) => qemu (Ubuntu)
** Also affects: qemu
Importance: Undecided
Status: New
** No longer affects: qemu
** Also
** Also affects: qemu
Importance: Undecided
Status: New
** No longer affects: qemu
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: qe
The fix was sent to the kernel teams mailing list:
https://lists.ubuntu.com/archives/kernel-team/2021-March/thread.html#118449
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-power-systems
Status: Confirmed => In Progress
--
You received this b
can be proofed that this patched kernel fixes the problem, I can
go ahead and work on a patch submission for hirsute/21.04. (kernel
freeze is April 8th)
** Changed in: ubuntu-power-systems
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Frank
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1920784
Title:
qemu-system-ppc64le fails with kvm acceleration
Statu
Maybe this will 'automagically' get fixed and change if MAAS got rebased on LXD.
LXD 4.2 comes with KVM support for s390x and the MAAS version that is going to
be based on LXD is (iirc) 2.9?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
I still think that #29 could be a viable fix for this.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1859656
Title:
[2.6] Unable to reboot s390x KVM machine after initial deploy
Status in MAAS:
In between I found the time to setup an env. build upon older releases:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
$ dpkg -l | grep -i qemu
ii qemu-block-extra:s390x1:2.11+d
@Lee, do you think that the boot log from comment #18 looks fine?
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1859656/+attachment/5323507/+files/boot_console.txt
What would be the usual next step for MAAS KVM on s390x if the above is
successful (me not really knowing the exact internal flow)
I doubled check today again with sfeole and he confirmed that it worked
for him as well (and not only for me) when he just started using MAAS
KVM on s390x and had his initial setup...
Anyway, I'm now sure on how much effort we should spent on recreating the old
situation (I may try some old qemu/
It took some time (due to travel), but I was now able to do a setup
based on the old 2.6.0 version [2.6.0 (7803-g6fc5f26eb-
0ubuntu1~18.04.1)] for testing.
And with the combination:
$ apt-cache policy maas
maas:
Installed: 2.6.0-7803-g6fc5f26eb-0ubuntu1~18.04.1
Candidate: 2.6.0-7803-g6fc5f26e
The general issue with multiple boot elements on s390x was indeed already
identified back in 2017, and a ticket was opened and reverse mirrored to IBM
(so it should never have worked that way):
LP 1736511 (and btw. RH ticket is referenced there as well)
--
You received this bug notification bec
I took the time and recreated a MAAS setup (latest stable 2.2) on s390x and it
looks like this:
- I could start a deployment and ran through the states:
- Power On, Commissioning (Performing PXE boot)
- Power On, Commissioning (Gathering Information)
- Power On, Ready
- Power Off, Read
** Tags added: s390x
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1859656
Title:
[2.6] Unable to reboot s390x KVM machine after initial deploy
Status in MAAS:
New
Status in QEMU:
Incomplete
S
** Changed in: maas
Status: Incomplete => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1859656
Title:
[2.6] Unable to reboot s390x KVM machine after initial deploy
Status in MAAS:
Ne
** Tags added: qemu-20.04
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1852781
Title:
qemu s390x on focal - applications breaking
Status in QEMU:
Incomplete
Status in Ubuntu on IBM z Systems:
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1852781
T
** Tags added: s390x
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1852781
Title:
qemu s390x on focal - applications breaking
Status in QEMU:
Incomplete
Bug description:
Running qemu-system-s
** Information type changed from Private to Public
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1842774
Title:
Enhanced Hardware Support - Finalize Naming
Status in QEMU:
Incomplete
Status in U
*** This bug is a duplicate of bug 1842774 ***
https://bugs.launchpad.net/bugs/1842774
** Information type changed from Private to Public
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1842916
Ti
** Also affects: qemu
Importance: Undecided
Status: New
** No longer affects: qemu
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
** Also affects: qemu
Importance: Undecided
Status: New
** No longer affects: qemu
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Critical
--
You received this bug notification because you are
23 matches
Mail list logo
