Opened 16 years ago
Closed 8 years ago
#1778 closed defect (obsolete)
Windows XP Guest crash with Kaspersky 2009 (rdpmc) -> fixed in SVN
Reported by: | Oxmosys | Owned by: | |
---|---|---|---|
Component: | VMM | Version: | VirtualBox 1.6.2 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | other |
Description
When using VirtualBox 1.6.2 with Windows XP SP2 guest with kaspersky 2009 installed, the computer crash a few seconds after boot. This is always reproducible.
Attachments (8)
Change History (94)
comment:1 by , 16 years ago
by , 16 years ago
comment:3 by , 16 years ago
The crash will probably go away if you turn on VT-x in the VM settings dialog.
comment:4 by , 16 years ago
VT-x totally enabled : No crash, but Windows XP won't boot, it stays waiting just after the welcome screen, when the desktop should normally appears. VT-x partially enabled : It boots to the desktop and works correctly during a few seconds, then crash with a BSOD VT-x disabled : It boots to the desktop and works correctly during a few seconds, then crash with a BSOD
comment:5 by , 16 years ago
We have to check this ourselves then. Is there a demo of Kaspersky 2009 and if so, does the problem occur with that version as well?
Also, there's no partial VT-x; it's either enabled or it's not. Can you attach a log when you have VT-x enabled?
by , 16 years ago
Attachment: | VBox.2.log added |
---|
comment:6 by , 16 years ago
I waited 30 minutes for Windows XP to boot, and then attached the VBox.log file, and closed Windows which was still not booted.
Kaspersky free trial version is here : http://usa.kaspersky.com/trials/home-users/anti-virus-7/tp/
You were right, there is no partial VT-x (I thought this because of the grey case). I tested VT-x enabled (don't boot) and disabled (crashes).
comment:7 by , 16 years ago
Guest type: | other → Windows |
---|
comment:8 by , 16 years ago
Component: | other → VMM |
---|
comment:10 by , 16 years ago
This bug can still be reproduced in 1.6.6 release when VT-x is enabled. However, the bug is not reproducible anymore with VT-x disabled!
comment:11 by , 16 years ago
Ah false, the situation improved : The guest system does not immediately crash anymore, but it still crashes with a BSOD on random situations.
comment:14 by , 16 years ago
This bug can be still reproduced with 2.0 release when VT-x is enabled. With VT-x disabled, it crashes on some circumstances (ex: when accessing a .zip file). Nothing changed since 1.6.6 release.
comment:15 by , 16 years ago
The problem that VirtualBox in VT-x disabled and AMD-V mode can't correctly skip and injects #UD then guest execute performance monitoring code - rdpmc instruction and read/write unknown for VirtualBox performance counters MSRs by rdmsr, wrmsr. Kaspersky 2009 use these instructions in kernel mode of heuristic analysis engine.
VirtualBox correctly work with Kaspersky on Intel VTx.
comment:16 by , 16 years ago
MMh, I just tried 2.0.2 with VT-x enabled (I have a intel core 2 duo CPU) and it still crashes with a BSOD when clicking on .zip archives.
comment:17 by , 16 years ago
Opps, there is other bug on 2.0.2 with VT-x enabled. Yesterday I check only heuristic analysis engine with VT-x - work correct. Other bug - VBox hangs when guest write to write-protected page (on supervisor level) with WP disabled bit of CR0.
comment:18 by , 16 years ago
I think your problem is no VT-x, your problem is Guest additions, try to start XP and unistall Gust additions from control panel
comment:19 by , 16 years ago
No, the bug is identical without guest additions (I just tested). Crash without VT-x when accessing .zip files, doesn't boot with VT-x
comment:21 by , 16 years ago
Replying to oxmosys:
2.0.4, not fixed yet.
Kaspersky just released a new KIS and KAS:
Kiss (firewall and all)
ftp://ftp.kaspersky.com//products/english/homeuser/kis2009/kis8.0.0.506en.exe
Kas (no firewall)
ftp://ftp.kaspersky.com//products/english/homeuser/kav2009/kav8.0.0.506en.exe
Have anyone had a chance to test it yet?
-T
comment:24 by , 16 years ago
I'm afraid not since the RDPMC x86 instruction still causes an exception.
We (Kaspersky Lab) can disable certain features of KAV/KIS and not use RDPMC on Virtual Box to avoid the crashes, but to do it, we need a reliable way of detecting Virtual Box "from within". Any ideas?
comment:25 by , 16 years ago
Unfortunately there's no CPUID bit for RDPMC, so we'll have to properly support this instruction ourselves. I've opened an internal defect for this.
comment:26 by , 16 years ago
Summary: | Windows XP Guest crash with Kaspersky 2009 → Windows XP Guest crash with Kaspersky 2009 (rdpmc) |
---|
comment:27 by , 16 years ago
I also get this crash however it could be related to the scanning engine. I only seem to get the crash after about 2 seconds after starting a system scan using Kaspersky. Im not at all an expert on Virtualbox but I thought it would be worth mentioning it. I have Win XP Pro SP3. My settings are near enough default.
STOP: 0x0000008E (0xC000001D, 0xF70213A3, 0xF4233AB0, 0x00000000)
The file which causes the crash as shown on the BSOD is 'KL1.sys'.
I have VirtualBox version 2.1.2 so by the look of it the crash still happens in the latest version. This is not an inportant bug for me since I was only messing around with VirtualBox. I installed the 30 day trial of Kaspersky Internet Security 2009 including all the latest updates for Windows and for Kaspersky. Guest Additions are installed.
comment:28 by , 16 years ago
Was this fixed in 2.1.4? There is no sigh of bug 1778 in the change log.
follow-up: 30 comment:29 by , 16 years ago
If there is no changelog entry then the probability that this was already fixed is low.
comment:30 by , 16 years ago
Replying to frank:
If there is no changelog entry then the probability that this was already fixed is low.
Any idea if it is in the queues for 2.1.6 (or whatever they are calling the next release)?
comment:31 by , 16 years ago
Summary: | Windows XP Guest crash with Kaspersky 2009 (rdpmc) → Windows XP Guest crash with Kaspersky 2009 (rdpmc) -> fixed in SVN/2.2 |
---|
comment:32 by , 16 years ago
Kaspersky Internet Security 2009 (trial version) seems to be happy here.
comment:33 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:36 by , 16 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Dudes! Guys! This is NOT fixed. Windows XP Pro SP3 and kis8.0.0.506en.exe will only boot up if you turn off VT-x support. And at that it runs like poop (slow, freezes up a lot).
Please fix VT-x support before closing this bug.
Running KAVremover9.exe (in safe mode) and reverting to kis7.0.1.325en.exe for now.
Many thanks, -T
follow-up: 39 comment:37 by , 15 years ago
It works here, so some more information is required. VBox.log of such a session and exact Kaspersky version would be helpful.
comment:39 by , 15 years ago
Replying to sandervl73:
It works here, so some more information is required. VBox.log of such a session and exact Kaspersky version would be helpful.
2) The exact version is kis8.0.0.506en.exe or Kaspersky Internet Security suite Version 8.0.0.506 "english". You can download it from: http://www.kaspersky.com/kis_latest_versions http://www.kaspersky.com/kis_latest_versions?downlink=206910253
1) Please give me exact directions on how to harvest this log (how to clear out the old stuff, where it is located, what format you want it in, etc.).
-T
by , 15 years ago
Attachment: | VB-WinXP-2009-04-20-19-12-12.log added |
---|
XP-Pro-SP3, kis8.0.0.506en.exe with VT-x crash log
by , 15 years ago
Attachment: | vbox_kis8.0.0.506de_exe.log added |
---|
XP SP3 on Vista X64, kis8.0.0.506de.exe
comment:40 by , 15 years ago
I have same problem.
VirtualBox 2.2.2 hosted on Ubuntu 9.04 jaunty (official public release) with a Windows XP Pro SP3 guest. Kaspersky (KIS) 8.0.0.506.
Since installing KIS the WinXP guest has become unusable. It just hangs immediately after booting up, with max CPU. Cannot even turn KIS off as it does not respond.
I'll probably trash my WinXP guest and start again with a clean install, only this time I'll take a VirtualBox snapshot before installing KIS. :-)
comment:41 by , 15 years ago
This bug is affecting my ability to give good tech support to my customers who have purchased Kiss8 from me. Since this is affecting my business, would the developers please consider upping the priority on this?
Many thanks, -T
comment:42 by , 15 years ago
For anyone moving from Windows to Linux there are almost always going to be Windows applications that they need to continue using, at least for a while. Wine is a solution for some apps but running a virtualized Windows guest [in VirtualBox] may be the only solution for some. I certainly have an app that just won't work in Wine and for which there is no Linux alternative.
If I could run my Windows guest offline that would be a solution. Unfortunately the app needs network access.
Given the above, those same people need the same system security that they had in Windows, in my case the ability to run Kaspersky Internet Security. I've seen similar problems reported for other antivirus software on a Windows guest, e.g. Symantec.
So, this is a serious problem.
I'd consider using a different antivirus if that were possible. Does anyone know of an Internet security app / antivirus that works OK in a Windows XP SP3 guest running in VB on Linux?
comment:43 by , 15 years ago
comment:44 by , 15 years ago
This bug is getting close to a year old (2008-06-26). It is a total pain in the neck! Is there any chance of this being fixed in 2.2.4? This is affecting my business.
comment:45 by , 15 years ago
ToddAndMargo, please use more correct language. It wouldn't help showing your emotions here, if you will us pay for our work - it may affect our priorities. Shouting won't.
comment:46 by , 15 years ago
This isn't fixed in 2.2.0, 2.2.2 and 2.2.4. I have exact the same issue like described above with Kaspersky 2009.
follow-up: 66 comment:48 by , 15 years ago
[quote]2008-12-26 11:18:03 changed by wordmonger ¶
I'm afraid not since the RDPMC x86 instruction still causes an exception.
We (Kaspersky Lab) can disable certain features of KAV/KIS and not use RDPMC on Virtual Box to avoid the crashes, but to do it, we need a reliable way of detecting Virtual Box "from within". Any ideas?quote
I know that if I look at the bios memory starting at b0000 (video memory) that VirtualBox is shown up there (video card). Perhaps you could use that info? You'll need to see exactly the offset where "VirtualBox" shows up and might have problems with priveledges. I am not sure how you would look at this as it's probably protected memory. Just a suggestion.
comment:49 by , 15 years ago
From: http://forums.virtualbox.org/viewtopic.php?f=15&t=19292&p=83392#p83392 [quote="sandervl"]... I'll have more time for 3.0.2. Remind me in case I forgotquote
Hi Sandervl,
3.0 just got announced. Nag, Nag, Nag :-)
Also, Kaspersky announced version 9 (2010): http://www.kaspersky.com/kis_latest_versions
-T
comment:50 by , 15 years ago
Kaspersky Internet Security version 9 works fine here (XP SP2 guest; VT-x). Trying version 8.0.0.506 next.
comment:51 by , 15 years ago
Reproduced high cpu load with version 8. Only happens without nested paging here (I have a Core i7 CPU). Investigating.
comment:52 by , 15 years ago
Summary: | Windows XP Guest crash with Kaspersky 2009 (rdpmc) -> fixed in SVN/2.2 → Windows XP Guest crash with Kaspersky 2009 (rdpmc) -> fixed in SVN |
---|
Ok, found and fixed the problem. Performance is normal now. Fix will be included in 3.0.2, which shouldn't be that far off.
follow-up: 54 comment:53 by , 15 years ago
Hi guys!
Today I've installed VB 3.0.0 r49315 in my Vista Ultimate x64. I've created a VM with WinXP SP3, and tried KIS 2009 8.0.0.517/506 and KIS 9.0.0.463 CF1 (beta) and IN BOTH CASES, after a few minutos 2 or 3 of working VB got hunged.
My base system ins a Pentium IV 3,4 Ghz / 4 GB RAM DDR2 800 Mhz.
Any idea? Some months ago I tried an older VB (I think 2.1.2 versión)with a KIS and my virtual XP hunged too.
Any idea?.
Regards.
follow-up: 55 comment:54 by , 15 years ago
Replying to harlan4096:
Today I've installed VB 3.0.0 r49315
Yes: see comment #52. Wait for 3.0.2, where to patch will reside. Then test and report.
-T
comment:55 by , 15 years ago
Replying to ToddAndMargo:
Replying to harlan4096:
Today I've installed VB 3.0.0 r49315
Yes: see comment #52. Wait for 3.0.2, where to patch will reside. Then test and report.
-T
Ok, thanks, I saw that comment, but I thought maybe It was maybe a different problem.
Regards.
comment:56 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
follow-up: 59 comment:57 by , 15 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Windows XP starts further but still hangs shortly after start with Kaspersky 2009 and high cpu usage.
I am using 3.0.2. Can anyone confirm this?
comment:58 by , 15 years ago
It still doesn't work on 3.0.2 (Windows Vista host, Windows XP SP3 host, KIS 9.0.0.463, VT-x is not available). System first hangs for some time, and later it starts working but KIS is not accessible (i.e. unable to open KIS window). KIS functions are not available (grayed) in Windows Explorer as well.
comment:59 by , 15 years ago
Replying to unggnu:
Windows XP starts further but still hangs shortly after start with Kaspersky 2009 and high cpu usage. I am using 3.0.2. Can anyone confirm this?
Yes. VBox 3.0.2, Host: CentOS 5.3, Guest: XP-Pro-SP3. Kaspersky Work Space Security (kav6.0.3.837_winwksen.exe). The corporate edition this time. It now has drags and dead stop since the upgrade. Very annoying to have the mouse stop activating buttons and typing stop every three minutes or so.
Work around (not a good one): send a <ctrl><alt><delete> from the "Machine" pull down.
-T
follow-ups: 61 64 comment:60 by , 15 years ago
Hi All,
I have a machine I need to update to 3.0.2. Does anyone know if Kaspersky version 7 still runs on 3.0.2? http://www.kaspersky.com/kis_previous_versions. It does under 2.2.4.
-T
comment:61 by , 15 years ago
VB 3.0.2 doesn't work either with KIS 9.0.0.463 CF1, my virtual XP hunged again ... bug still not fixed.
Regards.
follow-up: 63 comment:62 by , 15 years ago
It is working fine with VT-x here. If you report a problem and don't supply a VBox.log then I can't help you unfortunately.
comment:63 by , 15 years ago
Replying to sandervl73:
It is working fine with VT-x here. If you report a problem and don't supply a VBox.log then I can't help you unfortunately.
Attaching log file ...
Regards.
by , 15 years ago
Attachment: | WinXPSP3-2009-07-13-15-30-49.log added |
---|
Problem with KIS 2010 463 CF1 beta & VB 3.0.2
comment:64 by , 15 years ago
Replying to ToddAndMargo:
Hi All,
I have a machine I need to update to 3.0.2. Does anyone know if Kaspersky version 7 still runs on 3.0.2? http://www.kaspersky.com/kis_previous_versions. It does under 2.2.4.
Yes. KIS 7.0.1.325 on WXP Pro SP2 on VBox 3.0.2 on ubuntu 8.04.2.
follow-up: 67 comment:65 by , 15 years ago
Hello :-)
Workaround becoming unavailable?
The workaround for this problem -- of using KIS 7 -- is becoming unavailable.
My license is soon to run out so I bought a two year extension only to find it cannot be used on KIS 7. Error message: "This key is not for this application". support@… wrote "About the key problem, each area have itself solution, therefore you'd better contact the local agent/sales or local technical support for help". So I wrote to kaspersky.ie.cs@… asking for an activation code to extend the KIS 7 license but have had no reply > 96 hours later :-(
Best
Charles
comment:66 by , 15 years ago
Hello :-)
Replying to Serpardum
I know that if I look at the bios memory starting at b0000 (video memory) that VirtualBox is shown up there (video card). Perhaps you could use that info? You'll need to see exactly the offset where "VirtualBox" shows up and might have problems with priveledges. I am not sure how you would look at this as it's probably protected memory. Just a suggestion.
Any progress with that idea, Kaspersky? This bug is more than a year old so either intractable or a low priority for VirtualBox -- so a workaround by Kaspersky would be very welcome.
Best
Charles
follow-up: 68 comment:67 by , 15 years ago
Replying to catkin:
Hello :-)
Workaround becoming unavailable?
The workaround for this problem -- of using KIS 7 -- is becoming unavailable. Charles
Hi Charles,
The keys I sell work with 7, 8, and the unreleased 9. It all depends on how your create the key. Unfortunately, I only sell locally. But, all is not lost, you can contact my supplier and they will gin up a key that will work for you: http://www.useice.com/ 913.268.3250 They are very, very nice people, which is why I use them.
HTH, -T
comment:68 by , 15 years ago
Replying to ToddAndMargo:
Hi Charles,
The keys I sell work with 7, 8, and the unreleased 9. It all depends on how your create the key. Unfortunately, I only sell locally. But, all is not lost, you can contact my supplier and they will gin up a key that will work for you: http://www.useice.com/ 913.268.3250 They are very, very nice people, which is why I use them.
Thanks Todd :)
Thanks for confirming that it is possible to create a key for KIS 7 and suggesting ICE Systems. I'll contact them.
<rant> I'm getting nowhere fast with Kaspersky themselves on this. support@… said it is not a technical issue and referred me to http://www.kaspersky.com/customer_care_cente where it says "for orders placed on or after June 18, 2009, Kaspersky Lab eStore is supported by our trusted e-commerce partner - Digital River." so I wrote to kaspersky.ie.cs@… who took 3 days to reply saying they couldn't find my order despite being given the order reference and activation key. Don, on http://forum.kaspersky.com/index.php?showtopic=126784 suggested contacting Kaspersky via http://www.kaspersky.com/in/contacts (I live in India) which gives sales_india@… for non-technical email but Kaspersky's mail server bounced that address. The story continues ... </rant>
Best
Charles
comment:69 by , 15 years ago
Hello :-)
Update: the good news is that Kaspersky did issue an activation code for Kaspersky Internet Security 7.
The bad news is <rant>I still haven't had a response from Digital River, despite sending them a .pdf of the paid invoice</rant>. ICE systems were helpful but wanted me to buy another license. It was an email to info@… that produced the activation code along with an explanation that the reason the "customer care center was unable to help you is that you purchased the license through our Indian estore".
Best
Charles
follow-up: 71 comment:70 by , 15 years ago
Could you please move the license discussion to the forum? I know you mean well, but it makes the ticket harder to read. Thanks.
follow-up: 72 comment:71 by , 15 years ago
Replying to sandervl73:
Could you please move the license discussion to the forum? I know you mean well, but it makes the ticket harder to read. Thanks.
I'm sorry -- I did mean well. For users, bug workarounds can be as important, perhaps more important, than the bug itself, so I thought the license position useful here as well as on the Kaspersky forum. In retrospect I should have waited for the position to be determined before posting any relevant summary here. The position was determined in my last post which would have been my last on the subject.
comment:72 by , 15 years ago
Replying to catkin:
Replying to sandervl73:
Could you please move the license discussion to the forum? I know you mean well, but it makes the ticket harder to read. Thanks.
I'm sorry -- I did mean well. For users, bug workarounds can be as important, perhaps more important, than the bug itself, so I thought the license position useful here as well as on the Kaspersky forum. In retrospect I should have waited for the position to be determined before posting any relevant summary here. The position was determined in my last post which would have been my last on the subject.
sandervl73, I'm sorry some more and think it's worth adding another reply to say so. I added inappropriate material to this bug report and responded defensively to your gentle message saying so. Sorry. Lesson learned. Bug reports are not BBS threads.
comment:73 by , 15 years ago
I'm having crashes/hunging system in my virtualized WINXPSP3 + KIS 2010 9.0.0.463.
After some seconds of being started, the system hungs ... and I have to stop/force to stop the virtual machine sesion.
I provide logs of my VB.
Regards.
by , 15 years ago
Attachment: | WINXPSP3 + KIS2010-2009-10-04-22-02-08.log added |
---|
Windows XP hungs (KIS 2010 9.0.0.463)
comment:74 by , 15 years ago
Same here. WinXP SP3. Kaspersky 2009. Logs attached below. Summary: windows gets progressively slower, especially when running apps. That seems to speed up the time until it halts.
by , 15 years ago
Attachment: | Windows XP-2009-11-05-20-43-24.log added |
---|
follow-up: 78 comment:75 by , 15 years ago
But KIS 2010 9.0.0.736 is working fine here in VB 3.0.10 and even in 3.0.8 worked fine.
Regards.
comment:76 by , 15 years ago
Summary:
WinXP Pro SP3 VM hangs with Kaspersky 2009 (specifically kav8.0.0.523en.exe) and GA installed
Related ticket: #4974
Host:
9.10 w/ 2.6.31-14 64-bit kernel w/ VirtualBox 3.0.10r54097 and VirtualBox 3.0.12r54655 (Both versions are having the same issue)
Guest:
WinXP Pro SP3 32-bit w/ Guest Additions, Kaspersky 2009, VT Enabled, 512MB RAM, 10GB disk
comment:77 by , 15 years ago
Guy! Great news. I think I may have figured this one out. Or rather, Viznix did and did not realize it. Check out:
http://www.virtualbox.org/ticket/3792#comment:36
I could not get Virtual XP to reboot after running Go To Assist Express (GTAE) with out the restart jamming at a video shimmer. Viznix reported that he solved his reboot problem by upping his video memory to 16 MB and his RAM to 512 MB. Since my video was already at 32 MB, I bumped my RAM up from 352 Meg to 512 Meg. It fixed the reboot problem. Then I got to thinking, maybe bug 3792 was a duplicate of this bug. So, I fired up a VDI I had specially set up to test Kaspersky Internet Security Suite (KISS) 2009. And what do you know. KISS 2009 now run perfectly. Updates and License Server too.
So, everyone with this problem, try upping your RAM to at least 512 Meg. Then let us all know if it does the trick.
Virtual Box: this could very well be the same problem as bug 3792. We shall soon see.
-T
comment:78 by , 15 years ago
Replying to harlan4096:
But KIS 2010 9.0.0.736 is working fine here in VB 3.0.10 and even in 3.0.8 worked fine.
Regards.
Hi Harlan,
Set your RAM at or below 352 Meg an retry your test.
-T
comment:79 by , 15 years ago
Hi All,
I just got Kaspersky Internet Security 2010 (kis9.0.0.736en.exe) installed on my main XP guest. Yipee! RAM=512 Meg
-T
comment:80 by , 15 years ago
priority: | critical → major |
---|
comment:81 by , 13 years ago
I have VB 4.0.10R72479 and I've installed KIS2011 .566 and after a while always my virtual W7 (but tried in XP too) hangs ... this issue was also in previous builds of VB ... any solution?. The same issue is present wti hte new KIS2012 ...
Regards.
follow-up: 83 comment:82 by , 13 years ago
I am using VB 3.2.12 and kis11.0.2.556en.exe. After reinstalling and doing the update, my machine freezes up at 99% on the update. The host shows 100% CPU.
comment:83 by , 13 years ago
Replying to ToddAndMargo:
I am using VB 3.2.12 and kis11.0.2.556en.exe. After reinstalling and doing the update, my machine freezes up at 99% on the update. The host shows 100% CPU.
Update: http://products.kaspersky-labs.com/english/homeuser/kis2012/kis12.0.0.374en_gb.exe freezes my VM at 99% update too. Bummer ...
Oh, VM is XP-Pro-SP3, 32 bit. Host is CentOS 5.6, 32 bit
comment:84 by , 12 years ago
Hi everyone,
I am currently using VB 4.1.16 with a Windows XP x86 guest OS, and a Windows 7 x64 host OS. With Kaspersky Antivirus 6.0 , the virtual machine crashes after the Kaspersky's launch, since the database update of yesterday! Is this problem known with theses versions of VB and Kaspersky? I have to disable Intel VT-x to avoid the crash.. which is quite annoying.
Thank you for your help.
comment:85 by , 12 years ago
I can confirm this bug for VB 4.2.4 on a Core 2 Duo iMac. However, on a Core Duo iMac, the bug does not occur, event with VT-x enabled. HTH
comment:86 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | reopened → closed |
Please reopen if still relevant with a recent VirtualBox release.
Without the VBox.log of the XP VM there's not much we can say.