Linux guest VM starting verry slow on Linux Host:
BIOS/Hardware:
* 2 Kern Intel CPU, 2 kerns activated on BIOS
* VT activated on BIOS
* 8 GB RAM
* SSD Harddisk, some GB free space available
Host:
* Linux MInt 64
Guest OS:
* Linux MInt 64
* 4 GB RAM
Error/Symtome:
* the guest OS need some minutes for booting up to login window
* after login on Linux Mint guest system, i get a error message like "check your display driver, the driver dont support 3d speedup"
Any idea ?
Linux guest VM starting verry slow on Linux Host
-
- Posts: 20
- Joined: 11. Mar 2020, 02:30
Linux guest VM starting verry slow on Linux Host
Last edited by Lisa Miller on 26. May 2021, 17:55, edited 1 time in total.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Linux guest VM starting verry slow on Linux Host
Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
-
- Posts: 20
- Joined: 11. Mar 2020, 02:30
Re: Linux guest VM starting verry slow on Linux Host
Now attached my loggfile:
- Attachments
-
- LM20-Guest-2021-05-26-18-07-51.log.zip
- (29.72 KiB) Downloaded 15 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Linux guest VM starting verry slow on Linux Host
Your host PC is too old.Host CPU status:
00:00:02.415704 CPUM: Logical host processors: 2 present, 2 max, 2 online, online mask: 0000000000000003
00:00:02.415767 CPUM: Physical host cores: 2
00:00:02.416109 Full Name: "Intel(R) Core(TM)2 Duo CPU P9300 @ 2.26GHz"
00:00:02.241655 EnableNestedPaging <integer> = 0x0000000000000000 (0)
Guest CPU settings:
00:00:02.241115 NumCPUs <integer> = 0x0000000000000002 (2)
It's a Core 2 Duo, and it is probably barely handling the host OS, let alone a second OS. It's also missing Nested Paging, which helps a VM to run a lot better. If this cannot be enabled in the computer's BIOS, then you probably have the best you can get on this computer.
Time for a new PC!
-
- Posts: 20
- Joined: 11. Mar 2020, 02:30
Re: Linux guest VM starting verry slow on Linux Host
The host OS Linux MInt 64, are working fine on Core2 Duo since years. The Linux Mint 64 was working about up to 6 month ago fine as guest too.
Now one thing changed.
What are the NestedPaging are related ? Its related to RAM, VGA or to some other ?
And does the "NestedPaging" activated additional to the BIOS on one other configuration step too ?
Now one thing changed.
What are the NestedPaging are related ? Its related to RAM, VGA or to some other ?
And does the "NestedPaging" activated additional to the BIOS on one other configuration step too ?
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Linux guest VM starting verry slow on Linux Host
That's the sort of thing that should have been in the first post. It shows the "old" diagnosis to not really be the problem.Lisa Miller wrote:The Linux Mint 64 was working about up to 6 month ago fine as guest too.
Nested Paging relates to RAM, I think. However, since this VM has apparently been working beforehand on this host, so it may not be the problem either.
The VM environment does not show operating problems, just slowness. The problem could be a new update on the host, if updates have ben run. Or a problem within the OS itself, if the host OS and Virtualbox version have not been updated since the VM was working.
A Linux guru will have to look into this to see if I missed something in the log.