Replies: 3 comments 2 replies
-
|
I did see this discussion: #426 - but it looks like that was for a Windows system (thus the vmtoolsd path being To test, I have deleted the instance folder and re-ran ghosts. app.log And relevant dotnet systemd logs: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have not used guestInfoVars with the Linux client and looking at the code here its not going to work. This was likely a direct copy over from the Windows project. I will try to take a look at this, but my time to work on ghosts over the next few months is severely limited. The other problem is that increasingly, the future looks like Proxmox (since Broadcom's licensing costs for VMWare seem to be impacting the training and exercise community). I don't know how this functionality is done on Proxmox systems (or other hypervisors in the OSS space). |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I don't mind taking a look at the proxmox options - I've got a decent sized homelab to play around with. I'm not a dotnet developer - but that link should work on linux, provided the code is spawning a process like below: For now, is there a different way to try and set that |
Beta Was this translation helpful? Give feedback.
-
|
If you tell me the command, that makes this change easy. Thanks! |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Hrm, looks like the qemu guest agent doesn't have a 1:1 feature parity with vmtoolsd (which is kind of expected). There is a
Let me look into this a bit more. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to figure out how I can classify multiple different groups of Linux NPCs so that I can target them in machine groups. At first I thought I would try to
I have the following application configuration:
I have set the
guestinfo.groupvalue togrp_1, so I would expect the resultingIdbegrp_1-ghost-01for the machine whose hostname isghost-01.However, It looks like the client doesn't report that value at all. Instead, the machine shows up in the Ghosts UI with a UUID for its
Idand a name of onlyghost-01.I'm noticing that the client is also sending a value of
(none)for theghosts-domain- leading to the auto-created machine groups looking like this:I would love it if I could somehow set that domain and have machine groups auto-populate somehow. But even making it obvious that this
ghost-01belongs to group 1 vs the otherghost-01that belongs to group 2 would be ideal.Beta Was this translation helpful? Give feedback.
All reactions