In any case, on the CR Vm they are the good numbers of Vif, and if there is a match between NIC and VIF between Prod server and CR server, the CR VM seem to have the right ones

Yes, for exemple on a "prod" server I have a VM like this:

PROD SERVER ( with 3 network interfaces)
NIC1: cabled on cisco switch port with VLAN1 and Network name associated ont this NIC: VLAN1
NIC2: cabled on cisco switch port with VLAN2 and Network name associated ont this NIC: VLAN2
NIC3: cabled on cisco swtch port with VLAN3 and Network name associated ont this NIC: VLAN3

VM1 on PROD SERVER:
network1 : VLAN1
network2 : VLAN2
network3 : VLAN3

and on the CR SERVER:

CR SERVER ( with 2 network interfaces)
NIC1: cabled on cisco switch port with VLAN1 and Network name associated ont this NIC: VLAN1
NIC2: cabled on cisco switch port with TRUNK and 2 Networks name associated on the NIC: VLAN2 (tagged vlan2) and VLAN3 (tagged vlan3)

The CR of VM1 on the CR SERVER becomes:

VM1-CR:
network1: VLAN1 (good)
network2: VLAN1 (bad)
network3: VLAN1 (bad)

The VLAN1 associated as the fist network have the same name on the same number of NIC and it's OK
For the rest, the name of the network is the same, but not on the same NIC number, ans it seems to be the problem ?

I was sure that the important thing was the name of the network, but in fact it is rather the NIC number I think

Hi,

I have already the same problems, see pictures of a VM with some VIFs with differents VLAN, on a xcp-ng 8.0 hosts with separated NICS:

And now a picture of the CR of this VM on another XCP-Ng host who just have 2 NIC with a vlan 110 and the second NIC is a trunk with several external VLAN added, same as the first xcp-ng host.

The CR doesn't take automatiquly the good VLAN but they exist via the TRUNK NIC

For me the solution is to have identicals NIC ont the both servers. But with the same name of VLAN, the CR could have the good VLAN no ?

More simple to manage

Hi

I had exatly the same problem when I upgrade one of my four server from xenserver 7.1 to xcp-ng 8.0, one backup failed with error: job already running and the other finish normaly later!

I upgrade Xo from 5.51 to 5.54 and it's Ok for this problem BUT I have a new problem, the cold backup to NFS and the Continuous replication to a Xcp-ng 8 server are REALLY slow !! One exemple:

Start time: Thursday, December 19th 2019, 7:20:00 am

End time: Thursday, December 19th 2019, 7:58:54 am

Duration: 39 minutes

Snapshot

Start time: Thursday, December 19th 2019, 7:20:00 am
End time: Thursday, December 19th 2019, 7:20:05 am
Duration: a few seconds

SRs

Local storage (a70a93c4-4951-9bec-54ab-d45bb5039b44) ✔
    Start time: Thursday, December 19th 2019, 7:20:05 am
    End time: Thursday, December 19th 2019, 7:58:52 am
    Duration: 39 minutes
    transfer ✔
        Start time: Thursday, December 19th 2019, 7:20:06 am
        End time: Thursday, December 19th 2019, 7:58:50 am
        Duration: 39 minutes
        Size: 1.34 GiB
        Speed: 605.55 KiB/s

I try to upgrade debian OS, upgrade VM (4cpus 3Go ram) but same problem for the moment

Thanks in advance

Edit: I do a manual test by copy an iso of 2G locally on the virtual machine Xen orchestra, to the same connected NFS for backup, and the performance is normal, 10 seconds for 2Go, it seems to be a problem with Xen orchestra system backup?

In any case, on the CR Vm they are the good numbers of Vif, and if there is a match between NIC and VIF between Prod server and CR server, the CR VM seem to have the right ones

Sorry it's just an example effectively it's not possible to tagg VLAN1, bad example, on my real servers I have a VLAN 1 but not trunked

Yes, for exemple on a "prod" server I have a VM like this:

