andersonalipio

@semarie sorry for the delay.

@semarie said:

your /var/log/sdn-controller-plugin.log file (on the host) in order to check the parameter passed by XO.
MASTER_sdn-controller-plugin.txt

@semarie said:

output of xe network-param-list uuid=$UUID (for the network concerned) or xe network-list params=all (if uuid is unknown)
uuid ( RO) : 250cec4e-d7af-23c5-be1c-391186bde2f4
name-label ( RW): VLAN VDI INT - 102
name-description ( RW): VLAN Rede VDI Interna VMs
VIF-uuids (SRO): 9f23be5a-a6f5-f64d-e004-4a432aded733; b9f85e54-cfd0-6546-edac-ba1573f00bc5; 16bfa5e3-4022-7c9e-ef43-735599b9b5f2; 418fc7cb-ab9c-23db-8bad-7854cb16cbcb; b9dfc5b9-560e-38ac-941a-f744b0d741d8; af16b830-1d31-c664-d70c-a6d1c7ce3056; 3596ec8a-d0ee-2468-d6ae-16b66c745d03; 181808cf-1c42-ddcb-13b5-3bf5f4483a3f; 0c576952-b1f1-95db-1a7e-fc8f581a46e3; b2b8da93-f07f-32a4-1ae1-ae2eac13da08; 9c96d442-e782-774a-ac98-858fcce36607; f512706b-f1a3-767d-6941-ed0f6c926291; c5f2e0b1-a8d2-4846-521a-54b790d6d849; 82b9789c-cf69-6382-e6cc-95ef67b0ba2e; 967ecb88-a141-cd17-c45f-9f5a779efbca; 7445be42-7b30-7a61-f3a1-6aadb725be6a; aa2e03aa-dc9c-aff3-d8cb-5c652af62958; dd596564-a3b4-e15f-69cf-2af5d128a8c2; 767a2bae-8ff0-45fd-339f-56a955ed1ada; e5c85ad8-4bc1-f8b6-6c31-ca6f48604920; d30dfed6-ba5c-04f8-bbc6-ddc18414737e; cddb92fd-da90-cce1-620c-c31469dccada; da4421fa-0bb5-525b-544e-f03e6fbce04b; 947932f8-4bf6-204f-d112-0b251ac4abae; b5bdddd6-2908-ec1f-4a2d-a2b12cf36ee8; 0601ff52-51c9-72de-7dba-071d016473fd; 49739db0-2055-9a4b-fe22-027f5b7ceac0; e0e7fa88-1d3c-05f3-1cc9-cf6e08aa8294; 82b7a17e-2164-caec-90ba-2640a737897b; bda96371-0222-2919-d128-94f1e118a411; ca3e3dee-40da-b1c3-77ce-9b4640511151; 8241bab2-ab2a-228e-24ca-914a80d1cacc
PIF-uuids (SRO): fef83dfe-5a02-50b6-12a3-0fed1189acaf; de48ed20-e0d2-ab4d-c2b3-7857110e0f6a; 4014506f-75ff-800b-3bde-d49196f39bf7; 29d6c11e-d149-b54a-6cf5-d41af778cd50; c064f9cb-018d-d5a3-12d1-29a6050118d8; 4dffbd1d-2bcb-1d85-b029-1bc4366ef4ad; f81b260a-88ed-2c7f-b87d-ea1bcb830e69; 5deeb719-799b-2752-a1dd-5788b94c0f21; 5d7761a3-8ebd-fb60-8568-6a7129bef180; 74943f3a-bacc-bfb3-3efa-b66423fa0604; c4b64326-3c78-c7ac-0535-22aa0e2b0e62; d2f68f7a-a32a-f84d-9162-71f18d7b35ec
MTU ( RW): 1500
bridge ( RO): xapi3
managed ( RO): true
other-config (MRW): xo:sdn-controller:of-rules: ["{"allow":true,"protocol":"IP","ipRange":"172.22.146.126/32","direction":"from/to","cookie":"0xd3d2533ed26a8151"}","{"allow":true,"protocol":"IP","ipRange":"172.22.146.119/32","direction":"from/to","cookie":"0xa9b47fab93762ad1"}","{"allow":true,"protocol":"IP","ipRange":"172.22.146.120/30","direction":"from/to","cookie":"0x20b7928056a3e208"}","{"allow":true,"protocol":"IP","ipRange":"172.22.146.124/32","direction":"from/to","cookie":"0x67d0c4dc2d9fd8a9"}","{"allow":false,"protocol":"IP","ipRange":"0.0.0.0/0","direction":"from/to","cookie":"0xd191b1374733bc1a"}"]; automatic: false
blobs ( RO):
tags (SRW):
default-locking-mode ( RW): unlocked
purpose (SRW):

@semarie said:

