--- Comment From heinz-werner_se...@de.ibm.com 2021-02-25 07:33 EDT---
IBM Bugzilla status->closed Fix Released with 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-27 08:03 EDT---
ok, same behavior like with the PPA package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT]
--- Comment From niklas.schne...@ibm.com 2021-01-22 11:01 EDT---
(In reply to comment #89)
> So for now I think we should pick up the patches as they are,
> since they already provide value and we will be at a similar level like on
> groovy,
> mention the current situation in the release
--- Comment From niklas.schne...@ibm.com 2021-01-22 10:39 EDT---
(In reply to comment #87)
> Ubuntu supports NVMe Multipath on all architectures in Focal. I know that
> some other distributions do not.
>
> Setting nvme-core.multipath=0 for s390x isos only, or changing kernel config
> to
--- Comment From niklas.schne...@ibm.com 2021-01-22 10:02 EDT---
Hi Frank,
we've now internally confirmed that setting the "nvme-core.multipath=0" Kernel
parameter as a workaround makes "chreipl node" succeed with NVMes that
otherwise break the current chreipl due to its lack of
--- Comment From jjhe...@us.ibm.com 2021-01-15 08:35 EDT---
(In reply to comment #82)
> Is the NVMe drive with or without nvme-multipath support?
> Does it help to disable multipath?
>
> Please see the below pullrequest from Canonical employee in efivar project
> that explains the issue a
--- Comment From jjhe...@us.ibm.com 2021-01-14 09:00 EDT---
chreipl currently fails on Ubuntu 20.04 when given a device node (e.g. chreipl
/dev/nvme0n1p1). This is because chreipl cannot find the expected sysfs
directory structure. We are investigating the best way to fix this. If the
--- Comment From jjhe...@us.ibm.com 2020-12-01 08:05 EDT---
(In reply to comment #74)
> @Jason, seems to be some build failures. Can you please have a look.
It looks like there are two versions of this patch applied:
[PATCH] s390-tools: zipl: Fix NVMe partition and base device detection
--- Comment From jjhe...@us.ibm.com 2020-11-17 16:23 EDT---
I've attached the three backported s390-tools patches for focal-proposed. They
received a basic compile test and a very quick "it runs" sanity check.
If we need more testing at this stage, let me know and I'll see about
getting
--- Comment From jjhe...@us.ibm.com 2020-11-16 14:19 EDT---
(In reply to comment #60)
> Hi Jan, yes (almost) all Ubuntu packages are hosted nowadays at our
> Launchpad git (at least all packages in main, incl. s390-tools).
> Please see: https://code.launchpad.net/ubuntu/+source/s390-tools
--- Comment From jan.hoepp...@de.ibm.com 2020-11-16 11:16 EDT---
Canonical,
are there public s390-tools repositories with the Ubuntu versions available
that we can mirror internally and which we could then use for potential
backport work (such as this feature seems to require)?
Please
--- Comment From heinz-werner_se...@de.ibm.com 2020-11-05 12:23 EDT---
We were finally able to cobble together a system to perform some testing on the
provided Ubuntu test kernel.
Here is what was tested (using Debian s390-tools 2.14):
- Using zipl to install the bootloader to NVMe works
12 matches
Mail list logo