PROD SERVER ( with 3 network interfaces)
NIC1: cabled on cisco switch port with VLAN1 and Network name associated ont this NIC: VLAN1
NIC2: cabled on cisco switch port with VLAN2 and Network name associated ont this NIC: VLAN2
NIC3: cabled on cisco swtch port with VLAN3 and Network name associated ont this NIC: VLAN3

VM1 on PROD SERVER:
network1 : VLAN1
network2 : VLAN2
network3 : VLAN3

and on the CR SERVER:

CR SERVER ( with 2 network interfaces)
NIC1: cabled on cisco switch port with VLAN1 and Network name associated ont this NIC: VLAN1
NIC2: cabled on cisco switch port with TRUNK and 2 Networks name associated on the NIC: VLAN2 (tagged vlan2) and VLAN3 (tagged vlan3)

The CR of VM1 on the CR SERVER becomes:

VM1-CR:
network1: VLAN1 (good)
network2: VLAN1 (bad)
network3: VLAN1 (bad)

The VLAN1 associated as the fist network have the same name on the same number of NIC and it's OK
For the rest, the name of the network is the same, but not on the same NIC number, ans it seems to be the problem ?

I was sure that the important thing was the name of the network, but in fact it is rather the NIC number I think

HI !

I just see a problem with the CR between two servers XCP-Ng 8.0.

I do CR ( xith XO 5.50.1) for several VMs, but the CR for Vms with more than one network interface hasn't got the good Vif on all Vif.

For me, the most important with the vif during DR/CR, is the name of the vif no? If the Vif name on a VM is the same than an other XCP-Ng server, the DR/CR Vm take the good Vif.

On XCP-Ng 8 it seems to be the number of the NIC !?

On my old xenserver 7.1, all the NIC/Vif are exactly the same.... It may have already been in relation to the NIC number, and that does not help me

On the CR server I don't have the same number of NIC, and I create Vif VLAN with a network interface trunked on a cisco....

Ok thank you very much, it works! I think I forget to install package but no ....

Have a good day !

Hi, it's not me who has created those links, it's created automatically after XO install from source. On previous versions, I have to do this but now those links are already done.

I don't have "node_modules" in /usr/local/lib/ , just python2.7 and python3.5, maybe I forget to install a package?

But I have /usr/lib/node_modules, with npm folder and an other "node_modules" folder inside with 349 folders !

