I remember last time I tried Comodo in VirtualBox, it was not working OK in VBox. I posted here and on VBox forums to resolve the issues, but of no avail.
I tried last RC version of comodo on windows 7 in Vbox with latest ubuntu 11.10 beta 2 as host and got a pleasant surprise, it seems to work OK. I am not sure if it,s really true or I am making a mistake.
Just curious to know if there are any VBox users who are using Comodo in VBox. What is their observation.
Please note - just because CIS 5.8 does not crash under VBox, that does not mean that it is performing as intended - it just means it is not crashing.
The problem with VBox was how it implemented interrupts and interrupt hooking. I’ve seen no advice that this has changed in the latestVBox builds and until it does change, I’d assume the defect is still there.
Could you explain this in technical terms ? Virtualbox is my production environment and I would like to know what this defect really is and how a bug report could be constructed for the Virtualbox developers.
Or at least provide a specific example that displays an issue with Comodo functioning inside Virtualbox.
They are the details passed to me by Egemen. I’ll see if I can more, but I got the impression that the way Vbox do it is not a bug, it’s just the way it is - resulting in an incompability with CIS. Not all incompatibilities are resolvable, unfortuantely.
That’s what I mean by anecdotal evidence… A user saying it runs fine doesn’t cut it…
Just because CIS seems to run fine, doesn’t mean it’s able to do everything it needs to do. I’d prefer word from Egemen on whether or not the issues have been fixed in VirtualBox before I would count on it to protect my system.
“Word from” is not good enough for Virtualbox users who have reasons to use this particular product instead of another virtual machines. So, the question is: is Comodo good enough for Virtualbox users, or should they be using another security product ?
I’ve been running CIS (from 5.5 through 5.8 betas to the current release) in VirtualBox for a bit over 3 months now, testing done 6 days out of 7 with a minimum of 30 confirmed malware samples (less than 18 hours old) without any fault.
Actually the only issue that we’ve had with CIS came on the non-VM production computer!