I need to run certain programs on Windows 10.
Most of my activity is on Linux Mint so I installed Windows 10 as a guest under VirtualBox on Linux.
It was never fast but tolerable ... until recently.
I allocated two cores of my 4-core processor and 8Gb of dram to it
It is now painfully slow.
I am posting this here in the hopes that it might resonate with someone that has had and solved the same issue.
TIA, Alan
pinnerite <pinnerite@gmail.com> wrote:
I need to run certain programs on Windows 10.
Most of my activity is on Linux Mint so I installed Windows 10 as a guest under VirtualBox on Linux.
It was never fast but tolerable ... until recently.
I allocated two cores of my 4-core processor and 8Gb of dram to it
It is now painfully slow.
I am posting this here in the hopes that it might resonate with someone that has had and solved the same issue.
TIA, Alan
I think the reality is that Windows 10 isn't meaningfully less hardware-hungry than Windows 11 - I encountered that fact on my old
computer, in 2021, I had been running Linux for two years, not wanting
to participate in Microsoft's public beta test of Win10, and in that
time, between 1809 and 20H2, it had massively grown into the codebase
we have today, with current builds of Win10 and 11.
Why it worked better for you, before, I honestly don't know, but it's inevitable that it eventually won't. Windows is always supporting
relatively recent hardware. Linux is more than superior, in the
abstract, I like running Win11 for its conveniences and niceties, but
there's simply no comparison to the performance of Linux, which still performs well on old hardware.
--
Joel Crump
On Sun, 18 Jun 2023 22:50:04 -0400
Joel <joelcrump@gmail.com> wrote:
pinnerite <pinnerite@gmail.com> wrote:
I need to run certain programs on Windows 10.
Most of my activity is on Linux Mint so I installed Windows 10 as a guest under VirtualBox on Linux.
It was never fast but tolerable ... until recently.
I allocated two cores of my 4-core processor and 8Gb of dram to it
It is now painfully slow.
I am posting this here in the hopes that it might resonate with someone that has had and solved the same issue.
TIA, Alan
I think the reality is that Windows 10 isn't meaningfully less
hardware-hungry than Windows 11 - I encountered that fact on my old
computer, in 2021, I had been running Linux for two years, not wanting
to participate in Microsoft's public beta test of Win10, and in that
time, between 1809 and 20H2, it had massively grown into the codebase
we have today, with current builds of Win10 and 11.
Why it worked better for you, before, I honestly don't know, but it's
inevitable that it eventually won't. Windows is always supporting
relatively recent hardware. Linux is more than superior, in the
abstract, I like running Win11 for its conveniences and niceties, but
there's simply no comparison to the performance of Linux, which still
performs well on old hardware.
--
Joel Crump
Cold comfort but thanks,
Alan
It is now painfully slow.
I need to run certain programs on Windows 10.
Most of my activity is on Linux Mint so I installed Windows 10 as a guest under VirtualBox on Linux.
It was never fast but tolerable ... until recently.
I allocated two cores of my 4-core processor and 8Gb of dram to it
It is now painfully slow.
I am posting this here in the hopes that it might resonate with someone that has had and solved the same issue.
TIA, Alan
I need to run certain programs on Windows 10.
Most of my activity is on Linux Mint so I installed Windows 10 as a guest under VirtualBox on Linux.
It was never fast but tolerable ... until recently.
I allocated two cores of my 4-core processor and 8Gb of dram to it
It is now painfully slow.
I am posting this here in the hopes that it might resonate with someone that has had and solved the same issue.
TIA, Alan
I need to run certain programs on Windows 10.
Most of my activity is on Linux Mint so I installed Windows 10 as a guest under VirtualBox on Linux.
It was never fast but tolerable ... until recently.
I allocated two cores of my 4-core processor and 8Gb of dram to it
It is now painfully slow.
I am posting this here in the hopes that it might resonate with someone that has had and solved the same issue.
TIA, Alan
On 6/18/23 21:04, pinnerite wrote:
I need to run certain programs on Windows 10.
Most of my activity is on Linux Mint so I installed Windows 10 as a guest under VirtualBox on Linux.
It was never fast but tolerable ... until recently.
I allocated two cores of my 4-core processor and 8Gb of dram to it
It is now painfully slow.
I am posting this here in the hopes that it might resonate with someone that has had and solved the same issue.
TIA, Alan
Windows VMs have been painfully slow, even on a fast (4GHz) host machine.
I find that what makes the most difference is the disk. It speeded up a lot when I changed to a NVMe.
pinnerite wrote:
It is now painfully slow.
Is it slow because "something" is noticeably eating lots of CPU time
within the VM? lots of I/O, lots of memory
task manager/resource monitor/process explorer are your friends ...
On Mon, 19 Jun 2023 14:10:35 +0100
Andy Burns <usenet@andyburns.uk> wrote:
pinnerite wrote:
It is now painfully slow.
Is it slow because "something" is noticeably eating lots of CPU time
within the VM? lots of I/O, lots of memory
task manager/resource monitor/process explorer are your friends ...
I gave up on moving the VMs to VMware. The VM converted to an ova file
in VirtualBox was unwound in VMware but the VM started and crashed. I
tried everything.
I have several Disks that I can plug in with caddies.
I have two backups. I went back to a slow but satisfactory Win-10
backup. Tar'd and gz'd it and copied the result to my work machine.
Unwound and tested it and it was OK but slow. Not as slow as before. I
did a bit of work and then tried to save a modified spread sheet.
"Not enough resorces".
Now I keep most of my data on linux folders so 50Gb should be enough
for Win-10. Anyway I increased it beyond 60Gb and it worked.
BUT I seem to keep encountering those pale blue screens
telling me that Windows has encountered errors
"but don't worry. we'll fix them and reboot when we've done it" or
words to that effect. It gets to 100% and then just sits there until I
do a VBox reset.
I will try to remove unwanted files and hope for ther best.
On 6/22/23 10:06, this is what pinnerite wrote:
On Mon, 19 Jun 2023 14:10:35 +0100One of my live Windows installs takes a good 68G on a disk of 100G.
Andy Burns <usenet@andyburns.uk> wrote:
pinnerite wrote:
It is now painfully slow.
Is it slow because "something" is noticeably eating lots of CPU time
within the VM? lots of I/O, lots of memory
task manager/resource monitor/process explorer are your friends ...
I gave up on moving the VMs to VMware. The VM converted to an ova file
in VirtualBox was unwound in VMware but the VM started and crashed. I
tried everything.
I have several Disks that I can plug in with caddies.
I have two backups. I went back to a slow but satisfactory Win-10
backup. Tar'd and gz'd it and copied the result to my work machine.
Unwound and tested it and it was OK but slow. Not as slow as before. I
did a bit of work and then tried to save a modified spread sheet.
"Not enough resorces".
Now I keep most of my data on linux folders so 50Gb should be enough
for Win-10. Anyway I increased it beyond 60Gb and it worked.
BUT I seem to keep encountering those pale blue screens
telling me that Windows has encountered errors
"but don't worry. we'll fix them and reboot when we've done it" or
words to that effect. It gets to 100% and then just sits there until I
do a VBox reset.
I will try to remove unwanted files and hope for ther best.
On 6/22/2023 10:21 AM, Big Al wrote:
On 6/22/23 10:06, this is what pinnerite wrote:
On Mon, 19 Jun 2023 14:10:35 +0100One of my live Windows installs takes a good 68G on a disk of 100G.
Andy Burns <usenet@andyburns.uk> wrote:
pinnerite wrote:
It is now painfully slow.
Is it slow because "something" is noticeably eating lots of CPU time
within the VM? lots of I/O, lots of memory
task manager/resource monitor/process explorer are your friends ...
I gave up on moving the VMs to VMware. The VM converted to an ova file
in VirtualBox was unwound in VMware but the VM started and crashed. I
tried everything.
I have several Disks that I can plug in with caddies.
I have two backups. I went back to a slow but satisfactory Win-10
backup. Tar'd and gz'd it and copied the result to my work machine.
Unwound and tested it and it was OK but slow. Not as slow as before. I
did a bit of work and then tried to save a modified spread sheet.
"Not enough resorces".
Now I keep most of my data on linux folders so 50Gb should be enough
for Win-10. Anyway I increased it beyond 60Gb and it worked.
BUT I seem to keep encountering those pale blue screens
telling me that Windows has encountered errors
"but don't worry. we'll fix them and reboot when we've done it" or
words to that effect. It gets to 100% and then just sits there until I
do a VBox reset.
I will try to remove unwanted files and hope for ther best.
That's your hiberfil.sys and your pagefile.
That's why I make a few adjustments here, to get those sizes down.
The simple one, is:
powercfg /h off
and the hiberfile space is eliminated. That is suited to a desktop computer only.
Virtual machines don't have Hibernate and Sleep, because the same functions can be obtained with hosting software control buttons. The hosting software is so clever, if the machine runs out of RAM, the machine "freezes" on purpose,
to give you time to free up RAM.
But there are many other times, that VM Guests are hell on earth, because
you can't tell what is going on inside them.
Paul
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 297 |
Nodes: | 16 (2 / 14) |
Uptime: | 01:45:01 |
Calls: | 6,666 |
Calls today: | 4 |
Files: | 12,212 |
Messages: | 5,335,487 |