@olivierlambert Hi, I really appreciate your time!

I'm using a US QWERTY keyboard on a 2-year old MSI laptop running Windows 11. I first noticed this issue a few weeks ago when I first deployed xo-server v5.151.0 / xo-web v5.152.1 built from your sources.

A little bit ago I actually tried this in Brave browser and using shift worked perfectly fine. Then I tried it in vanilla FireFox and it worked fine there too...

I daily drive LibreWolf, a security/privacy version of FireFox and I usually don't ever have issues with it but I'm gonna chalk this keyboard thing up to something related to that.

Sorry about that!

@olivierlambert Hi, I really appreciate your time!

I'm using a US QWERTY keyboard on a 2-year old MSI laptop running Windows 11. I first noticed this issue a few weeks ago when I first deployed xo-server v5.151.0 / xo-web v5.152.1 built from your sources.

A little bit ago I actually tried this in Brave browser and using shift worked perfectly fine. Then I tried it in vanilla FireFox and it worked fine there too...

I daily drive LibreWolf, a security/privacy version of FireFox and I usually don't ever have issues with it but I'm gonna chalk this keyboard thing up to something related to that.

Sorry about that!

I have this exact same problem, using LibreWolf, which is basically FireFox... It's preventing me from logging into a break-glass account to fix an issue.

I just created a new post for this issue here:
https://xcp-ng.org/forum/topic/9629/keyboard-support-xo-vm-console

Hello,

I have a pretty major issue causing me some stress...

It seems the keyboard support for the XO-Web VM console is lacking functionality. Or maybe this is an issue local to me, such as maybe my web browser?

I'm unable to type any characters that requires a shift key... This means no capital letters or special characters.

If you use 20-character randomized passwords similar to the one in the below screenshot's text copy field, but have accidentally broke your VM's network preventing any SSH connections for the time being, how then are you supposed to use the VM console to access your VM? This seems like it should be simple and straightforward but I haven't been able to find anything in the documentation about this. I can't be the only one who has had this issue??

Moreover, what's the deal with this text copy field anyway? How's it supposed to work? I do indeed have the Management agent 7.30.0-12 installed onto this particular VM, but clicks also don't seem to emulate into the VM console.

What is the direction on what admins in this situation are supposed to do here?? Any suggestions here are hugely recommended...

Thanks very much!
Josh

@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!

@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.

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.

@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:

1. vif-create new virtual interface
2. vif-plug attach the newly created VIF (device 1) onto XOA VM
3. vif-unplug detach the existing VIF (device 0) from XOA VM
4. 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?

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.