The purpose of VLANs is to separate network traffic, so what you may want to do is to setup a virtual machine which acts as the router (e.g. pfSense).
In case you ever want to attach that vSwitch to a physical switch, remember that some switches reserve VLAN 1002 trough 1005.
If you have a L3 or "light" L3 switching you can trunk your uplinks and switch ports and create the VLANs on the switch, IP the VLANs and use inter VLAN routing.
(I can make an example of this in Packet Tracer as well if you like.)
Another option (depending on your network architecture) is to configure your gateway for both VLANs ala router on a stick.
I am going to do an example here for ya in Packet Tracer.
Gi0/1.1 192.168.50.1 VLAN 50
Gi0/1.2 192.168.51.1 VLAN 51
Switch will represent quasi host/switch.
The uplink is simply set to trunk all. In production set to trunk only required VLANs.
On the switch your PG's will be represented by individual ports.
Fa0/1 is VLAN 50
Fa02 is VLAN 51
Now each server in the private VLAN / PG's will be shown as PC's.
PC 1 is 192.168.50.2
PC 2 is 192.168.51.2
See screen shot. Both PC's (servers) can ping each other in the separate VLAN's and simulated port groups.
Also including Packet Tracer File.------
Don't forget to mark posts as helpful or correct if they deserve it!
Bring in the switch to make there 2 subnet to ping each other and let us know on what are the components u r using to do so.
Confused, surely you can't route between those subnets without a L3 device?
subnet 192.168.10.0 /24 and 192.168.11.0 /24 ?
I am a little confused as to how you are routing between the two subnets in the first place, even if on the same VLAN.
In my lab I use vyos VMs with trunked VLANs to do all the routing between my subnets. Works out quite well.