@jqueiroz said in Second IP for Hosts Interface: I have a situation where I would like to add a second IPv4 address to the management interface of a host. I am installing a host that will be used in another location and I would like to add the address of that location to the management interface before shipping the machine there. Is it possible to do this, or should I continue using the current procedure (making the necessary configurations and change the address shortly before shutting down the machine and packing it for transport)? there is a nuance between secondary IP and secondary MANAGEMENT IP if you have multiple NICS, you could add & configure the destination site IP on it, but it is not flagged management yet. once the server gets on the new site, you could access web ui by this IP address (or SSH) and then either go to web console/xs server or SSH and do the necessary to change management to the good PIF/IP ?

@MajorP93 It's being packaged at the moment. between this and the testing that needs to be done it might take a couple of weeks to be released, but I can't promise anything yet

I just released 0.0.4! Still an alpha, but it's becoming pretty usable - there was over 60 commits of code cleanup, polish and also limited testing of all visible features - pretty much everything that is now visible in the UI should be operational at this point, option pages, properties of hosts, pools, VDIs, configuration of NICs, even bonding and advanced stuff like pool password / secret rotation. All XAPI actions and commands were already ported over from C# variant, so my focus now is only on finishing it into a final usable product. We also have some features that original client doesn't have (such as XenCache explorer)! Next on my to-do is to add all features that are currently missing completely: HA, GPU, PCIe, VM import / export etc. Note: I will not be porting over any licensed or proprietary Citrix stuff. This tool may work with XenServer just fine, but I will not be porting over any of the proprietary features, because I will never use it and I have no way to test it either.

@Tristis-Oris yes it is likely you're using a newer kernel, we likely need to rebuild the agent using a newer version of the netlink crate.