YESSSSS!!!!!!!! I FINALLY DID IT!!!!!!! WOO!!! :D:D:D Less gooo! 👉👶👈

I've been trying this for HOURS!! But what you said was exactly what I was looking for! I didn't realise that the other link that existed in the lab 1 worksheet here showed an alternative method for getting the .qcow2 file.

I didn't bother looking at the link as the hyperlink text literally just said "Using UTM on M-series Mac laptops", something I already knew. I would recommend that there should be more emphasis on the fact that there IS a way to get this working on M-series devices consistently. Perhaps something like "In this link there's a method to get the vagrant image working on UTM/M-series devices but it's uncertain" or something else.

Once I booted it up on UTM there was life!!

P.S. For anyone who's wondering what on earth the username and password needed to log in, they both are vagrant. I was a bit confused there for a second. 😅

WAIT! Less stop!! 👈😭👉

By following the instructions on https://cits3007.github.io/labs/lab01-utm.html, the .box file they get us to download is from the libvirt provider (you can see this by looking at the URL for the box, https://app.vagrantup.com/arranstewart/boxes/cits3007-ubuntu2004/versions/0.1.4/ providers/libvirt/ unknown/vagrant.box). When you download the same file by using the virtualbox provider, you end up with the same files that I have been trying to (unsuccessfully, mind you) convert to the mystical .qcow2 format.

The commands on the lab says to use the provider=virtualbox option (see step 5 on lab 1 and look for vagrant up --provider=virtualbox).

This also leads to the terminal showing up with vagrant@ubuntu2004 instead of the typical vagrant@cits3007-ubuntu2004 as seen on my friends' non Apple silicon devices.

Even if there is 2 different providers, if I continue to use the libvirt environment, will I be penalised if I get some weird incompatibility issues that are caused purely because I was using the libvirt development environment???

This issue has been plaguing me for long enough and I need to make sure I have this environment set up so then I can become familiar with coding within it.

I would love some clarification if we'd be allowed to use the libvirt provider or not for projects have both environments be considered for marking as well. This is because us Apple Silicon device users have literally no other viable path to even being fairly assessed in this unit.

Thanks.

P.S. Apparently none of the Ubuntu lab machines allow for logging in or installation of new packages or whatever due to technical skill issues. 🍜😭

"Henuka Daluwatta" [email protected] wrote:

P.S. For anyone who's wondering what on earth the username and password needed to log in, they both are vagrant. I was a bit confused there for a second.

Glad to hear you got things working. I'll add the username and password details to the lab sheet.

Cheers,

Arran

"Henuka Daluwatta" [email protected] wrote:

Even if there is 2 different providers, if I continue to use the libvirt environment, will I be penalised if I get some weird incompatibility issues that are caused purely because I was using the libvirt development environment???

There are no incompatibilities between the libvirt disk image and the virtualbox disk image. They contain exactly the same software packages, running on exactly the same Linux kernel, on exactly the same (virtualised) hardware. The hostname (stored in /etc/hostname) may be different, but that is not something that will affect the compilation of C code.

Cheers

Arran