I happened to be root while running the unbind command and the result of the command kicks me out of root back to my normal user. Had I been a normal user I am not sure I would have found this bug as a normal user because the sudo command returns you to normal user after complete.
The kernel does not crash as before, but I don't think the unbind command is working properly in this situation. I think it is clear the kernal oops problem is gone but the unbind step in the list does not work.
Christopher Penalver,
I finally got a chance to install 13.10 Saucy and retry this problem. The new unbind problem happens exactly described above. Reminder I am following these instructions: http:// www.linux- kvm.org/ page/How_ to_assign_ devices_ with_VT- d_in_KVM
I happened to be root while running the unbind command and the result of the command kicks me out of root back to my normal user. Had I been a normal user I am not sure I would have found this bug as a normal user because the sudo command returns you to normal user after complete.
root@apocalypse :/home/ bruzer# echo 0000:01:00.0 > /sys/bus/ pci/devices/ 0000\:01\ :00.0/driver/ unbind apocalypse: ~$
bruzer@
The kernel does not crash as before, but I don't think the unbind command is working properly in this situation. I think it is clear the kernal oops problem is gone but the unbind step in the list does not work.