Slow startup with Linux Mint Guest

[Leloup78]

Bonjour,

I use VirtualBox 6.0.4r. Win7 is host and Linux Mint Cinnamon 18.3 is the guest.
It seems to me. The Linux startup is slower. I have to wait more than 2mn30s, is-it acceptable for you?

Leloup@Leloup-VirtualBox ~ $ dmesg
[ 0.000000] Linux version 4.10.0-38-generic (buildd@lgw01-amd64-059) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #42~16.04.1-Ubuntu SMP Tue Oct 10 16:32:20 UTC 2017 (Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17)
...
[ 17.339502] floppy0: no floppy controllers found
[ 102.464118] cgroup: new mount options do not match the existing superblock, will be ignored
85,124616 seconds are lost (=1minute and 24s)
...
[ 111.470315] 00:00:00.002185 main 5.2.20 r125813 started. Verbose level = 0
[ 113.613507] TCP: request_sock_TCP: Possible SYN flooding on port 34185. Sending cookies. Check SNMP counters.
[ 167.394556] TCP: request_sock_TCP: Possible SYN flooding on port 40611. Sending cookies. Check SNMP counters.
54 seconds are lost

It seems more likely to me that this is a problem with Virtualbox than Mint. The last one is the Virtualbox 6.0.4r extension pack. Mint updates do not fix the problem.

To compare, Linux Mint 19 Xfce starts in 2 minutes and Debian in 35s, with the same version of VirtualBox.

Does someone have a little bit idea to fix this problem?

Regards,

Le Loup

[socratis]

Does someone have a little bit idea to fix this problem?

Not a clue unless we see a complete log. You should know the procedure by now...

[Leloup78]

With logs like VBox.log.1,2,3

[Leloup78]

With logs like VBox.log.1,2,3

[Leloup78]

I did a mistake. When I wrote:

[ 17.339502] floppy0: no floppy controllers found
[ 102.464118] cgroup: new mount options do not match the existing superblock, will be ignored

85,124616 seconds are lost (=1minute and 24s)
This was not a issue because no floppy controllers found but it was a problem in relations with

cgroup: new mount options do not match the existing superblock, will be ignored

Searching on internet, it seemed to be a fstab issue. It happens to those who adjust the partitions.
On terminal, I taped: "cat /etc/fstab" I checked the UUID of two partitions and the UUID of the second partition did not match with the indicated one on GParted. I modified the UUID in order that it match with the GParted. I rebooted.

Now I get:

[ 19.353004] floppy0: no floppy controllers found
[ 19.353051] work still pending
[ 19.659384] cgroup: new mount options do not match the existing superblock, will be ignored

The start duration is decreased from 2mn30s to 45

Good. Nevertheless, I get:

[ 33.921527] TCP: request_sock_TCP: Possible SYN flooding on port 41011. Sending cookies. Check SNMP counters.
[ 43.890856] vboxsf: Successfully loaded version 6.0.4 (interface 0x00010004)
[ 45.107922] 20:16:27.067968 main VBoxService 6.0.4 r128413 (verbosity: 0) linux.amd64 (Jan 25 2019 19:35:06)

This last delay comes from Virtualbox. It was a little birdie who told me that.
Do you have any idea what do?
Regards,
Leloup

[Leloup78]

Bonjour,

Recently, there has been a further slowdown. At the end of the Boot, the screen switches to a black screen with the message:
Linux Mint 18.3 Sylvia Leloup-virtualBox tty1
Leloup-VirtualBox login:
The screen waits 1mn24s for us to log in.
Can we not remove this waiting phase?

All idea are welcome.

Regards,

Leloup

[Leloup78]

Bonjour,

Searching on web, I found out some commands.
Leloup@Leloup-VirtualBox ~ $ systemd-analyze blame | head -n 20
27.696s vboxadd.service
9.463s ntp.service
7.978s NetworkManager-wait-online.service
7.372s winbind.service
7.358s nmbd.service
6.950s samba-ad-dc.service
5.581s ModemManager.service
5.101s dev-sda1.device
4.778s irqbalance.service
4.211s accounts-daemon.service
4.016s loadcpufreq.service
3.590s NetworkManager.service
3.401s ondemand.service
3.370s virtualbox-guest-utils.service
3.080s avahi-daemon.service
3.015s grub-common.service
2.669s systemd-hwdb-update.service
2.366s speech-dispatcher.service
2.260s networking.service
2.249s systemd-udevd.service
Leloup@Leloup-VirtualBox ~ $
It is possible to save around 27s by removing vboxadd.service
leloup@leloup-VirtualBox ~ $ sudo systemctl disable vboxadd.service --now
[sudo] Mot de passe de leloup :
Removed symlink /etc/systemd/system/multi-user.target.wants/vboxadd.service.
The vboxadd.service is in relation with the Guest Additions, I suppose.
It is possible to enable it later. Nevertheless, I don't have any idea what impact of the vboxadd.service stopping is.

Do you have any idea?

Regards,
Leloup

[GoneSouth]

I just wanted to +1 this thread. I was seeing boot / restart times of several minutes on my Linux Mint 18.3 guest running on a Windows 10 host, and stumbled across this thread whilst googling for a solution.

Indeed I had recently resized the disk in my VM using Gparted, and after reading this thread saw the same issue where uuids in /etc/fstab did not match Gparted.

I updated /etc/fstab with the uuids from GParted, rebooted, and now boot times are down to a reasonable ~ 30 seconds.

[scottgus1]

Another possible consideration, though the op's original posts are old:

00:00:01.521669   NumCPUs <integer> = 0x0000000000000004 (4)
00:00:02.107868 CPUM: Physical host cores: 4

Virtualbox doesn't use hypertreads, and all physical host cores available in the guest does sometimes cause slowness in the guest.

In the above case, there's no hyperthreading:

00:00:02.107866 CPUM: Logical host processors: 4 present, 4 max, 4 online

So everything the host has is in the guest. Expect possible slothful behavior.