• [6.12.0-rc4.1] vfio-bind-error


    Kwakx
    • Closed

    Since the rc3 version, after restarting I get an alert: "VM Autostart disabled due to vfio-bind error", on rc4.1 is the same.

     

    On rc2, nothing like that happens

    homelab-diagnostics-20230430-2344.zip




    User Feedback

    Recommended Comments



    6 minutes ago, Xeniummm said:

    I tried to delete the vifo but I can't find any documentation on how to do this.

    Can you please provide me with the command to delete the Vifo file ?

    goto tools->system devices is there a blue tick next to the HBA?

     

    image.png

     

    Un check and the bind selected option button will allow you to save the new vfio file.

     

    or from the cmdline you could do either of the following: 

     

    nano  /boot/config/vfio-pci.cfg and just delete the text from the file and save. or rm  /boot/config/vfio-pci.cfg 

    Link to comment
    4 minutes ago, SimonF said:

    goto tools->system devices is there a blue tick next to the HBA?

     

    image.png

     

    Un check and the bind selected option button will allow you to save the new vfio file.

     

    or from the cmdline you could do either of the following: 

     

    nano  /boot/config/vfio-pci.cfg and just delete the text from the file and save. or rm  /boot/config/vfio-pci.cfg 

    Hello SimonF

     

    Here is how my system devices looks like for the Raid controler 

    I will go for the second atempt where I will try to delete the vifo from cli

    I will post the result.

    Screenshot 2023-10-21 123832.png

    Link to comment
    2 hours ago, Xeniummm said:

    Hello SimonF

     

    Here is how my system devices looks like for the Raid controler 

    I will go for the second atempt where I will try to delete the vifo from cli

    I will post the result.

    Screenshot 2023-10-21 123832.png

    For me the device didn't show up in tools > system devices, presumably because it had been removed from the system long ago. 

     

    I tried Krusader, but it didn't have access to /boot and I didn't know if it was possible to change that.

     

    3 hours ago, SimonF said:

    goto tools->system devices is there a blue tick next to the HBA?

     

    image.png

     

    Un check and the bind selected option button will allow you to save the new vfio file.

     

    or from the cmdline you could do either of the following: 

     

    nano  /boot/config/vfio-pci.cfg and just delete the text from the file and save. or rm  /boot/config/vfio-pci.cfg 

    This is what worked for me. Going into the command line and typing:

    rm /boot/config/vfio-pci.cfg 

     

    That file only had one line in it, so deleting the file was not a problem. Your setup may be different.

    Link to comment
    2 minutes ago, randomusername said:

    For me the device didn't show up in tools > system devices, presumably because it had been removed from the system long ago. 

     

    I tried Krusader, but it didn't have access to /boot and I didn't know if it was possible to change that.

     

    This is what worked for me. Going into the command line and typing:

    rm /boot/config/vfio-pci.cfg 

     

    That file only had one line in it, so deleting the file was not a problem. Your setup may be different.

    Checking a box on the system devices saving, and then removing and saving again will also rewrite the vfio file to match the system devices display.

    • Like 1
    Link to comment

    Hello All

     

    For me is now  working the VM Manager

    I have manually removed the VIB file as suggested and restarted the Server.

    After Restart I was able to start the VM with no problem and I have tried to create a VM.

    after I filled up the VM profile with the latest settings I tried to create the VM and got a new surprise 

    The GUI was unresponsive. I considered that I made a mistake in configuration and I may have assigned the same IP address to the new VM.

    After rebooting the server and rebuilding the Parity I tried again to create a VM and all went smoothly and with no problems.

     

    Thank you for your Support

    Edited by Xeniummm
    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.