Using Agama remote access with quickemu

[RastislavKish]

I'm trying to use the remote access feature of the latest Agama live ISO with quickemu, a Linux wrapper around QEMU simplifying spinning up and using VMs. I have forwarded a random port (6419) to 443 on the guest in order to access the installer. Usually, I'm afterwards able to access the server running in a VM on localhost:6419 from the guest.

However, not in this case, for some reason. Even though the port is forwarded and should work, I'm unable to connect through the browser or curl, the connection will time out. Possibly a firewall configuration preventing access from the outside network?

Here is the quickemu configuration I use:

#!/usr/bin/quickemu --vm
guest_os="linux"
disk_img="agama/disk.qcow2"
disk_size="100G"
iso="agama/agama-installer.x86_64-16.pre.0.0-openSUSE_PXE-Build16.1.install.iso"
port_forwards=("6419:443")

Any quickemu Agama users out there? Can you use the remote access feature? Is this a bug I should report, or the intended behavior?

[dgdavid]

Hey! 👋

I don’t have experience with that particular QEMU wrapper, but I gave your example a try using the default Agama Live ISO from https://agama-project.github.io/download.

At first, I couldn’t get it to work either, the process seemed to die or something. But then I tried removing the port forwarding and I could boot the system successfully and manage to have the installer running there. That led me to quickemu-project/quickemu#963, in which is suggested that the port must be above 1024. The port in your configuration indeed met that condition, but oddly enough switching it to 8443 made it work and I can access to the installer remotely from my browser 🤯 🤷‍♂️

I’m not very familiar with port forwarding, so I can’t explain why it worked for me after switching to 8443, but I hope this workaround helps you as well until someone else can shed some light on the root cause.

Thanks for keep testing Agama and for introducing me to Quickemu! 🙌

[RastislavKish]

@dgdavid thank's for checking this out!

I have tried the image from your link, and thisone actually works! Previously I had been using the images from the OBS linked by the project readme. Maybe the remote access is disabled there, or something is broken in the current development builds.