output of xe pool-list params=other-config (for xo:sdn-controller:* elements)
xo:sdn-controller:of-method: xapi-plugin; xo:sdn-controller:of-format: xapi-plugin; auto_poweron: true;

@semarie said:

output of xe vif-list params=uuid,network-uuid,other-config (for xo:sdn-controller:* elements)

this output is pointless because our current rules are on network, not on VIF anymore.

@bleader XOA 6.7 premium (updated last friday - latest channel), as all updates on XCP-ng 8.3 from latests available updates on same day (not testing, ci or other repos)

@semarie I'll do it as soon as I get access to the server, hopefully tomorrow.

Ran into some issues with sdncontroller.py (XCP-ng 8.3 and xcp-ng-xapi-plugins-1.16.0-1) when creating traffic rules on VLAN VIFs (and networks) in XOA — same error on both Premium and Community. The problem turned out to be a line feed sent by XOA.

On line 236 of sdncontroller.py, I added a fix that solved the problem, and it now works perfectly managing traffic rules in XO on VLAN networks:

def update_args_from_ovs(args):
    # FIX: strip line feed (\n \X0a) sent by Xen Orchestra
    args["bridge"] = str(args["bridge"]).strip()
    # get parent...

I had another problem when adding rules on networks that weren't connected on all hosts, because those hosts didn't have VMs running on that network (default). Manually connecting them worked fine.

I think it's more of an XO error than xapi plugin, but worked ok in my case.

Thanks for the great work!

@Swen Thanks bud! It did the trick!

I did the interface modify commands on master only, it changed all hosts online with running guest vms and no downtime at all!

Hello all,

I got it working just fine so far on all lab tests, but one thing a couldn't find in here or other post related to using a dedicated storage network other then managemente network. Can it be modified? In this lab, we have 2 hosts with 2 network cards each, one for mgmt and vm external traffic, and the second should be exclusive for storage, since is way faster.

@rjt said in XS 7.0 to XCP-ng 8 live migration error VM.migrate_send with the incorrect number of parameters:

Do you have any shared storage somewhere on your LAN to use?
A three GB thumbdrive shared from another machine is big enough for this VM.

I have a NFS storage that's seen by all servers, but when migrating using this storage gives me the same error.

Found the correct xe command but got the same error

[root@srv-vm02 ~]# xe vm-migrate remote-master=172.16.254.2 remote-username=root remote-password=xxxxxx vm=VM_MEPCAFI host=srv-vm01 live=true vdi:75400759-8829-48a0-b4ee-d8dd56a0facc=652efd1c-e37e-2f33-4ed3-3deffb251ed6
Performing a Storage XenMotion migration. Your VM's VDIs will be migrated with the VM.
Will migrate to remote host: srv-vm01, using remote network: Pool-wide network associated with eth0. Here is the VDI mapping:
VDI 75400759-8829-48a0-b4ee-d8dd56a0facc -> SR 652efd1c-e37e-2f33-4ed3-3deffb251ed6
You tried to call a method with the incorrect number of parameters. The fully-qualified method name that you used, and the number of received and expected parameters are returned.
method: VM.migrate_send
expected: 6
received: 7

Don't really know what to do next...

@andersonalipio said in XS 7.0 to XCP-ng 8 live migration error VM.migrate_send with the incorrect number of parameters:

@olivierlambert said in XS 7.0 to XCP-ng 8 live migration error VM.migrate_send with the incorrect number of parameters:

Can you try with Xen Orchestra? And/or xe CLI?

Would the command line be something like this?

xe vm-migrate remote-master=x.x.x.x remote-username=root remote-password=******* vm=vm-name live=true force=true

If yes, should it be executed from the master or the server where the VM lies?

I need to live migrate a VM from slave 1 (XS 7.0) to the upgraded master (XCP 8.0)

That's not it...

I'm trying to find the correct parameters, because in my case, I need to migrate a VM from slave1 with VDI in slave1 LOCAL SR to the master and the VM's VDI to master's LOCAL SR.

I've found this but I'm confused about wich uuid and wich SR should I use, current or new....

xe vm-migrate uuid=[vm's uuid?] host=master live=true host-uuid=[old or new host uuid?] vdi:72ce69ce-6162-4d9d-a82b-1020ba8eeaf0=62cb502e-ffc0-79c2-3b73-9888d9dad60b

@olivierlambert said in XS 7.0 to XCP-ng 8 live migration error VM.migrate_send with the incorrect number of parameters:

Can you try with Xen Orchestra? And/or xe CLI?

Would the command line be something like this?

xe vm-migrate remote-master=x.x.x.x remote-username=root remote-password=******* vm=vm-name live=true force=true

If yes, should it be executed from the master or the server where the VM lies?

I need to live migrate a VM from slave 1 (XS 7.0) to the upgraded master (XCP 8.0)