LACP is not Balance-SLB but Balance-TCP.

Balance-SLB is Source Load Balanced and happens via mac addresses. So nothing needs to be configured on the switch side. 

To add to that, When you configure LACP inside Nutanix AHV, the only possible load balancing mode you can use is balance-tcp. It is not possible to use slb with LACP.

Nutanix AHV using balance-tcp with LACP load balances outbound traffic using the source and destination IP addresses, and source and destination ports. This matches the Cisco etherchannel load balancing method of
switch(config)# port-channel load-balance ethernet source-dest-port

thank you @bbbburns  @JeroenTielen  for the answers. now i know that balance slb is not LACP and wont help me to integrate to 2x 1G links and become 2G link

balance-slb has multicast traffic caveats , With balance-slb, the virtual switch forwards inbound multicast traffic on only one active adapter and discards multicast traffic from other adapters. Physical switches with IGMP snooping may discard traffic to the active adapter and only send it to the backup adapters. This mismatch leads to unpredictable multicast traffic behavior. Disable IGMP snooping or configure static IGMP groups for all switch ports connected to Nutanix servers using balance-slb.

Each VM NIC uses only one bond member interface at a time, but a hashing algorithm distributes multiple VM NICs (multiple source MAC addresses) across bond member interfaces. As a result, it's possible for a Nutanix AHV node with two 10 GbE interfaces to use up to 20 Gbps of network throughput, while an individual VM might have a maximum throughput of 10 Gbps, the speed of a single physical interface.

https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2071-AHV-Networking:balance-slb.html