It has been in vyos since I started using it in 2020, but seems to be missing in 1.5-rolling-202412160007 and 202501060800.
Agents were removed in T6942
Thanks! Sorry to bother you. Logic for removal makes sense.
How come?
The qemu-agent is a good addon specially if/when you choose to run VyOS as a VM-guest in a KVM-based environment such as Proxmox among others.
The qemu-agent package is also part of Debian stable:
It seems they didnāt want to include an agent for every possible virtual environment, which I suppose opens it up for requests to support X and Y environments in the future. Although, if I ventured a guess, most of them can probably utilize qemu-ga.
But they do for the custom builds in Azure, Amazon etc - dont they?
Also wasnt there a package system developed for VyOS which VPP is supposed to be using?
Cant that be used to package each VM-guest addon as its own package so you can easily maintain that over system updates?
Or some other wayhave that included so it can get enabled by a config line?
Otherwise if you manually add the qemu-guest-agent after the install it will either break the installation if you point to the Debian repos or you need to manually add more than one package (due to dependencies) and that will vanish next time you update your VyOS to the next VyOS release.
Or at least keep the qemu-guest-agent since KVM is a native part of the Linux kernel.
VM-guest agents arent critical for VyOS but a nice addon to do clean shutdowns/reboots including system maintenance such as fstrim etc from the VM-host when needed.
I mean, if it were up to me I wouldnāt have removed it, but I understand why they did. I figured it was accidentally excluded or something and wanted to point it out if it were, but since it was intentional and they gave a reason why, Iām okay with that since Iām not a paying customer nor a contributing developer. Iāll just have to figure out how to build it and include it myself.
So far though it seems to be anything but trivial, as most of the instructions on this page donāt work: Build VyOS ā VyOS 1.5.x (circinus) documentation
1 Like
What step(s) in the docs did fail when you tried to create an ISO? I periodically build an ISO and it works exactly as mentioned in the docs for including additional packages.
I first tried to do a native build and after fumbling around with it for a bit to get the environment and dependencies setup (I followed vyos-build/docker/Dockerfile at current Ā· vyos/vyos-build Ā· GitHub) I finally gave up and just used Docker. I dislike Docker, but those instructions do work as printed on the instructions page. Perhaps Iāll come back and submit some more documentation for the native build once I get a chance to get it working for me.
1 Like
Go ahead, I have thick skin.
Oh, I see. Iād never āpolluteā my everyday computer with dependencies, docker works very well for tasks like these. I only use docker for compiling whatever I want to compile.
I mean you can install qemu-guest-agent by yourself. It was easy.
And then you have to do it over again next time you update your VyOS - not to mention that it will be tricky for offline environments (as in where internet is not available to just āapt-get installā things).
Its like saying lets remove FRR and every other package since installing it afterwards is easy if you want to do routing with your VyOS?
Sure, qemu-guest-agent is not a core component of VyOS but running VyOS as a VM-guest is a core feature which makes it that IMHO qemu-guest-agent should be put back to the VyOS.
It should be an issue. but we can build a qcow2 image with qemu-guest-agent and cloud-init , each time upgrade the image by deploy new image with cloud-init file. That would be fine.