Sorry Corey, I don't have any test environment in hand to verify
currently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855691
Title:
Can't choose a fedora-coreos image when creating a cluster
@Christian thanks for the update. Nothing new on my side. So currently,
we have to build the Arm64 iPXE binary ourselves.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890230
Title:
arm64 ipxe
Hi Lucas,
It seems that after I added "root=LABEL=cloudimg-rootfs" kernel cmdline
parameter into grub.cfg, it doesn't happen again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892292
Title:
Hi @cleary, only need to update grub efi on your tftp server. I use
grub-mknetdir cmd to do it. Like
https://github.com/openstack/ironic/blob/master/devstack/lib/ironic#L2673-L2674
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To be noted that this issue also exists in Debian 10 and Ubuntu 18.04.
Because they all has commit 781b3e5efc3 (tftp: Do not use priority
queue).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892290
Verified that focal grub2 with above commit works.
grub> linux vmlinuz-5.4.0-47-generic
grub> echo $?
0
grub> initrd initrd.img-5.4.0-47-generic
grub> echo $?
0
Rebuild grub2 deb with above commit and install
$ git clone -b applied/ubuntu/focal-updates
Similar bug: https://bugzilla.redhat.com/show_bug.cgi?id=1869987
I've tried boot by cmdline, looks the same issue.
grub> linux vmlinuz-5.4.0-47-generic
grub> echo $?
0
grub> initrd initrd.img-5.4.0-47-generic
error: timeout reading `initrd.img-5.4.0-47-generic'.
grub> echo $?
28
It looks like it
Any progress on this bug? @janitor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892290
Title:
PXE load Focal initrd.img-5.4.0-42-generic always timeout
To manage notifications about this bug go
Yes, focal initrd is a little larger than bionic one.
$ ls -lh /boot/initrd.img-5.4.0-42-generic
-rw-r--r-- 1 root root 81M Jul 22 06:35 /boot/initrd.img-5.4.0-42-generic
$ ls -lh bm-ubuntu-bionic.initrd
-rw-r--r-- 1 root root 52M Aug 10 03:49 bm-ubuntu-bionic.initrd
But not sure if it is
Public bug reported:
iscsi boot fails to boot into rootfs, due to iscsi root disk is not
available in time and mount root fails.
After add 10 secs delay, it can boot into iscsi root disk successfully.
It seems that 'udevadm settle' is not enough to wait for iscsi disk is
available.
---
I encounter a Synchronous Exception crash when booting shim with
qemu-system-aarch64 on Focal. But on an real aarch64 server this doesn't happen.
Not sure if it is the same issue.
software:
qemu-efi-aarch64/focal,now 0~20191122.bd85bf54-2ubuntu3 all
[installed,automatic]
UEFI firmware for
Public bug reported:
PXE booting Focal initrd always gets a timeout, but PXE booting Bionic initrd
works
error: timeout reading `initrd.img-5.4.0-42-generic'.
grub.cfg
menuentry "boot_iscsi" {
linux vmlinuz-5.4.0-42-generic ...
initrd initrd.img-5.4.0-42-generic
}
grub,
Note that PXE booting Bionic initrd works.
Even though change the initrd compress to gz, it still gets timeout
$ unmkinitramfs initrd.img-5.4.0-42-generic ubuntu-focal-initrd/
$ cd ubuntu-focal-initrd/; find . | cpio -H newc -o | gzip >
../ubuntu-focal-new.initrd
** Also affects:
@rafaeldtinoco
Thanks for quickly responding to the bug.
Our use case is booting real bare metal aarch64 servers from remote iSCSI
volume[1]. Which uses iPXE's iSCSI boot functionality. The booting iPXE script
looks as bellow:
-
:boot_iscsi
imgfree
set username xx
set password
** Summary changed:
- arm64 ipxe package isn't an arm64 built
+ arm64 ipxe package isn't an arm64 build
** Description changed:
- arm64 ipxe package is an x86-64 built.
+ arm64 ipxe package is an x86-64 build.
$ apt install ipxe # on arm64 server
$ file /boot/ipxe.efi
/boot/ipxe.efi:
Public bug reported:
arm64 ipxe package is an x86-64 built.
$ apt install ipxe # on arm64 server
$ file /boot/ipxe.efi
/boot/ipxe.efi: MS-DOS executable PE32+ executable (DLL) (EFI application)
x86-64, for MS Windows
It should be built for aarch64 platform:
$ git clone
Tested linux-next tag next-20200706, which got bellow fixed patches,
iSCSI target login, disk read/write are OK
5a0c256d96f0 scsi: target: tcmu: Fix crash on ARM during cmd completion
3145550a7f8b scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
3c58f737231e scsi: target: tcmu:
Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=208045
Seems that the fixed patch[1] is not in v5.8-rc4 yet.
[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=5a0c256d96f0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Tested 5.8.0-050800-generic,it also encounters this issue.
** Bug watch added: Linux Kernel Bug Tracker #208045
https://bugzilla.kernel.org/show_bug.cgi?id=208045
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux (Ubuntu)
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/1886364
Title:
initiator causes kernel crash when login lun/disk on Focal
Public bug reported:
Software version
linaro@j13-r120-t32-09:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
linaro@j13-r120-t32-09:~$ uname -a
Linux j13-r120-t32-09 5.4.0-37-generic #41-Ubuntu SMP
21 matches
Mail list logo
