(*) Changed to 4GB since you added more RAM. The other recommendations have not changed.mpack wrote:Assigning 3 cores to a VM on a 2 core host might well do that (i5-3210M specs).NorbyD wrote: It runs now but seems snail slow as before.
I would reduce VM RAM to 2048MB (*). Reduce cores to 2. Reduce graphics RAM to 128MB. Install the host Extension Pack (6.1.42).
Just updated to 7.0 and got error message...
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Just updated to 7.0 and got error message...
Re: Just updated to 7.0 and got error message...
I made those changes.mpack wrote:(*) Changed to 4GB since you added more RAM. The other recommendations have not changed.mpack wrote:Assigning 3 cores to a VM on a 2 core host might well do that (i5-3210M specs).NorbyD wrote: It runs now but seems snail slow as before.
I would reduce VM RAM to 2048MB (*). Reduce cores to 2. Reduce graphics RAM to 128MB. Install the host Extension Pack (6.1.42).
With those changes, initially I noticed it loads faster until after the Windows logo then lagging begins.
I attached the log.
Please advise.
Thanks.
- Attachments
-
- Windows2-2023-02-08-08-07-16.log 2.zip
- (40.29 KiB) Downloaded 2 times
-
- Volunteer
- Posts: 690
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Just updated to 7.0 and got error message...
You have overallocated your host resources.
From your log:
You need to lower the VM Memory to less than the 7.0GB you have available. Your current setting is 8GB.
You machine only has 2 physical cores. You have allocated 3. Lower it to 2.
You have been advised to do this by previously. Please make these changes before asking for further diagnosis.
From your log:
Code: Select all
00:00:03.740994 Host RAM: 16384MB (16.0GB) total, 7253MB (7.0GB) available
00:00:03.996599 RamSize <integer> = 0x0000000200000000 (8 589 934 592, 8 192 MB, 8.0 GB)
00:00:03.996595 NumCPUs <integer> = 0x0000000000000003 (3)
00:00:04.500031 CPUM: Physical host cores: 2
You machine only has 2 physical cores. You have allocated 3. Lower it to 2.
You have been advised to do this by previously. Please make these changes before asking for further diagnosis.
Re: Just updated to 7.0 and got error message...
I think that was the wrong one I uploaded as I made those changes.
This should be the correct one.
This should be the correct one.
- Attachments
-
- Windows2-2023-02-08-08-07-16.log.zip
- (40.29 KiB) Downloaded 4 times
-
- Volunteer
- Posts: 690
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Just updated to 7.0 and got error message...
Sigh - you still have 3 CPU cores and 8GB memory allocated according to your latest posted log.
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Just updated to 7.0 and got error message...
And still a mismatched extension pack.
Re: Just updated to 7.0 and got error message...
The log isn't reflecting my current setup - I set it up as you advised.granada29 wrote:Sigh - you still have 3 CPU cores and 8GB memory allocated according to your latest posted log.
Let me see if there is a way to reset the logs...
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Just updated to 7.0 and got error message...
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)
Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)
Re: Just updated to 7.0 and got error message...
Hi Scott,scottgus1 wrote:Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)
I appreciate your help and patience as well as Granada29!
I've included the log again. Now, previously, the log didn't reflect the changes I made in settings. So I'm including some screenshots. I might have to do separate comments if they're too big to include in one comment.
- Attachments
-
- Windows2-2023-02-09-11-31-39.log.zip
- Log_2_9_23
- (39.31 KiB) Downloaded 2 times
Re: Just updated to 7.0 and got error message...
These are the screenshots of my current settings just in case the log doesn't reflect.
Now, it takes about 15 minutes to load everything from Start which is ridiculously too long!
Initially, it loads pretty quick but then drastically slows down after the Windows logo
screen.
Please advise.
Thanks!
Now, it takes about 15 minutes to load everything from Start which is ridiculously too long!
Initially, it loads pretty quick but then drastically slows down after the Windows logo
screen.
Please advise.
Thanks!
- Attachments
-
- Video_memory_VB.zip
- Video memory screenshot
- (191.25 KiB) Downloaded 4 times
-
- Processor_VB.zip
- Processor Screenshot
- (133.47 KiB) Downloaded 3 times
-
- RAM_VB.zip
- Ram screenshot.
- (222.41 KiB) Downloaded 3 times
-
- Volunteer
- Posts: 690
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Just updated to 7.0 and got error message...
One thing that I do is to go to System Preferences -> Security&Privacy -> Privacy (in macOS) and make sure that both VirtualBox and VirtualBoxVM are disabled in Accessibility and Input Monitoring. That may help reduce load if they are enabled.
Also - do you need audio in the application you are trying to run in the VM? If not then disable Audio in the VM settings.
Also - do you need audio in the application you are trying to run in the VM? If not then disable Audio in the VM settings.