| 7 Nov 2024 |
 Arian | * Or Connect -> EC2 Serial Console. Should work too | 20:14:26 |
| Arian | * get-console-output without --latest is only available after instance termination . Or around 15 minutes after the instance started | 20:14:45 |
 quyse | In reply to @arianvp:matrix.org
get-console-output without --latest is only available after instance termination . Or around 15 minutes after the instance started oh, thank you very much! indeed it returns the output after termination. I wonder why the web interface doesn't warn about it | 20:17:25 |
| Arian | But the --latest flag should work too | 20:18:18 |
| quyse | In reply to @arianvp:matrix.org
But the --latest flag should work too yes, just tried it, it works! not immediately after instance launch, but quite quickly | 20:20:56 |
| quyse | interesting, after termination the output is again empty, with --latest or without | 20:27:40 |
| quyse | ok, a few more munutes after the termination get-console-output starts returning the full output again. I guess it's just a bit of weirdness on AWS side | 20:32:47 |
| 8 Nov 2024 |
 tuxiqae | Arian: Thanks for the help the other day
I was able to write the following thanks to your help!
https://github.com/tuxiqae/autovm
| 22:56:29 |
| tuxiqae | BTW, had to use 24.05 since AMI building in unstable seems to be broken due to hash mismatch in the getty package. Couldn't figure where the faulty hash is defined so I didn't fix it yet | 22:58:29 |
| tuxiqae | 
Download image.png | 22:58:33 |
| 9 Nov 2024 |
 colemickens |
Smoke test
waiting for instance to be healthy.
hmmm
| 04:26:31 |
| Arian | Sometimes AWS just .... Doesn't work | 08:47:34 |
| Arian | I've had it before where instance just doesn't get into the healthy state and nothing was wrong | 08:47:53 |
| 10 Nov 2024 |
|  @sbc64:matrix.org left the room. | 20:02:20 |
| 11 Nov 2024 |
 commiterate | Draft PR for amazon-ec2-net-utils: https://github.com/NixOS/nixpkgs/pull/355111
Someone will need to update the NixOS systemd libs to allow setting the [Install] options in the systemd unit config.
| 02:34:15 |
| colemickens | Oh no, sorry, it was just a joke about smoking. :( | 17:31:37 |
| colemickens | Though that does remind me, it maybe doesn't matter, but I am curious if you thought about using systemd-boot instead of grub on the EFI image.s | 17:32:19 |
| commiterate | I believe some instance types only support the legacy-bios boot mode which means we can't use systemd-boot for those. | 17:36:47 |
| Arian | It makes the build more complicated | 17:36:51 |
| Arian | And for x86 we don't have UEFI-only images. Just hybrid ones. And systemd-boot doesn't support that | 17:37:08 |
| Arian | Only grub | 17:37:10 |
| colemickens | I see, that probably explains the slightly odd (unaligned?) partition layout I was seeing in a booted instance with legacy bios partition. | 17:37:38 |
| Arian | The current images are bios-only | 17:38:07 |
| Arian | I have a PR open for hybrid | 17:38:14 |
| colemickens | I built one with your PR. | 17:38:16 |
| colemickens | (and booted) | 17:38:21 |
| Arian | Ah gotcha | 17:38:21 |
| Arian | I think it should be pretty simple for people to build an image that's UEFi only and with systemd-boot | 17:39:13 |
| Arian | It's just that quite a few instance types on AWS don't support UEFi at all | 17:39:23 |
| Arian | E.g. the T2 family. So we can't really use it for the public images | 17:39:37 |
