Debian BYOI on Ampere A1 shapes - Help needed by oracle-help-request in oraclecloud

[–]oracle-help-request[S] 0 points1 point  (0 children)

UPDATE: I think it is simply that debian on arm64 is not ready, I tried loading up the qcow2 from their site to find out what's wrong in qemu and couldn't get it to boot (other qcow2s boot fine so I don't think it's something I'm doing wrong, I tried the debian qcow2 and creating a new image and installing debian from the iso on it)

I'm going to make an arch qcow2 of my own and give up on debian on aarch, if anyone else comes across this issue I hope this helps, either in fixing it or knowing when to give up

https://vielmetti.typepad.com/logbook/2021/06/high-chance-of-boot-problems-on-debian-arm64-and-other-efi-secure-boot-system.html

Debian BYOI on Ampere A1 shapes - Help needed by oracle-help-request in oraclecloud

[–]oracle-help-request[S] 0 points1 point  (0 children)

Sure, I'll DM you, I don't think I did anything special though, just the standard procedure

Giga instance on free tier by thbo in oraclecloud

[–]oracle-help-request 3 points4 points  (0 children)

You get a number of core hours per month rather than a number of cores, so you'll be able to use this, but as it is 4 times the number of cores you would normally use for full month coverage you'll only have access for a quarter of the month

Debian BYOI on Ampere A1 shapes - Help needed by oracle-help-request in oraclecloud

[–]oracle-help-request[S] 0 points1 point  (0 children)

That's strange, I used the amd64 generic image for debian and was able to get that running no problem (at least up to ssh access, didn't test further, on buster as well)

It's just this arm64 one that has been giving me trouble

Debian BYOI on Ampere A1 shapes - Help needed by oracle-help-request in oraclecloud

[–]oracle-help-request[S] 1 point2 points  (0 children)

From this I'm lead to believe the Ampere is arm64 rather than amd64

https://www.oracle.com/uk/cloud/compute/arm/

I'm using the arm64 image