Is there a way to proxy the xe command?

Danp

I don't believe that xe will honor the proxy. Have you checked out the alternate installation options?

You could also download the XVA from the website and then import the local copy.

Murf

@Danp Thanks I will try a manual download

Murf

@Danp this worked great except I cant change the static IP of the XOA VM:

[14:39 ost-cla-ucs-b0408-xcpng tmp]# xe vif-list vm-uuid=6ad2ed7b-bb4a-6648-89d3-f27fc1bd72f0
uuid ( RO)            : 5bc599d3-be60-c556-4393-0f69ffaa906f
         vm-uuid ( RO): 6ad2ed7b-bb4a-6648-89d3-f27fc1bd72f0
          device ( RO): 0
    network-uuid ( RO): 2b5c4825-5dc5-9283-cada-a81f965872c4


[14:40 ost-cla-ucs-b0408-xcpng tmp]# xe vif-configure-ipv4 uuid=5bc599d3-be60-c556-4393-0f69ffaa906f mode=static address=172.17.132.200/24 gateway=172.17.132.1
You attempted an operation on a VM which lacks the feature.
vm: 6ad2ed7b-bb4a-6648-89d3-f27fc1bd72f0 (XOA)
[14:40 ost-cla-ucs-b0408-xcpng tmp]#

olivierlambert

Hi! You need to read the XO doc on how to deploy manually and how to change the IP address: https://xen-orchestra.com/docs/xoa.html#manually-deployed

edit: you can also inject the IP config directly with this command, let me ask @julien-f for the detailed command

julien-f

This should work:

xe vm-param-set uuid="$uuid" \
  xenstore-data:vm-data/ip="$ip" \
  xenstore-data:vm-data/netmask="$netmask" \
  xenstore-data:vm-data/gateway="$gateway"

Optionally the default DNS server can be replaced as well:

xe vm-param-set uuid="$uuid" xenstore-data:vm-data/dns="$dns"

Don't forget to restart the XOA afterward!

olivierlambert

Thanks @julien-f !

Murf

@julien-f Yes thanks, this now applied to the VM but after a reboot I cant ping XOA.

I am using a trunked interface on my XCP-NG host, and the management interface is on VLAN 2850 (set in XCP-NG console VLAN setting)

The IP address I am assigning to the XOA VM is also in the same subnet/VLAN.

I tried the following bit it made no difference:
xe vm-param-set uuid="$uuid" xenstore-data:vm-data/vlan="2850"

Murf

Further to this, I believe this should already be working, since the primary PIF has the VLAN built into it already, the VM is attached to the PIF and in the same network, however I cant ping the XOA VM

julien-f

@Murf Only the parameters I wrote in my messages are supported, vlan is not. As you said, the VLAN config is set to the PIF, not inside the VM.

If you cannot ping your XVA, it's likely that one of your parameter is wrong.

Murf

@julien-f Thanks, the VM had been assigned to VIF default with VLAN ID -1, I just had to move it to my Management VLAN VIF
:
xe vif-move