@olivierlambert Understood! I forgot how incredibly easy it is to just deploy another Xen Orchestra VM... I feel like an idiot and wish I didn't dump so many hours into recovering the previous XOA VM but atleast I can move forward now!
TechGrips
@TechGrips
The open-source world is a hub of innovation, consistently surpassing proprietary alternatives over time. At Tech Grips, we utilize this rapidly growing branch of IT for dependable solutions that cater to each client's specific requirements. Our dedication to open-source technology demonstrates our conviction that everyone should have access to effective and affordable IT solutions without restrictions.
In a time when there is an abundance of computing power & software tools, we notice a chance to revolutionize the standard IT managed-services sector.
Come and embrace a future where businesses are empowered by technology to succeed on their own terms. Experience software freedom through open-source, customizable IT solutions with Tech Grips, helping you cut costs and have more control over your digital strategy.
Let us get a grip on your tech today!
Latest posts made by TechGrips
-
RE: Changing Hosts and XOA IP
-
RE: Changing Hosts and XOA IP
@olivierlambert Moreover, what's weird is on the new network I've made to try and access the XOA VM again, it does indeed show up on my firewall's ARP table, albeit with an incomplete MAC, which I've never seen that before. It also doesn't return pings and of course I can't connect to its web app.
-
RE: Changing Hosts and XOA IP
Hi Olivier, super appreciative of your attention to this!
@olivierlambert said in Changing Hosts and XOA IP:
Hi,
In XCP-ng, you do not change a VM IP address via the hypervisor. This change has to be done inside the VM itself, or via an external mechanism (xenstor, Cloudinit and such).
Are you saying this in terms of what is proper and "the right way to do it" so to speak? Or are you saying that what I'm trying to do is impossible?
This is the context for why I NEED to be able to change the XOA IP from the hypervisor...
- This particular hypervisor was brought into my previous employer to assist with a lack of compute during a big modernization & migration project. XCP-ng was setup from scratch on this server on that company's network. It was then shutdown and shelved when the extra compute was no longer needed.
- Fast-forward a few years later, I've started my own company and need to incorporate this box into a private cloud I've been building. I would like to access various resources on this box, however, all the virtual networking is configured onto a network which no longer exists now. I don't want to factory-wipe/reinstall because then I'll lose a ton of hours of work across its VMs.
- If I can just access XOA again, I can fix all the other VM networks.
- I've tried to create a route to the XOA VM from my firewall but just can't get XOA to become accessible again from the new network.
This is why I believe resetting XOA's network from the hypervisor (if possible) is the most optimal approach to access XOA again.
-
RE: Changing Hosts and XOA IP
@Nick-085 Thanks for the suggestion, I'm not real familiar with this stuff but this method seems to make sense.
However after trying it out, the XOA VM still retains the same inaccessible IP address as before. I'm unsure if I'm doing this the right way though, I performed the following:
vif-create
new virtual interfacevif-plug
attach the newly created VIF (device 1) onto XOA VMvif-unplug
detach the existing VIF (device 0) from XOA VM- wondering how the newly created VIF has any network config, I tried to give it some with the
vif-configure-ipv4
...and still same annoying ambiguous "You attempted an operation on a VM which lacks the feature" error... Tried to reboot the XOA VM to no differences. I don't understand why this isn't more intuitive.
Did I follow the right syntax and order of operations here?
-
RE: Changing Hosts and XOA IP
Hi, I stumbled upon this article and others a few weeks ago but am still really struggling with this...
It appears OP asked about changing the IP address of his hosts as well as his XOA VM. This thread only answers changing the host's management IP! I've looked everywhere possible around my host's physical Management Console and it doesn't allow you to change a VM's IP config from there.
So part of OP's (as well as my own) question still stands: What's the easiest and most direct way to change the IP address of the XOA VM if you've lost access to Xen Orchestra?
Per the CLI docs, on the command shell I've tried using
xe vif-configure-ipv4
against my XOA VM's VIF but I keep getting a super annoying "You attempted an operation on a VM which lacks the feature"... This occurs regardless if the XOA VM is running or shutdown.
So what's the method to the madness here? Any assistance is greatly appreciated.