For VM routing in network virtualization environment one should use Hyper-V NV Gateway.
But as much as I understand, one cannot have 1 subnet (10.0.0.x/24) stretched across physical VLAN and part of Hyper-V network virtualization infrastructure while also be able to route packets to another corporate subnet (10.1.0.x/24).
P2V process from physical world to "network virtualized" VM (with zero reconfiguration) is also impossible, I guess.
Could anyone clarify that?
↧