[Touch-packages] [Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower
I do not see anything actionable for systemd at this time. Please re- open if I am mistaken. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748280 Title: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower Status in OpenStack Compute (nova): Confirmed Status in nova package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Within Canonical's multi-architecture compute cloud, I observed that arm64 instances were taking an unreasonable amount of time to return from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same cloud region). Digging into this, I find that a nova soft reboot request is doing nothing at all on arm64 (no events visible within the qemu guest, and no reboot is triggered within the guest), and then after some sort of timeout (~2m), 'nova reboot' falls back to a hard reset of the guest. Since this is entirely predictable on the arm64 platform (because there's no implementation of ACPI plumbed through), 'nova reboot' on arm64 should just skip straight to the hard reboot and save everyone some clock time. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1748280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower
** Changed in: nova (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748280 Title: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower Status in OpenStack Compute (nova): Confirmed Status in nova package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Within Canonical's multi-architecture compute cloud, I observed that arm64 instances were taking an unreasonable amount of time to return from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same cloud region). Digging into this, I find that a nova soft reboot request is doing nothing at all on arm64 (no events visible within the qemu guest, and no reboot is triggered within the guest), and then after some sort of timeout (~2m), 'nova reboot' falls back to a hard reset of the guest. Since this is entirely predictable on the arm64 platform (because there's no implementation of ACPI plumbed through), 'nova reboot' on arm64 should just skip straight to the hard reboot and save everyone some clock time. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1748280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower
arm64 maps to AARCH64. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748280 Title: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower Status in OpenStack Compute (nova): Confirmed Status in nova package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Within Canonical's multi-architecture compute cloud, I observed that arm64 instances were taking an unreasonable amount of time to return from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same cloud region). Digging into this, I find that a nova soft reboot request is doing nothing at all on arm64 (no events visible within the qemu guest, and no reboot is triggered within the guest), and then after some sort of timeout (~2m), 'nova reboot' falls back to a hard reset of the guest. Since this is entirely predictable on the arm64 platform (because there's no implementation of ACPI plumbed through), 'nova reboot' on arm64 should just skip straight to the hard reboot and save everyone some clock time. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1748280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower
On the surface, it seems like this is something we could check for in the libvirt driver and skip the soft reboot timeout cycle if ARM64. The question I have is, which architecture fields does "ARM64" map to in nova? ARMV6 or ARMV7 or ARMV7B or AARCH64 or all of them? Or one that I missed? [1] [1] https://github.com/openstack/nova/blob/da1669/nova/objects/fields.py#L108-L112 ** Changed in: nova Importance: Undecided => Medium ** Changed in: nova Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748280 Title: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower Status in OpenStack Compute (nova): Confirmed Status in nova package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Within Canonical's multi-architecture compute cloud, I observed that arm64 instances were taking an unreasonable amount of time to return from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same cloud region). Digging into this, I find that a nova soft reboot request is doing nothing at all on arm64 (no events visible within the qemu guest, and no reboot is triggered within the guest), and then after some sort of timeout (~2m), 'nova reboot' falls back to a hard reset of the guest. Since this is entirely predictable on the arm64 platform (because there's no implementation of ACPI plumbed through), 'nova reboot' on arm64 should just skip straight to the hard reboot and save everyone some clock time. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1748280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower
** Tags added: libvirt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748280 Title: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower Status in OpenStack Compute (nova): Confirmed Status in nova package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Within Canonical's multi-architecture compute cloud, I observed that arm64 instances were taking an unreasonable amount of time to return from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same cloud region). Digging into this, I find that a nova soft reboot request is doing nothing at all on arm64 (no events visible within the qemu guest, and no reboot is triggered within the guest), and then after some sort of timeout (~2m), 'nova reboot' falls back to a hard reset of the guest. Since this is entirely predictable on the arm64 platform (because there's no implementation of ACPI plumbed through), 'nova reboot' on arm64 should just skip straight to the hard reboot and save everyone some clock time. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1748280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower
** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748280 Title: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower Status in OpenStack Compute (nova): New Status in nova package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Within Canonical's multi-architecture compute cloud, I observed that arm64 instances were taking an unreasonable amount of time to return from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same cloud region). Digging into this, I find that a nova soft reboot request is doing nothing at all on arm64 (no events visible within the qemu guest, and no reboot is triggered within the guest), and then after some sort of timeout (~2m), 'nova reboot' falls back to a hard reset of the guest. Since this is entirely predictable on the arm64 platform (because there's no implementation of ACPI plumbed through), 'nova reboot' on arm64 should just skip straight to the hard reboot and save everyone some clock time. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1748280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower
This affects systemd-fsckd autopkgtest ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748280 Title: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower Status in nova package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Within Canonical's multi-architecture compute cloud, I observed that arm64 instances were taking an unreasonable amount of time to return from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same cloud region). Digging into this, I find that a nova soft reboot request is doing nothing at all on arm64 (no events visible within the qemu guest, and no reboot is triggered within the guest), and then after some sort of timeout (~2m), 'nova reboot' falls back to a hard reset of the guest. Since this is entirely predictable on the arm64 platform (because there's no implementation of ACPI plumbed through), 'nova reboot' on arm64 should just skip straight to the hard reboot and save everyone some clock time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1748280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
