-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Then as Stated you are already vulnerable to much more than interrupt remapping will fix. So dont worry about it.
On 11/14/2013 06:00 PM, Giancarlo Razzolini wrote: > Em 14-11-2013 14:18, InterNetX - Robert Garrett escreveu: >> The issue you outlined below is not an openbsd issue, this is a >> kvm issue. and depends greatly on the version of linux/whatever >> you are using. The interrupt remapping you are talking about is >> either a bios issue (likely) or an issue with the hypervisor. >> >> it sounds like to me you are using or attempting to use SRIOV. >> >> all of the issues that you mentioned are still relevent even >> with "safe interrupts", as well as several you did not mention. > Robert, > > I do believe it is a specific issue with OpenBSD, because using > the same hypervisor I can do pci passthrough, using the same > versions, hardware, etc, to other operating systems using interrupt > remapping. > > I do have indeed SRIOV enabled on my bare metal bios. The thing is > that kvm specifically warns me that the guest do not support > interrupt remapping, when using openbsd only. As I told before, it > is not a problem for me right now, since I enable the unsafe > interrupt assignment and the OS works normally. > > Also, David, thanks for pointing out the patch, because since I > applied it, I did not experienced anymore lockups (so far). I am > betting it was indeed the problem. Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJShdk4AAoJEMrvovfl62c8DVEIALQmLbVLlnEsayXgpvCNiO2g gWF0+L4haMA7Rhf7FvRqOpXxCcZVhxk5ocEvSHLnyG1iYfh3tlnq1ts8rk9dfSHT DP1QA0ReXvVJKW2r8UcLVfI62H6gA93TiFZWLzFioO6NZExKlfe3DCWDg3scBqg3 dZFE7fcQW5iUjOdKJzw79DBTN1FlQUxeZ5EAGXN19XZAezbHP08KmmyAkil7jvqf DRFVRT7xnh0Vqa5H6Iz4KrQcasIPiLnt6ggxRzCxXL2EKu8K5Htwc9/LD4Jynz6y YVPKEPrL0lJ03ocb+U47vSynTfFWjDbOdKeIikqhUFDccfwTWUtefSVGmTzzdgQ= =tyuk -----END PGP SIGNATURE-----
