Hi Chenjie,

Working scenario-1:
	Note:Used existing network(public-net0) mapped with physnet0(vlan) for instance creation.
	1. Configure helm chart in nova (controller-0)
	echo '8' > /sys/class/net/eno1/device/sriov_numvfs
	system helm-override-update stx-openstack nova openstack --values nova-overrides.yaml
	system helm-override-show stx-openstack nova openstack
	system application-list

	2. Instance creation used pci passthrough alias set that flavor
	mkdir -p /home/sysadmin/.ssh/
	vi /home/sysadmin/.ssh/id_rsa
	openstack keypair create key1 --private-key /home/sysadmin/.ssh/id_rsa
	openstack security group create security1
	openstack security group rule create --ingress --protocol icmp --remote-ip 0.0.0.0/0 security1
	openstack security group rule create --ingress --protocol tcp --remote-ip 0.0.0.0/0 security1
	openstack security group rule create --ingress --protocol udp --remote-ip 0.0.0.0/0 security1

	openstack flavor create --ram 4096 --disk 100 --vcpus 2 m1.medium.pci_passthrough
	openstack flavor set --property "pci_passthrough:alias"="intel-X722-pf:1" m1.medium.pci_passthrough
	openstack image create --file xenial-server-cloudimg-amd64-disk1.img --disk-format qcow2 --public ${NET}-image
	openstack server create --image ${NET}-image --flavor m1.medium.pci_passthrough --network public-net0 --security-group security1 --key-name key1 ${NET}-vm0
		
	3. No error, Instance is created successfully with active state.
	Note:  To ssh the VM, getting No route to host Error.
		controller-0:~/standard_script$ openstack network list
		| cb438bc0-0b9e-44bd-9639-4caf62a8bd8b | public-net0   | 335a7149-a4c3-45df-bf9d-746cb7cf7ab3 |
		
		compute-1:~$ sudo ip netns
			qdhcp-cb438bc0-0b9e-44bd-9639-4caf62a8bd8b (id: 4)
		compute-1:~$ sudo ip netns exec qdhcp-cb438bc0-0b9e-44bd-9639-4caf62a8bd8b bash
		compute-1:/home/sysadmin# ssh -i /home/sysadmin/.ssh/id_rsa ubuntu@192.168.101.234
		ssh: connect to host 192.168.101.234 port 22: No route to host
	
Failure scenario-2:
	1. Configure PCI-passthrough interface
	DATA0IF=eno1
	PHYSNET2='physnet2'
	system datanetwork-add $PHYSNET2 vlan
	system host-if-modify -m 1500 -n pcipass -c pci-passthrough ${COMPUTE} ${SRIOVIFUUID}
	system interface-datanetwork-assign ${COMPUTE} pcipass ${PHYSNET2}
		
	2. Update nova helm chart
	system helm-override-update stx-openstack nova openstack --values nova-overrides.yaml
	system application-apply stx-openstack
	system application-list
	3. Create network with(physnet2) pci-pt configured interface and instance with use flavor of pci passthrough alias set
	openstack network create ${NET}-net --mtu 1500 --provider-network-type vlan --provider-physical-network $PHYSNET2
	openstack subnet create --network ${NET}-net --subnet-range 192.168.15.0/24 --ip-version 4 --dhcp ${NET}-subnet
	openstack flavor create --ram 4096 --disk 100 --vcpus 2 m1.medium.pci_passthrough
	openstack flavor set --property "pci_passthrough:alias"="intel-X722-pf:1" m1.medium.pci_passthrough
	openstack image create --file xenial-server-cloudimg-amd64-disk1.img --disk-format qcow2 --public ${NET}-image
	openstack server create --image ${NET}-image --flavor m1.medium.pci_passthrough --network public-net0 --security-group security1 --key-name key1 ${NET}-vm0
		
	4. Instance created with ERROR status

So please let me know, Do we need to configure interface with (eno1)pci-pt or not ?
Which above scenario to use for pci-pt test?

Because physnet0(assigned data0) mapped to public-net0 using instance creation working as expected.