Ticket #2496 (reopened defect)
VirtualBox causes COMODO Firewall 3.0 AND COMODO Internet Security 3.5 to crash and become unresponsive.
|Reported by:||Happy-Dude||Owned by:|
NOTE:: Also made notice of this bug on these threads and will attach various crash dumps I have along with dumps from other users who has experienced the same problem--
I will add more details from my experiences in this bug report, since #1279 doesn't seem to have gotten any attention.
Alright, so this issue, as far as I can see, has existed since VirtualBox 1.5.2 and still does in the lastest (2.0.4).
What the bug is:
As far as I know (from my experience), COMODO Firewall Pro 3.0.25 installs just fine.
However, during rebooting the virtual machine, COMODO reports a crash, and generates a crash dump. So, at this point, the program has crashed. But afterwards, I was able to see cfp.exe still running with task manager, and the COMODO Firewall icon (on the task tray) becomes unresponsive.
Now, first, I thought it was the programs issue. I also tried my installation disk (which includes CFP 3.0.25, keep reading as to how I did this) with Virtual PC 2007. As it turns out, the Virtual Machine runs just fine.
Once VirtualBox 2.0 came out, it had Virtual PC 07 hard disk compatibility, so I tried it. (Originally, I thought it was a problem during the installation of the disk under VirtualBox.) Unfortunately, same results: COMODO crashes, and Virtual PC still runs fine.
I have since encountered others who has experienced this problem, and I even made note of it with COMODO Forums. And, the devs of COMODO was able to take a look at this issue during the development of COMODO Internet Security 3.5. Unfortunately, its been reported that COMODO is unable to do anything on their part.
What I can conclude from this:: This is a flaw in VirtualBox's design. Something with the COMODO program interacts with the VM and causes the program itself to crash.
Defect in VirtualBox design (since the install works just fine under Virtual PC) An issue that the COMODO developers were unable to fix Issue is not isolated so a certain host type, as reported with ticket #1279
Not an issue with .vhd extension compatibility Not an issue with how the users set up their installs
This is the most detailed info that I am able to give under my own experience. (This is just a copy paste of the COMODO Bug thread I made at https://forums.comodo.com/bug_reports/comodo_firewall_pro_3025_x32_crashes_in_virtualbox-t27744.0.html .) Read this for more detailed info on what I did, and continue reading with the thread so see other user experiences.
System Info: CPU: Intel Pentium 4 [ at ] 2.8 GHz (32 bit) Operating System: Windows XP Home w/ SP2 *(Virtualized) Windows XP Professional SP3* Other active security software: (Virtualized environment) avast! 4.8 home edition + Windows Defender + Winpatrol + ThreatFire
About problem: Alright, so here's my basic story.
--Running a modded (and legit) XP using programs nLite ( http://www.nliteos.com/) + RVMi ( http://integrator.siginetsoftware.com/index.php?download) + XPize ( http://www.xpize.net/) + WMP11 Slipstreamer ( http://www.boooggy.org/slipstreamer/) Reason for it --> Will eventually reinstall Windows XP to clean up my hard disk and on a new hard disk + wanted a light-weight installation with my customizations
--Using CFP add-on from http://www.msfn.org/board/Release-Comodo-Firewall-Pro-v302537-t119020.html (yes, that was me posting also, and I believe someone else also ran into a problem there)
--Will provide my last_session.ini from nLite to let you guys know what I did with my installation disk
SYMPTOM/ PROBLEM: Here's my problem:
--Testing disk on VirtualBox. Setup and runonce things (from nLite) completes, CFP crashes. Also everytime the virtual machine starts up, COMODO would crash.
Tray Icon is still there, but no response from it (double click = nothing) Makes a crash dump file (will attach) Firewall won't work at all afterwards
--Tested disk on Virtual PC 2007 (fresh install also). No problems, runs fine. Set firewall level to Safe mode --or the level that's before the lowest level, ie. second lowest level with least amount of prompts-- (both Firewall and D+)
--VirtualBox 2.02 released, compatibility with VPC native disks done (.vhd I believe). Still had VPC, and tested the .vhd with VirtualBox. Machine boots up, and error results (the same one or the same nature as installing the disk on VirtualBox 1.66).
I believe it might be a problem with driver integration and the VirtualBox drivers (my guess, but I don't have the time or the luxury to actually test it). I don't think its a problem with whatever else I integrated (software) or my tweaks and settings.
Thanks guys !! If there is anything else you guys need, let me know Smiley !!
Will attach my COMODO crashdump and my last_session.ini from nLite
What I did with my install disk RVMi some things to my disk (included logfile). After, I integrated XPize 4.7 + XPize Darkside (in 2 different sessions, since 1 session itself won't/ doesn't integrate both) with nLite. Then I followed with integrating WMP11 via Booogy's WMP11 slipstreamer. Then the final nLite session with major removals and integrations (last_session included).
Changed 8 years ago by Happy-Dude
- attachment Crash_dump_CIS_3.5.53896.424_Vbox_2.0.4_on_XP_Pro_SP3_32_bit.zip added
Changed 8 years ago by Happy-Dude
- Summary changed from VirtualBox causes COMODO Firewall 3.0 AND COMODO Internet Security 3.5 to crash and become unresponsive. to VirtualBox causes COMODO Firewall 3.0 AND COMODO Internet Security 3.5 to crash and become unresponsive. -> fixed in SVN
- Summary changed from VirtualBox causes COMODO Firewall 3.0 AND COMODO Internet Security 3.5 to crash and become unresponsive. -> fixed in SVN to VirtualBox causes COMODO Firewall 3.0 AND COMODO Internet Security 3.5 to crash and become unresponsive.
- Status changed from new to closed
- Resolution set to fixed
comment:10 Changed 7 years ago by Happy-Dude
- Status changed from closed to reopened
- Resolution fixed deleted