-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add QEMU Guest Agent #6152
base: master
Are you sure you want to change the base?
add QEMU Guest Agent #6152
Conversation
- initial version, builds for arch-x64-7.1 only
@sgelineau17 can you please try, whether this works with proxmox? |
this qemu-ga build is not work on my DSM vm. qemu-ga is installed on this vm: qemu-ga command output:
|
@tofuHero did you try to add the missing folder after creating the run folder, I get a different error (not running under qemu/proxmox):
|
i've done that and also got this error. |
@r0bb10 I did some analysis on the qemu-ga package of https://spk7.imnks.com/
We could clone the functions of the implementation by imnks.com/jim.plus, but I doubt that it will be more stable. |
- must run as root, so manual action is required for installation an upgrade - ensure /dev/virtio-ports/org.qemu.guest_agent.0 exists before service starts
@tofuHero, @r0bb10 I did some progress. I guess when not running virtual dsm, the kernel module Can you please check with: on my virtual dsm it shows:
|
mm installed the latest version Build #6811, done the run-as root, package starts and no error seem obvious
and
log file
|
Hi @hgy59 I'm a xpenology user and also waiting for this package from SynoCommunity, I can see there is pull request from you but it has not been merged yet. may I know when the package will be available in the repository? Thanks for you effort for this package. |
I'm in same the case, I waiting this package from SynoCommunity too. |
@xutongtongxue, @sgelineau17 can one confirm that this package works as expected? |
for me still not working. |
with the latest push still shows same error:
|
@hgy59 Hi, I just downloaded the latest x64-7.1 artifact from the Actions and tried to install to my synology VM, but the installation failed. My DSM version is 7.2.1-69057, I want to know if this package supports DSM 7.2.1-69057, so I can help test this package. Thanks. |
@hgy59 still no go with 9.1.2
|
Hello, |
|
still no go adding serial0 (i already had serial2 enabled, adding 0 suggested in the link did do nothing :( ) any check i can do to help debugging? |
The latest package in the skp7 repository requires the serial console to be removed from PVE, have you tried removing the serial console to see if the package works? Thanks. |
@hgy59 @r0bb10 I tried installing the package(change the privilege and start a service), the PVE now can get the IP from the qemu-ga and the shutdown command from PVE also works fine. Thanks. When try to click shutdown from PVE web console, the result of 'tail -f /volume1/@appdata/qemu-ga/qemu-ga.log' are as follows. Stoping the qemu-ga service and run manmually. Below is my env. |
@xutongtongxue we are using different enviroments, you are on xpenology i'm on virtualdsm. @hgy59 i see on the latest screenshots posted that qemu-ga shows the docker container stopping via serial0, i can see this happen on serial2 on my side on virtualdsm, is it possible to set qemu-ga to listen to serial2? |
@sgelineau17 @tofuHero please try this, I have installed the this package and it works fine for me. Below is my env. Thanks.
|
@r0bb10 Sorry I didn't know your issue or the backaground of issue. I just check the flows again and still did't get your issue. Can you explain your requirements and problems again. Perhaps, I can help you. |
Just wanted to pop in to comment that I was able to get this to work with a newly installed xpenology system running dsm 7.2.2 under proxmox. Had already installed the one showing in the repository, but followed the steps posted by @hgy59 above. It overwrote/replaced the one I had already installed and all is working well! |
@r0bb10, @hgy59, |
yeah this is what i thought but i did not thinker with the start script to set a different listening port, i set it up now like you suggested and it finally works. i had to edit line 26 in not that it really matters since it already worked with acpi commands but it's nice to have the guest agent fully work. |
@grimandreas, @r0bb10 shall we introduce a wizard variable to define the virtual port (default Or shall we try to autodetect the port at service start? |
the problem is only present on a virtualdsm instance on proxmox, wich is probably a very niece scenario since not many use virtualdsm on non-synology hardware.. and the vm has to be setup correctly, including the snippet companion. but i agree that could be very handy to have an advanced option in the wizard to redirect to port2 (with a big warning asking if the package is being installed on a virtualdsm and correctly configured).. i guess autodetect would not work in a scenario where the vm is virtualdsm but no serial2 has been setup. tbh with the package permission faq and the wizard would bring the agent to a stable release and should be also available in the repo, maybe some more testing is needed but i think it's ready. |
In vanilla Virtual DSM running on DSM hardware /dev/vport1p1 also exists. As I told previously, it's used for retriving from host information about license, s/n, cpu information, etc. In real DSM hardware first serial port exists too.
I don't know if we could really autodetect the port at service start. Wizard variable could be optimal in this case (with default port value |
Hello, |
It is still here (available for 90 days, use the latest workflow) |
Description
Fixes #6019
Checklist
all-supported
completed successfullyType of change