Hello everyone.
I have a question about a package where I'm not sure how to do it.
It's about the Qemu guest agent.
I would like to create it as an addon and have been trying for a few days without success.
Whenever I want to create the package via the Ipfire build environment, there is nothing in the associated log after a successful run.
I also think that I now figured out what it could be.
The problem is that the Qemu source files are already available in the build system,
which also includes qemu-ga, since the Qemu package is created with it, which means that all the necessary files have already been created.
Since qemu-ga should not be included in the final add-on according to /config/rootfiles/packages/qemu,
it is in the build system but in the end it is not accessible to the user.
I wanted to create qemu-ga as a separate package, virtualize the Ipfire for users like me,
but currently don't know how, since the source files from the lfs are already available for Qemu.
If I use my own source files, which I would like to do because of the newer version,
those from the Qemuaddon will be overwritten by the newer ones in the build system.
I myself have the qemu-ga running on the Ipfire without any problems because I created it myself
using the ./make.sh shell and put the files in the right place in the system myself.
The only thing I can't do is use the build system so that others can benefit from it.
For example, can you use /lfs/qemu to create 2 add-ons?
Or do I have to create a separate /lfs/qemu-ga just without a build routine and then write the required files into /config/rootfiles/packages/qemu-ga myself?
It would be nice if someone had an idea how to do this.
I hope that I have expressed myself reasonably understandably.
Regards
Marcel Follert
Hi Marcel,
I am not familiar with the usage of qemu so maybe I am misunderstanding something but find my comments below.
On 28/11/2021 14:00, smooky@v16.de wrote:
Hello everyone.
I have a question about a package where I'm not sure how to do it.
It's about the Qemu guest agent.
I would like to create it as an addon and have been trying for a few days without success.
Whenever I want to create the package via the Ipfire build environment, there is nothing in the associated log after a successful run.
I also think that I now figured out what it could be.
The problem is that the Qemu source files are already available in the build system,
which also includes qemu-ga, since the Qemu package is created with it, which means that all the necessary files have already been created.
Since qemu-ga should not be included in the final add-on according to /config/rootfiles/packages/qemu,
The qemu-ga entry in the rootfile is not commented out. This means that the qemu-ga binary will be installed into /usr/bin when the qemu add-on is installed.
I just tested this out on my Virtualbox vm test network. I installed the qemu addon and then checked in /usr/bin and qemu-ga was there.
If I have misunderstood something then please let me know.
it is in the build system but in the end it is not accessible to the user.
What made you think the binary was not accessible. Was it missing on your system?
Regards,
Adolf.
I wanted to create qemu-ga as a separate package, virtualize the Ipfire for users like me,
but currently don't know how, since the source files from the lfs are already available for Qemu.
If I use my own source files, which I would like to do because of the newer version,
those from the Qemuaddon will be overwritten by the newer ones in the build system.
I myself have the qemu-ga running on the Ipfire without any problems because I created it myself
using the ./make.sh shell and put the files in the right place in the system myself.
The only thing I can't do is use the build system so that others can benefit from it.
For example, can you use /lfs/qemu to create 2 add-ons?
Or do I have to create a separate /lfs/qemu-ga just without a build routine and then write the required files into /config/rootfiles/packages/qemu-ga myself?
It would be nice if someone had an idea how to do this.
I hope that I have expressed myself reasonably understandably.
Regards
Marcel Follert
Hi Adolf.
Sorry, but I overlooked qemu-ga in the qemu addon.
But since I only need the qemu-ga when I run ipfire virtualized without the complete qemu, it would make a lot of sense to provide this as a separate add-on.
It would not make sense to run a virtualization again on a virtualized system.
How about that?
So to create two addons from one source.
Maybe it would make sense then not to deliver the qemu-ga in the qemu addon because the qemu-ga is only interesting for the virtualized clients but not for the host.
Regards
Marcel
Hi Marcel,
On 28/11/2021 18:01, smooky@v16.de wrote:
Hi Adolf.
Sorry, but I overlooked qemu-ga in the qemu addon.
But since I only need the qemu-ga when I run ipfire virtualized without the complete qemu, it would make a lot of sense to provide this as a separate add-on.
If this is also the case for all users, that the qemu-ga is always needed separately from qemu, then it would make sense to have a separate addon for qemu-ga.
It would not make sense to run a virtualization again on a virtualized system.
How about that?
So to create two addons from one source.
Maybe it would make sense then not to deliver the qemu-ga in the qemu addon because the qemu-ga is only interesting for the virtualized clients but not for the host.
So then my suggestion would be to comment out in the qemu addon rootfile the qemu-ga entry.
Then I would suggest to create an additional lfs called qemu-ga, based on the qemu lfs. Probably remove some the last lines that are creating a wrapper for kvm handling and the udev script. Then create a qemu-ga rootfile, based on the qemu rootfile but with everything commented out except the qemu-ga line and any of the /usr/share/entries that might be required for qemu-ga. That way you have two addons that deal separately with qemu and with qemu-ga.
The above would be how I would try and approach it. You would basically need to give it a go and see if it works or not.
Regards,
Adolf.
Regards
Marcel
-
Adolf Belka -
smooky＠v16.de