(10:20:46|root@xo-xcp-ng**:/usr/lib/node_modules/npm** #) l
total 96K
-rw-r--r-- 1 root root 959 août 2 2018 appveyor.yml
-rw-r--r-- 1 root root 23K août 15 20:26 AUTHORS
drwxr-xr-x 3 root root 4,0K oct. 9 14:51 bin/
-rwxr-xr-x 1 root root 521 août 2 2018 configure
drwxr-xr-x 4 root root 4,0K oct. 9 14:51 html/
drwxr-xr-x 8 root root 4,0K oct. 9 14:51 lib/
-rw-r--r-- 1 root root 3,2K août 16 2018 .mailmap
-rw-r--r-- 1 root root 156 août 2 2018 make.bat
-rw-r--r-- 1 root root 5,5K août 16 2018 Makefile
drwxr-xr-x 5 root root 4,0K oct. 9 14:51 man/
drwxr-xr-x 351 root root 12K oct. 9 14:51 node_modules/
-rw-r--r-- 1 root root 324 août 15 20:26 .npmignore
-rw-rw-r-- 1 root root 7,3K août 15 20:26 package.json
drwxr-xr-x 2 root root 4,0K oct. 9 14:51 scripts/
-rw-r--r-- 1 root root 1,2K août 15 20:26 .travis.yml
(10:20:47|root@xo-xcp-ng:/usr/lib/node_modules/npm #) cd node_modules/
Display all 349 possibilities? (y or n)

@Biggen said in XO from source and plugins installation:

Are plugins even available for the community XO edition?

Hi and thank you for your response.

Yes, before plugins are available, I have this two plugins activate on many old version of Xo from source. Just have to install the plugin(s) and make a link to activate it with a xo-server restart.
Maybe on this new version, it has changed?

Hi all !

I install the last XO (5.50.1 and xo-web 5.50.2) from source, and I have a problem to install/activate plugins on it.
No plugins are available, but on the server (debian9) I see plugins I want, in ~/xen-orchestra/_modules:

rwxrwxrwx 1 root root 27 oct. 9 14:55 xo-acl-resolver -> ../packages/xo-acl-resolver
lrwxrwxrwx 1 root root 18 oct. 9 14:55 xo-cli -> ../packages/xo-cli
lrwxrwxrwx 1 root root 25 oct. 9 14:55 xo-collection -> ../packages/xo-collection
lrwxrwxrwx 1 root root 21 oct. 9 14:55 xo-common -> ../packages/xo-common
lrwxrwxrwx 1 root root 33 oct. 9 14:55 xo-import-servers-csv -> ../packages/xo-import-servers-csv
drwxr-xr-x 2 root root 4,0K oct. 9 14:55 xok/
lrwxrwxrwx 1 root root 18 oct. 9 14:55 xo-lib -> ../packages/xo-lib
lrwxrwxrwx 1 root root 28 oct. 9 14:55 xo-remote-parser -> ../packages/xo-remote-parser
lrwxrwxrwx 1 root root 21 oct. 9 14:55 xo-server -> ../packages/xo-server
lrwxrwxrwx 1 root root 33 oct. 9 14:55 xo-server-auth-github -> ../packages/xo-server-auth-github
lrwxrwxrwx 1 root root 33 oct. 9 14:55 xo-server-auth-google -> ../packages/xo-server-auth-google
lrwxrwxrwx 1 root root 31 oct. 9 14:55 xo-server-auth-ldap -> ../packages/xo-server-auth-ldap
lrwxrwxrwx 1 root root 31 oct. 9 14:55 xo-server-auth-saml -> ../packages/xo-server-auth-saml
lrwxrwxrwx 1 root root 36 oct. 9 14:55 xo-server-backup-reports -> ../packages/xo-server-backup-reports
lrwxrwxrwx 1 root root 27 oct. 9 14:55 xo-server-cloud -> ../packages/xo-server-cloud
lrwxrwxrwx 1 root root 35 oct. 9 14:55 xo-server-load-balancer -> ../packages/xo-server-load-balancer
lrwxrwxrwx 1 root root 32 oct. 9 14:55 xo-server-perf-alert -> ../packages/xo-server-perf-alert
lrwxrwxrwx 1 root root 36 oct. 9 14:55 xo-server-sdn-controller -> ../packages/xo-server-sdn-controller
lrwxrwxrwx 1 root root 26 oct. 9 14:55 xo-server-test -> ../packages/xo-server-test
lrwxrwxrwx 1 root root 33 oct. 9 14:55 xo-server-test-plugin -> ../packages/xo-server-test-plugin
lrwxrwxrwx 1 root root 37 oct. 9 14:55 xo-server-transport-email -> ../packages/xo-server-transport-email
lrwxrwxrwx 1 root root 38 oct. 9 14:55 xo-server-transport-nagios -> ../packages/xo-server-transport-nagios
lrwxrwxrwx 1 root root 37 oct. 9 14:55 xo-server-transport-slack -> ../packages/xo-server-transport-slack
lrwxrwxrwx 1 root root 36 oct. 9 14:55 xo-server-transport-xmpp -> ../packages/xo-server-transport-xmpp
lrwxrwxrwx 1 root root 34 oct. 9 14:55 xo-server-usage-report -> ../packages/xo-server-usage-report
lrwxrwxrwx 1 root root 26 oct. 9 14:55 xo-vmdk-to-vhd -> ../packages/xo-vmdk-to-vhd

I just want for the moment: xo-server-transport-email and xo-backup-reports. The links are already done, and I don't find how can install/activate it.

Thanks in advance and have a good day !