[VFIO Gotcha (PCI IDS Change) (VM Lockout due to autostart)]

Thanks for the update. Will keep this open to see if the PCI device id mapping can also be improved. 

 

[VFIO Gotcha (PCI IDS Change) (VM Lockout due to autostart)]

Also, anyway to check [8086:10d3] 07:00.0 with [8086:1d6b] 07:00.0. and find a miss match. Which stops the PCI device reset ?

Seems to me that the VM start is only checking "07:00.0".

[VFIO Gotcha (PCI IDS Change) (VM Lockout due to autostart)]

Well that's not what I experienced. 

 

Array Autostart Disabled.

VM Manager Enable VMs No.

pfSense VM Autostart On.

 

When I doVM Manager Enable VMs No to Yes.

The pfSense VM Autostarts irrespective Array Autostart was Disabled or Enabled.

[VFIO Gotcha (PCI IDS Change) (VM Lockout due to autostart)]

I did disable array autostart. And I was able to login. Then I disabled VM Manager start. Then I was able to start the array. But as soon as I enable VM Manager the error happend. The only way was to go back to old config without the Asus card and make the VM to not auto start.

[VFIO Gotcha (PCI IDS Change) (VM Lockout due to autostart)]

Hi Team,

 

I would like to raise a concern around my VFIO passthrough experience. May be this is a bug which can be addressed. Or this experience helps someone else from this pitfall.

 

I have a pfSense VM with 4 NIC's passthrough to the VM. The VM is set to autostart ofcourse.

The four NIC's are listed as below.

 

Now I decided to add a new Asus PCI M.2 X16 card which supports 4 M.2 drives with PCI bifurcation.

When I plugged in this device. My system would boot but freeze on startup. The error thrown out is a Filesystem corruption error displayed on the screenshot below.

 

After multiple hours of troubleshooting, I found that the PCI IDS have changed for the NIC's.

The four NIC's are now listed as below.

 

And if you see carefully, the old PCI IDS are now occupied by the SATA controllers.

 

I disabled Autostart of array, but could not disable Autostart of VM. Had to pull out the new Asus card, go back to old config. Set the pfSense VM not to autostart. Then plugged back the Asus card in. And finally I was able to start the VM Manager. At this point, if I manually start the VM without editing the passthrough devices, the same BTRFS corruption error happens and everything is frozen. So I hard rebooted the machine and before starting the pfSense VM, I edited the passthrough devices and everything works. Yey !!!

 

Can this be fixed in anyway ? The lockout situation is very bad, any check before starting the VM to see if the correct devices are passed through would be good. Then at least the VM manager starts and the VM config can be edited. My situation was severely bad as it was throwing out the array disks itself.

[Didn't Receive Your Registration Key?]

I too have not received my key.

 

Invoice No is 34211

Order Number is 357861566

 

Help.