Re: virtualbox just became slow
On Fri, 11 Nov 2011 07:37:49 +1100, Scott Ferguson wrote:
>On 11/11/11 00:41, Steve Kleene wrote:
>> On Tue, 8 Nov 2011 12:54:11 +0000 (UTC), I wrote:
>>
>>>> I've been happily running a virtualbox Windows XP machine (VM) on a
>>>> Wheezy host for eight months. However, the VM just became
>>>> pathologically slow. For example, if I boot the VM, call Photoshop 6,
>>>> and open a small JPG, it all works but takes several minutes. During
>>>> much of this time the XP Task Manager pins at 100% CPU usage,
>> On Thu, 10 Nov 2011 10:22:14 +1100, Scott Ferguson replied:
>>> Debian/VirtualBox - check dmesg[*1]
dmesg shows these:
[ 10.093878] vboxdrv: Found 2 processor cores.
[ 10.094047] vboxdrv: fAsync=0 offMin=0x80e offMax=0x1b19
[ 10.094144] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 10.094149] vboxdrv: Successfully loaded version 4.1.2_Debian\
(interface 0x00190000).
[ 10.419123] vboxpci: IOMMU not found (not registered)
>>> and VirtualBox log for
>>> relevant messages. ... You don't say what sort of
>>> VirtualBox disk system you use.
It's normal format (VDI), dynamically allocated. VBox.log shows these
errors:
00:00:01.983 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005)\
aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display}\
aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
00:00:02.016 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005)\
aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display}\
aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
00:00:12.936 PATM: Stop monitoring IDT handler pages at 812a9bec - invalid\
write 812a9880-812a9884 (this is not a fatal error)
00:00:12.940 PATM: Stop monitoring IDT handler pages at 812a94a4 - invalid\
write 812a9770-812a9771 (this is not a fatal error)
>> Sorry, I meant to mention that there's 8 GB of free disk space on c:.
>> I have never defragged it.
>
>Oh?
>So every read involves a game of hide and seek in the Pacific Ocean? :-)
I did defrag tonight and it didn't help the problem.
>>> ... I'd also suggest you
>>> temporarily disable the virtual NIC to rule out Windoof network
>>> activity as the problem.
This had a definite effect. With the virtual NIC (attached to NAT), it took
Photoshop 50-55 sec to load. Without the NIC, it took 12 sec. This was
reproducible. In either case trying to print a 95KB JPG from Photoshop
gave this:
Cannot print. Initialization error. The error code is 10.
The IDT error handler errors did not show up when the NIC was disabled.
This all used to work with NAT. Any ideas how to get it back?
> (or move to a proper OS like Debian)
That is my host OS. It may not be obvious, but I've be using various *IX
since 1982 and learned those long before I learned DOS. My hosts are all
Debian. I still need some access to Windows because of co-workers who use
it.
Reply to: