Because they are exactly the same hardware so it will show the same vendor id and same device id. The only difference between the 2 cards is the slot it is sitting in (probably the 1st part in your output).
You can use dmidecode –t slot to match it with the output from lspci -nn to identify them each but you can not tell KVM that.
Interesting question though and generally I would leave it at "you probably need another, different, card" when I came across this:
On kernel.org it says that "Writing a device ID to /sys/bus/pci/drivers/.../new_id will attempt to dynamically add a new device ID to a PCI device driver. This may allow the driver to support more hardware than was included in the driver's static device ID support table at compile time. The format for the device ID is: VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID, Device ID, Subsystem Vendor ID, Subsystem Device ID, Class, Class Mask, and Private Driver Data. The Vendor ID and Device ID fields are required, the rest are optional. Upon successfully adding an ID, the driver will probe for the device and attempt to bind to it. For example: # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id"
And that lead me to the command setpci and an U&L topic that suggests you can change the device ID of PCI cards.
So maybe you can change one of the 8080:aa68 to another device id with one of these 2 methods. Do pick an id that is a similar card but maybe a bit older or newer than the one you have. Changing it to a random device id will probably cause trouble.
