damdo/gokrazy-machine

gom (gokrazy-machine)

A lightweight virtual/emulated machine based on qemu, to run and develop for gokrazy.

It supports all major Linux distributions and macOS (both intel and apple silicon (M1,M2,..)) >= 12.x.

pre-install requirements

A hard requirement for this to work is to install qemu >= 7.1.0.

On macOS this can be done directly with:

brew install qemu

On Linux you might need to compile and install qemu with:

curl -SLO https://download.qemu.org/qemu-7.1.0.tar.xz
tar -xf qemu-7.1.0.tar.xz
cd qemu-7.1.0
./configure
make -j $(nproc)
sudo make install

install

go install github.com/damdo/gokrazy-machine/cmd/gom

Check version

gom version

play

The main command is

gom play --full /tmp/disk.img

The gorkazy web UI will be available at a certain address and port depending on how you configured networking.

By default it will be available at http://locahost:PORT, where the port is a randomly assigned to achieve host to guest mapping over NAT.

The NATTED port can be found in the log output of gom, at the top, where the qemu Args are reported before the machine is started, in the -netdev argument.

e.g. if you see: -netdev user,id=net0,hostfwd=tcp::59681-:80,hostfwd=tcp::59682-:443,hostfwd=tcp::59683-:22 then the port mapped to the guest port 80 is 59681, meaning the gokrazy web UI will be at http://locahost:59681.

There are various other modes with which you can run gom, take a look below!

with various disk images

Run machine from a full disk img.

gom play --full /tmp/disk.img

Run machine from different disk parts (boot,root,mbr).

gom play --boot=/tmp/boot.img --root=/tmp/root.img --mbr=/tmp/mbr.img

Run machine from remote OCI artifact (the image won't be kept locally). NOTE: to work with this tool an OCI artifact will need to be constructed in this way.

gom play --arch amd64 --oci <your-oci-amd64-img-url>

# or with an arm64 image

gom play --arch arm64 --oci <your-oci-arm64-img-url>

# if the OCI artifact reference is in a private repository, you can specify credentials
# by using --oci.user and --oci.password
gom play --arch amd64 --oci.user "<youruser>" --oci.password "<yourpassword>" --oci <your-oci-amd64-img-url>

# if the OCI registry is HTTP only you can specify the --oci.plainHTTP=true flag

Run machine from .gaf (Gokrazy Archive Format) disk.

gom play --gaf /tmp/disk.gaf

with various networking setups

By default a gom machine will use a nat network, and will map port 80, 443 and 22 to random ports. These random assigned ports can be found in the log output of gom, at the top, where the qemu Args are reported before the machine is started, in the -netdev argument. e.g. -netdev user,id=net0,hostfwd=tcp::59681-:80,hostfwd=tcp::59682-:443,hostfwd=tcp::59683-:22

But if you need to do specific or extra mappings, or use different modes, here is how you can do it.

Run gom machine in NAT network, with specific port forwarding. Set --net-nat="<outer-port>-:<inner-port>,<outer-port>-:<inner-port>"

gom play ... --net-nat="8181-:80,2222-:22"

[Supported only for macOS] Run gom machine in shared network, with specific IP range. This can be set with --net-shared, a comma separated string where users can set --net-shared="<start-ip,end-ip,subnet-mask>"

gom play ... --net-shared="192.168.70.1,192.168.70.254,255.255.255.0"

with various target architectures

By default gom will use the amd64/x86_64 architecture as the target machine architecture. But arm64 can also be set.

For amd64/x86_64:

gom play --arch="amd64"

For arm64:

gom play --arch="arm64"

with custom memory for the guest VM

By default gom will use 1G of memory for the guest VM. It can be customized with

gom play --memory="2G"

damdo / gokrazy-machine