[vfio-users] Unbind Vfio Passthrough = general protection fault

nahoxou at netcourrier.com nahoxou at netcourrier.com
Tue Sep 22 15:26:18 UTC 2015


Thanks for withopf deveject good tool who i use as a shutdown task schedule. I have new improvements now on xserver :
In a first host boot i get 4/5 vm cycles success.
Second host boot same 4/5 result!
The 5th attempt fail in both case.
Another idea please?
Well we're almost there...

Apart from the usual sysfs device inter face, you can disable cars in windows before shutting it down: there was a software called deveject and you can eject it device manager gui(devmgmt.msc).

On Sep 22, 2015 12:49 PM, <nahoxou at netcourrier.com> wrote:



|Have you tried without -daemonize switch? I had issues when running with -daemonize. When I shutdown the VM and I |immediately start the VM again using the same command, it complained about the devices aren't available to be assigned, |forgot the real wording of it.

|

|Then I tried to do without -daemonize. It took quite some time from the display got off after issuing shutdown from inside the |VM to QEMU process finally exits to the Terminal again. So probably 1/10 of your attempts has the correct timing in |unbinding the device when it is ready to be unbinded.

|
|Best regards,
|Okky Hendriansyah



Ok now without daemonize unbind works better.  Successful 7 cycles of start/wait win desktop icons/stop qemu one after the other without xserver.

But i get a general protection fault on the 8th attempt when i am on xserver.
My xserver only use intel graphic so no trace of nvidia...

Is there a way to check the card state or force card to be ready to unbind before unbind command?

I only know vfio bind create /dev/vfio/1 file... :(  






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20150922/ca71eb2f/attachment.htm>


More information about the vfio-users mailing list