On Mon, Jun 14, 2021 at 11:23:06PM -0000, dann frazier wrote:
> btw, this bug says bionic guests fails to boot - do we know if other
> Ubuntu guests versions are OK?
Thanks for your efforts looking into this so far.
Yeah, I've only seen it in bionic. I tried spawning instances for all
current supported releases, and only bionic failed:
ubuntu@juju-806ee7-stg-proposed-migration-43:~$ for ip in $(openstack server
list | awk -F'[= |]+' '/bos01-arm64/ { print $6 }'); do timeout 60s ssh
-oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no ubuntu@${ip}
'lsb_release -a; uptime'; done
Warning: Permanently added '10.43.128.5' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.7 LTS
Release: 16.04
Codename: xenial
No LSB modules are available.
08:21:32 up 3 days, 21:33, 0 users, load average: 0.00, 0.00, 0.00
Warning: Permanently added '10.43.128.22' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description: Ubuntu Impish Indri (development branch)
Release: 21.10
Codename: impish
No LSB modules are available.
08:21:34 up 3 days, 21:33, 0 users, load average: 0.00, 0.00, 0.00
Warning: Permanently added '10.43.128.8' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description: Ubuntu 21.04
Release: 21.04
Codename: hirsute
No LSB modules are available.
08:21:36 up 3 days, 21:33, 0 users, load average: 0.00, 0.00, 0.00
Warning: Permanently added '10.43.128.4' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description: Ubuntu 20.10
Release: 20.10
Codename: groovy
No LSB modules are available.
08:21:38 up 3 days, 21:33, 0 users, load average: 0.00, 0.00, 0.00
Warning: Permanently added '10.43.128.15' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
No LSB modules are available.
08:21:40 up 3 days, 21:33, 0 users, load average: 0.03, 0.01, 0.00
ssh: connect to host 10.43.128.20 port 22: No route to host # that's the
bionic instance
and I double checked they all eneded up on an eMAG.
(I was trying all releases with a reboot loop to try to reproduce the
other issue Julian mentioned on ubuntu-devel, but failed to cause it to
happen ...)
What do you think about the "MDS mitigation" BIOS setting idea as a
difference between the working/broken installations, is it worth trying
to get IS to flip that? Seems like it's probably sane to have it on,
but it'd maybe be useful info.
Cheers,
--
Iain Lane [ [email protected] ]
Debian Developer [ [email protected] ]
Ubuntu Developer [ [email protected] ]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931728
Title:
[scalingstack bos01] bionic (arm64) instances always fail to boot on
eMAGs in this cloud
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1931728/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
