virtualbox.org

Comodo Internet Security does not work properly in a windows guest in Virtual box while it seems to work OK in a windows guest in VMware and Virtual PC, also it works fine on real hardware as well. Can it be fixed please?

https://forums.comodo.com/empty-t60783.0.html;topicseen

Thanks

If changes need to be made, I would suggest to Comodo that they make their software compatible with VirtualBox rather than the other way around.

I have had Comodo Firewall and Antivirus (Internet Security as they call it) in a VM and no problems whatsoever. Even now, I still have a few VMs with Comodo Firewall running flawlessly.

BillG wrote:If changes need to be made, I would suggest to Comodo that they make their software compatible with VirtualBox rather than the other way around.

If Comodo Internet security has something wrong, it would not work properly in any VM software or even real hardware but seeing as it works in two VM software and on real hardware but does not woek well in VBox, I would assume that the people who make VB need to work at it.

Sasquatch wrote:I have had Comodo Firewall and Antivirus (Internet Security as they call it) in a VM and no problems whatsoever. Even now, I still have a few VMs with Comodo Firewall running flawlessly.

The developers of Comdo themselves say that it doesn,t work well in VirtualBox.

The Comodo devs are just like any other dev, it's never their fault, the other party need to change their program to work with theirs. That's just blaming someone else for their own incompetence. If it works in VMWare and VPC, but not VB, they are doing something wrong, not VB. The three virtualisers are in essence the same. If a simple security program like antivirus or firewall fail to work properly in a virtual environment, those who create it have to figure out why it doesn't work. Only then can it be improved. Just blaming others and let them screw up their own software just isn't the way to go. Work together, debug your own software in the virtual environment and look for a solution with each other.
Some just don't get it. Or am I too naïve?

Sasquatch wrote:The Comodo devs are just like any other dev, it's never their fault, the other party need to change their program to work with theirs.

Any official word from Virtualbox team?
It won't worth just bashing Comodo team.
It would be honest an acknowledgment.

Sasquatch wrote:The Comodo devs are just like any other dev, it's never their fault, the other party need to change their program to work with theirs.

Just blaming others and let them screw up their own software just isn't the way to go. Work together, debug your own software in the virtual environment and look for a solution with each other.[/quote]
Yeah... Work together with Comodo team in order to solve this...

If you want people to use the software which you produce, you have to ensure that it works properly with the software and hardware of your target user base. As an example, Internet Security software has to be updated to work with each new version of Windows because it is a big target.

Sometimes the target user base is not big enough to warrant the effort required. If the Comodo devs are aware that there is a problem but have not fixed it, maybe they have decided it is not worth the hassle. There are lots of things that people would like to see in VirtualBox (or WVPC or VMWare), but there has to be strong driving force to get it to the top of the "wish list".

BillG wrote:If the Comodo devs are aware that there is a problem but have not fixed it, maybe they have decided it is not worth the hassle.

What if the problem is on Virtualbox side?
I have problems with avast Internet Security alerts (firewall alerts) that the problem was on the Virtualbox side.
Sun team did nothing about it... http://forum.avast.com/index.php?topic= ... #msg516060

CIS 5 can't run into Virtualbox: https://forums.comodo.com/beta-corner-c ... #msg425567

Seems that Comodo teams do not test Comodo programs into Virtualbox (for instance: https://forums.comodo.com/help-ctm/virt ... #msg427138 and https://forums.comodo.com/beta-corner-c ... #msg417267).

Seems that the limitation is imposed by Sun Virtualbox:

WARNING: CIS does not work properly in VirtualBox because of the limitations imposed by this virtual machine(Vectored Exceptions fail). So please test it with another VM software.

Seems that Sun (users?) says that the problem is on Comodo side that does not develop their programs to run in Virtualbox. For instance, http://forums.virtualbox.org/viewtopic. ... 07&start=0

In other situations, the problem was on Virtualbox side and their did not acknowledge it...
http://forum.avast.com/index.php?topic= ... #msg516060

Who is telling the truth? Comodo or Sun?

Nothing about CiS 5 from me at this time, because it appears to be released just recently. But I have CiS 4.1 in a W7 x64 VM on Xubuntu 10.04 x64 running happily. I will try out CiS 5 later when the machine is at work again so it can access internet (I'm not hooking it up to my home network).

Sasquatch, thank you.
My thread get closed in Comodo forums (https://forums.comodo.com/general-discu ... #msg432959).
They stated the problem is *really* in your side.
I'm thinking again to return back to VMWare... but I really would like that Virtualbox team acknowledge it and try to solve it and don't give up.

I hate to bring you bad news, but I 'updated' my VM to use CIS 5 and it did not cause any major problems. Only thing is that it makes my system run very slow, down to a crawl due to the extensive I/O it generates. I removed it for now in favour of AVG, as that AV doesn't cause so much I/O when the virus database gets an update. But even so, in the time I ran it, there was no problem whatsoever.

So I'm wondering, what is the actual problem? Is it only with XP? I had no problems running CIS on Windows 7 x64.

Sasquatch wrote:So I'm wondering, what is the actual problem? Is it only with XP? I had no problems running CIS on Windows 7 x64.

Problems aren't apparent.
But VirtualBox is failing on virtualize the OS as it does offer support for necessary Microsoft needs.
In fact, I/O is a problem on updating CIS, but this problem is unrelated to Sun faults.
I think there is no comparison with AVG. CIS is superior in conception and technology, there is a free firewall also.

I've dropped VirtualBox to VMware due to this limitation.
Hope the Sun programmers take it seriously and improve the software.

Bei mir arbeitet CIS 5 in VirtualBox sehr gut. There aren't any problems with CIS 5 on Host win xp sp3 = guest win xp sp3. Of course xp 32Bit...on netbook with atom!