WIP: Audit the VM Launch Process

[jesse-peters]

The vm doesn't currently launch on my mac, so I have been modifying the scripts to allow for the additional architecture.

[jesse-peters]

Hoping someone can point me in the right direction here. I've been working on getting the VM building on my machine. I'm running on a mac, so I had to tweak a bunch of the processes to handle the different chip (There is cleanup required on all of my modifications still). I can run this now without an issue locally:

make build-container
make kernel
make initramfs
make network

I've created a new docker container that has libvirt in it, and I run make virsh-init followed by make virsh-start inside that container. I get the following error when I run this (I have modified the libvirt.xml file to match my system)

However, when I run that, I get this error in the libvirt logs:

virCgroupSetValueRaw:502 : Unable to write to '/sys/fs/cgroup/machine/qemu-1-aurae.libvirt-qemu/cgroup.procs': Operation not supported```

[krisnova]

I know @MalteJ and @Vincinator had worked on this originally, maybe they have some insights. I can try to replicate on my end as well.

Are you trying to run a VM hypervisor... inside a container..?

[jesse-peters]

The goal of this PR is to get to a point I can build aurae and run it inside of a VM for testing on my Mac M1. I've gone down a few paths here trying to find the best way to do it. I may be wildly off base though, some of this is uncharted territory for me.

At this point I'm probably pursuing it mostly because I'm stubborn and want to get it to work. I certainly appreciate any help, but also understand that running the project on an M1 like this probably isn't a major hangup for most folks here.

• Build on the mac itself. I hit an issue there:

  Building procfs on an for a unsupported platform. Currently only linux and android are supported
  (Your current target_os is macos)

  • So I set up the makefiles to run the build inside a debian container on my mac, without emulating an environment for docker (--platform linux/amd64). There are more modifications needed to make sure it doesn't change the existing process though.
• In order to make the kernel I had to add support for my architecture by modifying the makefiles again, and adding an additional kernel config.
  • Once I had that, I started trying to get the make virsh-start virsh-console virsh-stop commands working, but hit some issues - again due to my mac.
  • Next I tried creating a docker container to run libvrt inside of a debian container (yea.... I know its pretty hacky). I was pretty close I think, but kept hitting issues still. Those are the ones that prompted this PR and the questions in discord. I think the issues were because it was inside of docker mostly.
  • Since then, I have been playing with running qemu-system-aarch64 on my mac, trying to use the kernel and ramfs that were built earlier (but without the docker "wrapper").

Hopefully this provides some context to anyone wondering whats going on with this PR.

[jesse-peters]

I'm going to close this PR. I'm not sure how much more work it'll be, and I can re-open it in the future once I get it worked out. I'd rather not leave the PR up for an indeterminate time.