I am using VirtualBox 5.2.32 on a Windows 10/64-bit system with a Windows XP VM to run a number of 16-bit programs that won't run under W10 (they run in a cmd.exe box on the virtual XP machine). Speeds are VERY slow when some programs are performing a lot of I/O. Something that takes a few seconds with native WXP, takes several minutes with the virtual XP machine. Similarly, MS-Word 'Select all > F9 (perform calculations)' takes
- Virtualbox 64bit Guest Windows 10
- Virtualbox 32 Bit Windows Xp
- Download Virtualbox 32-bit Windows 7
- Telecharger Virtualbox 32-bit Windows 7
I've tried to speed it up as follows:
• Increasing 'base memory' from 1024MB to 3584Mb didn’t help. More than that (with 128MB video memory) prevents the virtual machine from loading. But 1024MB works fine with a W10 (332-bit) or Linux Mint (64-bit) host.
Windows 10 VM Image From A Windows 10 Machine. If the above option doesn’t suit and you want a VM image that runs Windows 10 32-bit or that doesn’t expire after 90 days you’re going to need access to an actual Windows 10 machine running the version of Windows 10 that you want to create a VM machine for. We are using win 7 32bit. Problem Event Name: APPCRASH Application Name: VirtualBox.exe Application Version: 5.2.6.20293 Application Timestamp: 5a5cc3df Fault Module Name: VirtualBox.dll Fault Module Version: 5.2.6.20293 Fault Module Timestamp: 5a5cc3f2 Exception Code: c0000005 Exception Offset: 001edcd7 OS Version: 6.1.7601.2.1.0.256.1.
• Enabling I/O APIC didn't help
• Can’t select multiple processors (option is greyed out on x64 host, but not on x32 or Linux host!)
• Can’t enable VT-x/AMD-V (Acceleration tab is greyed out on x64 host, but not on x32 or Linux host, which do have it selected!)
• Can’t enable Nested Paging (Acceleration tab is greyed out on x64 host, but not on x32 or Linux host, which do have it selected!)
• Increasing the display memory to 128MB didn’t help
• Enabling 3D Acceleration and/or 2D Video Acceleration didn't help
• Unchecking 'Use Host I/O cache' made no difference
Virtualbox 64bit Guest Windows 10
• Checking 'Solid-state drive' made no difference, even though the .VDI file is stored on a SSD
• Excluding c:VirtualMachines from Defender scan didn’t help, nor did disabling Avira in the VM• Turning off indexing (in the virtual machine) didn’t help
• Defragmenting the virtual hard disk (in the virtual machine) didn't help
• Changing the power plan (in the host machine) to 'high-performance' didn't help
Any other suggestions?
(Note that this does not happen with VirtualBox 5.2.32 on a Windows 10 32-bit
Virtualbox 32 Bit Windows Xp
system, or VirtualBox 5.2.32 on a Linux Mint 64-bit system with the identical
Windows XP VM, but the same anomaly does occur with VirtualBox 6.0.10 on a Windows 10 64-bit system!)