The short answer is, if you want a single VM to use more than one single link, then you need to use a link aggregate (port channel). The switches (or switch) need to be configured with a static link aggregate i.e., without LACP, and the ESX host needs to be configured to use the route based on IP hash load balancing.
The slightly longer answer...
As per the IEEE standard, a link aggregate (port-channel) can only exist between two physical devices. While this can be used to add bandwidth, it does of course introduce a single point of failure.
Cisco vPC is a proprietary mechanism that allows a single downstream device to have two connections across two physical switches, but see those two switches as a single entity.
As far as the Nexus switches are concerned the MAC addresses of all the VMs on the host are associated with a single link i.e., the port-channel. The switch then decides, based on the port-channel load balancing algorithm in use, which physical link should be used. If the switches are configured with a load-balancing algorithm that looks at source/destination IP and port numbers (configured with command port-channel load-balance ethernet source-dest-port), a single VM can utilise more than one link of the port-channel. This of course is for traffic flowing from the network to the host.
For traffic from the ESX hosts, a single VM will only use more than one physical link if the ESX load balancing is set to route-based on IP hash. This is what enables the link aggregation on the ESX. Take a look at Part 3 of Ken Cline's Great vSwitch debate for details of the load balancing options available on the ESX host.
Regards