Crash on linux host of windows guest by running CureIt

Frankenstine · Post by **Frankenstine** » 16. Apr 2008, 11:29

I have instant virtual mashine crash or 100% processor buzy by CureIt scan process. It is much more likely crashing (not guest OS, virtual mashine instead) than process freezing.
Host: customized 32-bit 2.6.18 kernel, Debian etch (4.0 updated). Stable OpenVZ patches, 100Hz interrupt frequency, SMP, big memory support (upto 64GB with sparse model). 4GB of physical memory installed. AMD64 processor with two cores. AMD-V disabled for guest, ACPI enabled, IO APIC disabled.
"VBoxManage -v" say: 1.5.6r28266
Guest: WindowsXP SP2 with latest patches. 512 MB of memory configured for guest.
Program: CureIt (free DrWeb antivirus software for emergency applying). ftp://ftp.drweb.com/pub/drweb/cureit/cureit.exe direct link to used version (updates frequently!).
strace (near crash):

Code: Select all

futex(0x80758d4, FUTEX_WAKE, 1)         = 0
write(6, "8", 1)                        = 1
gettimeofday({1208336600, 86465}, NULL) = 0
gettimeofday({1208336600, 86492}, NULL) = 0
gettimeofday({1208336600, 86520}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1208336600, 86547800}) = 0
futex(0x80756b8, FUTEX_WAIT, 119, {29, 999972200}) = 0
futex(0x80756f4, FUTEX_WAKE, 1)         = 0
write(6, "8", 1)                        = 1
gettimeofday({1208336600, 86732}, NULL) = 0
gettimeofday({1208336600, 86759}, NULL) = 0
gettimeofday({1208336600, 86787}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1208336600, 86815040}) = 0
futex(0x80756b8, FUTEX_WAIT, 121, {29, 999971960}) = 0
futex(0x80756f4, FUTEX_WAKE, 1)         = 0
write(6, "8", 1)                        = 1
gettimeofday({1208336600, 86998}, NULL) = 0
gettimeofday({1208336600, 87026}, NULL) = 0
gettimeofday({1208336600, 87054}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1208336600, 87082040}) = 0
futex(0x80756b8, FUTEX_WAIT, 123, {29, 998971960}) = 0
futex(0x80756f4, FUTEX_WAKE, 1)         = 0
write(6, "8", 1)                        = 1
gettimeofday({1208336600, 87267}, NULL) = 0
gettimeofday({1208336600, 87295}, NULL) = 0
gettimeofday({1208336600, 87322}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1208336600, 87350240}) = 0
futex(0x80756b8, FUTEX_WAIT, 125, {29, 999971760}) = 0
futex(0x80756f4, FUTEX_WAKE, 1)         = 0
futex(0x8090fbc, FUTEX_WAKE, 1)         = 1
gettimeofday({1208336600, 87529}, NULL) = 0
futex(0x8092514, FUTEX_WAIT, 1, NULL)   = 0
futex(0x8092540, FUTEX_WAKE, 1)         = 0
futex(0x8075ae0, FUTEX_WAIT, 1, NULL)   = 0
futex(0x8075b1c, FUTEX_WAKE, 1)         = 0
futex(0x8075ae0, FUTEX_WAIT, 3, NULL
!!Assertion Failed!!
Expression: pVM->patm.s.pGCStateHC->fPIF == 1
Location  : /home/vbox/vbox-1.5.6/src/VBox/VMM/PATM/PATM.cpp(6075) int PATMR3HandleTrap(VM*, CPUMCTX*, RTGCPTR, RT
GCPTR*)
Crash in patch code f76c33d8 (804dbc88) esp=f64f6aec
Patch state=4 flags=c30c1001 fDirty=0
<NULL>
)   = -1 EINTR (Interrupted system call)
+++ killed by SIGTRAP +++

vitaz · Post by **vitaz** » 29. Apr 2008, 02:51

I confirm this

content of VirtualBox.log is always the same, only esp values vary:

Code: Select all

Log created: 2008-04-29T00:37:58.768758000Z
Executable: /usr/lib/virtualbox/VirtualBox
Arg[0]: /usr/lib/virtualbox/VirtualBox
Arg[1]: -comment
Arg[2]: WinXPdeSp3
Arg[3]: -startvm
Arg[4]: 67537e93-4381-4cd2-42a1-fd7a30ead231

!!Assertion Failed!!
Expression: pVM->patm.s.pGCStateHC->fPIF == 1
Location  : /build/buildd/virtualbox-ose-1.5.6-dfsg/src/VBox/VMM/PATM/PATM.cpp(6075) int PATMR3HandleTrap(VM*, CPUMCTX*, RTGCPTR, RTGCPTR*)
Crash in patch code f9e234b8 (804dc237) esp=f85834bc
Patch state=4 flags=c30c1001 fDirty=0
<NULL>

P.S. Found this bugtracker post:
http://www.virtualbox.org/ticket/1439