Error running VM because of fnternal filter

Hello! After upgrade cluster to 3.6 I cannot run VM's because of error: The host vms-intron did not satisfy internal filter HostDevice because it does not support host device passthrough.. How can I disable this filter?

12.11.15 16:40, Alexandr Krivulya пишет:
Hello!
After upgrade cluster to 3.6 I cannot run VM's because of error:
The host vms-intron did not satisfy internal filter HostDevice because it does not support host device passthrough..
How can I disable this filter?
Half-day brainstorm and everything is ok: delete from vm_device where type='hostdev' and vm_id='aaa-bbbb-ccccccc...';

On 12 Nov 2015, at 17:54, Alexandr Krivulya <shuriku@shurik.kiev.ua> wrote:
12.11.15 16:40, Alexandr Krivulya пишет:
Hello!
After upgrade cluster to 3.6 I cannot run VM's because of error:
The host vms-intron did not satisfy internal filter HostDevice because it does not support host device passthrough..
How can I disable this filter?
Half-day brainstorm and everything is ok:
delete from vm_device where type='hostdev' and vm_id='aaa-bbbb-ccccccc…';
and you didn’t add anything in UI, this is just an upgrade from 3.5 when using usbhost hook? thanks, michal
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

13.11.15 15:32, Michal Skrivanek пишет:
On 12 Nov 2015, at 17:54, Alexandr Krivulya <shuriku@shurik.kiev.ua> wrote:
12.11.15 16:40, Alexandr Krivulya пишет:
Hello!
After upgrade cluster to 3.6 I cannot run VM's because of error:
The host vms-intron did not satisfy internal filter HostDevice because it does not support host device passthrough..
How can I disable this filter?
Half-day brainstorm and everything is ok:
delete from vm_device where type='hostdev' and vm_id='aaa-bbbb-ccccccc…'; and you didn’t add anything in UI, this is just an upgrade from 3.5 when using usbhost hook?
When VM did not start after upgrade I did many different steps including attaching/detaching usb devices via UI. All my attempts ended with the same error. Only editing vm_device table by hand solves my problem.
participants (2)
-
Alexandr Krivulya
-
Michal Skrivanek