machine
machine copied to clipboard
docker
docker-machine cannot open SSH session to a newly created Hyper-V VM
While creating a Hyper-V VM on a Windows 10 machine the docker-machine gets stuck on creating a SSH session to that VM.
My Environment
- Windows 10 Pro
- docker version 17.03.1-ce, build c6d412e
- docker-machine version 0.10.0, build 76ed2a6
- OpenSSH 7.4
Description
I have enclosed a file ([createCommand.txt (https://github.com/docker/machine/files/908025/createCommand.txt)) with the messages from executing the following command
docker-machine -debug create -d hyperv --hyperv-virtual-switch ExternalWireless worker1
Everything looks fine until the script tries to open a SSH session to the newly created VM. Each attempt looks like this
Waiting for SSH to be available...
Getting to WaitForSSH function...
(worker1) Calling .GetSSHHostname
(worker1) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Get-VM worker1 ).state
(worker1) DBG | [stdout =====>] : Running
(worker1) DBG |
(worker1) DBG | [stderr =====>] :
(worker1) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM worker1 ).networkadapters[0]).ipaddresses[0]
(worker1) DBG | [stdout =====>] : 192.168.0.108
(worker1) DBG |
(worker1) DBG | [stderr =====>] :
(worker1) Calling .GetSSHPort
(worker1) Calling .GetSSHKeyPath
(worker1) Calling .GetSSHKeyPath
(worker1) Calling .GetSSHUsername
Using SSH client type: external
&{[-F /dev/null -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none [email protected] -o IdentitiesOnly=yes -i C:\Users\wojtek\.docker\machine\machines\worker1\id_rsa -p 22] C:\Program Files\OpenSSH\ssh.exe <nil>}
About to run SSH command:
exit 0
SSH cmd err, output: exit status 255:
Error getting ssh command 'exit 0' : ssh command error:
command : exit 0
err : exit status 255
output :
and after 60 such attempts the script quits with the message
Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
notifying bugsnag: [Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded]
The VM is created, it is given an IP address, and it starts. The interesting part is that I can create SSH session from the command line using exactly the same SSH commands as in the script (I have enclosed a file sshConnection.txt with debug messages from execution of that command)
ssh -v [email protected] -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=DEBUG -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o IdentitiesOnly=yes -i C:\Users\wojtek\.docker\machine\machines\worker1\id_rsa
This means that SSH server works fine on the VM and the certificate checks out. Just for completeness I tested creating a SSH session from the VM to the Windows 10 host machine, and it also works fine. Also, after reading a few posts, I turned the firewall off but the problem still persists.
Below is what I get when I ask the docker-machine to (a) list the VM docker hosts and (b) create SSH session to the new VM
C:\WINDOWS\system32>docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
worker1 - hyperv Running tcp://192.168.0.108:2376 Unknown Unable to query docker version: Get https://192.168.0.108:2376/v1.15/version: x509: certificate signed by unknown authority
C:\WINDOWS\system32>docker-machine ssh worker1
exit status 255
Notice that the 255 exit status is the same as in the create script.
Why does the same SSH command fail when executed in a docker-machine script and succeeds when executed from the command line? How do I further debug the issue?
Cheers, Wojtek
It looks like the issue is between OpenSSH and the docker-machine on Windows 10.
I have installed OpenSSH to enable remote PowerShell connections with Linux boxes (see installation guidelines @ https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH).
I have uninstalled OpenSSH, removed a reference to its binary from the Path system variable, and now the "docker-machine create ..." command completes ( ?! ).
The sequence of debug messages for creating SSH connection to the new VM now looks like this:
Getting to WaitForSSH function...
(worker1) Calling .GetSSHHostname
(worker1) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Get-VM worker1 ).state
(worker1) DBG | [stdout =====>] : Running
(worker1) DBG |
(worker1) DBG | [stderr =====>] :
(worker1) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM worker1 ).networkadapters[0]).ipaddresses[0]
(worker1) DBG | [stdout =====>] : 192.168.0.106
(worker1) Calling .GetSSHPort
(worker1) DBG |
(worker1) DBG | [stderr =====>] :
(worker1) Calling .GetSSHKeyPath
(worker1) Calling .GetSSHKeyPath
(worker1) Calling .GetSSHUsername
SSH binary not found, using native Go implementation
&{{{<nil> 0 [] [] []} docker [0xc8a0d0] <nil> []} 192.168.0.106 22 <nil> <nil>}
About to run SSH command:
exit 0
SSH cmd err, output: <nil>:
It appears that when the script cannot locate an SSH binary it falls back on a native Go implementation (whatever that is), which works.
I will open a separate issue with the PowerShell/Win32-OpenSSH folks, and I probably should also open a separate issue like "docker-machine does not work with OpenSSH on Windows 10" in this repo.
Cheers, Wojtek
As a workaround --native-ssh option can be specified when using docker-machine commands.
Just experiencing same issue on Windows 10 Home with native windows openssh:
c:\Users\feryardiant>docker version
Client:
Version: 17.10.0-ce
API version: 1.33
Go version: go1.8.3
Git commit: f4ffd25
Built: Tue Oct 17 19:00:02 2017
OS/Arch: windows/amd64
c:\Users\feryardiant>docker-machine version
docker-machine.exe version 0.14.0, build 89b8332
Based on output of docker-machine -D restart <machine-name> I tried to connect ssh manually using the same config and it's clear (for me) that main problem is because SSH key file permission.
ssh [email protected] -o IdentitiesOnly=yes -o PasswordAuthentication=no -i C:\Users\feryardiant\.docker\machine\machines\<machine-name>\id_rsa -p 50496
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions for 'C:\\Users\\feryardiant\\.docker\\machine\\machines\\<machine-name>\\id_rsa' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key "C:\\Users\\feryardiant\\.docker\\machine\\machines\\<machine-name>\\id_rsa": bad permissions
[email protected]: Permission denied (publickey,password,keyboard-interactive).
So I change the id_rsa file permission as described on stackoverflow link above & re-try to connect again
ssh [email protected] -o IdentitiesOnly=yes -o PasswordAuthentication=no -i C:\Users\feryardiant\.docker\machine\machines\local\id_rsa -p 50496
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions for 'C:\\Users\\feryardiant\\.docker\\machine\\machines\\local\\id_rsa' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key "C:\\Users\\feryardiant\\.docker\\machine\\machines\\local\\id_rsa": bad permissions
[email protected]: Permission denied (publickey,password,keyboard-interactive).
c:\Users\feryardiant>ssh [email protected] -o IdentitiesOnly=yes -o PasswordAuthentication=no -i C:\Users\feryardiant\.docker\machine\machines\local\id_rsa -p 50496
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\_______/
_ _ ____ _ _
| |__ ___ ___ | |_|___ \ __| | ___ ___| | _____ _ __
| '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__|
| |_) | (_) | (_) | |_ / __/ (_| | (_) | (__| < __/ |
|_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_|
Boot2Docker version 18.05.0-ce, build HEAD : b5d6989 - Thu May 10 16:35:28 UTC 2018
Docker version 18.05.0-ce, build f150324
docker@boot2docker:~$
Now, when I want to create new docker-machine I have to update the id_rsa file permission in order to make it works.
Any plan to make the generated SSH key have correct file permission by default?
Apologize for poor english & hopefully that help.
Cheers 🥂
Initial error
Error creating machine: Error in driver during machine creation: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
With docker-machine --debug:
(sparkles) DBG | Checking vm logs: /Users/David/.docker/machine/machines/sparkles/sparkles/Logs/VBox.log
(sparkles) DBG | Getting to WaitForSSH function...
(sparkles) DBG | Using SSH client type: external
(sparkles) DBG | Using SSH private key: /Users/David/.docker/machine/machines/sparkles/id_rsa (-rw-------)
(sparkles) DBG | &{[-F /dev/null -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet -o PasswordAuthentication=no -o ServerAliveInterval=60 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [email protected] -o IdentitiesOnly=yes -i /Users/David/.docker/machine/machines/sparkles/id_rsa -p 55553] /usr/bin/ssh <nil>}
(sparkles) DBG | About to run SSH command:
(sparkles) DBG | exit 0
(sparkles) DBG | SSH cmd err, output: exit status 255:
(sparkles) DBG | Error getting ssh command 'exit 0' : ssh command error:
(sparkles) DBG | command : exit 0
(sparkles) DBG | err : exit status 255
(sparkles) DBG | output :
In the VBox.log:
00:00:29.314084 Decompressing Linux... Parsing ELF... Performing relocations... done.
00:00:29.314238 Booting the kernel.
00:00:29.314391
00:00:29.314544 --------------------------------------------------------------------------------
00:00:29.314732 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:29.314766 emR3Debug: rc=VERR_PGM_INVALID_CR3_ADDR
00:00:30.316637 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:30.316892 Console: Machine state changed to 'GuruMeditation'
http://www.fixedbyvonnie.com/2014/09/heck-virtualbox-guru-meditation-error/
No solution so far.
Hi @dherges... I had the same initial problem:
"Error creating machine: Error in driver during machine creation: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded"
And, after all, the machine was created and I could see it running in VirtualBox. However, when I tried to ssh it I couldn't.
### What solves my problem: As "WojtekKozaczynski" described, looks that docker-machine doesn't play well with Windows' "OpenSSH", so I removed it from the PATH variable. Then I tried to build again the machine with "docker-machine" and it worked like a charm.
This is not the first time that I have had troubles with Windows' "OpenSSH", because at work when I tried to ssh a Linux machine it was causing some troubles for me, so I had to the same and the machine could do a successful ssh.
BTW, I'm using Windows 10 Home with Virtual Box.
@dherges if this solved your problem, try to comment it to shows others that this work, else you could facing another problem. I waste a lot of hours trying to use other approachs.
Regards!
Hello
I am also facing similar issues,
I am trying to create a docker machine with following command
docker-machine -D create nfsbox --virtualbox-no-vtx-check
This is where docker machine creation gets stuck
(nfsbox) DBG | Getting to WaitForSSH function...
(nfsbox) DBG | Using SSH client type: external
(nfsbox) DBG | Using SSH private key: /root/.docker/machine/machines/nfsbox/id_rsa (-rw-------)
(nfsbox) DBG | &{[-F /dev/null -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet -o PasswordAuthentication=no -o ServerAliveInterval=60 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [email protected] -o IdentitiesOnly=yes -i /root/.docker/machine/machines/nfsbox/id_rsa -p 40819] /usr/bin/ssh <nil>}
(nfsbox) DBG | About to run SSH command:
(nfsbox) DBG | exit 0
Any suggestions to what I could be missing?
My Setup Ubuntu 18.04 LTS Linode VM
This may happen if you have too open permissions on your private key. I notice that with docker-machine --debug create
(nfsbox) DBG | Using SSH private key: /root/.docker/machine/machines/nfsbox/id_rsa (-rw-------)
in my case permission on private key is (-rw-------) what should it be then?
It looks like the issue is between OpenSSH and the docker-machine on Windows 10.
I have installed OpenSSH to enable remote PowerShell connections with Linux boxes (see installation guidelines @ https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH).
I have uninstalled OpenSSH, removed a reference to its binary from the Path system variable, and now the "docker-machine create ..." command completes ( ?! ).
The sequence of debug messages for creating SSH connection to the new VM now looks like this:
Getting to WaitForSSH function... (worker1) Calling .GetSSHHostname (worker1) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Get-VM worker1 ).state (worker1) DBG | [stdout =====>] : Running (worker1) DBG | (worker1) DBG | [stderr =====>] : (worker1) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM worker1 ).networkadapters[0]).ipaddresses[0] (worker1) DBG | [stdout =====>] : 192.168.0.106 (worker1) Calling .GetSSHPort (worker1) DBG | (worker1) DBG | [stderr =====>] : (worker1) Calling .GetSSHKeyPath (worker1) Calling .GetSSHKeyPath (worker1) Calling .GetSSHUsername SSH binary not found, using native Go implementation &{{{<nil> 0 [] [] []} docker [0xc8a0d0] <nil> []} 192.168.0.106 22 <nil> <nil>} About to run SSH command: exit 0 SSH cmd err, output: <nil>:It appears that when the script cannot locate an SSH binary it falls back on a native Go implementation (whatever that is), which works.
I will open a separate issue with the PowerShell/Win32-OpenSSH folks, and I probably should also open a separate issue like "docker-machine does not work with OpenSSH on Windows 10" in this repo.
Cheers, Wojtek
Thanks for sharing this but is this native Go correct deployment procedure..?
I confirm that the issue is due to incorrect permissions on the private key. docker-machine should set the correct permissions on keys while creating machine.
Until this is fixed, set permissions manually:
icacls %USERPROFILE%\.docker\machine\machines\node1\id_rsa /inheritance:r
icacls %USERPROFILE%\.docker\machine\machines\node1\id_rsa /grant %USERNAME%:F
Just experiencing same issue on Windows 10 Home with native windows openssh:
c:\Users\feryardiant>docker version Client: Version: 17.10.0-ce API version: 1.33 Go version: go1.8.3 Git commit: f4ffd25 Built: Tue Oct 17 19:00:02 2017 OS/Arch: windows/amd64 c:\Users\feryardiant>docker-machine version docker-machine.exe version 0.14.0, build 89b8332Based on output of
docker-machine -D restart <machine-name>I tried to connect ssh manually using the same config and it's clear (for me) that main problem is because SSH key file permission.ssh [email protected] -o IdentitiesOnly=yes -o PasswordAuthentication=no -i C:\Users\feryardiant\.docker\machine\machines\<machine-name>\id_rsa -p 50496 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Permissions for 'C:\\Users\\feryardiant\\.docker\\machine\\machines\\<machine-name>\\id_rsa' are too open. It is required that your private key files are NOT accessible by others. This private key will be ignored. Load key "C:\\Users\\feryardiant\\.docker\\machine\\machines\\<machine-name>\\id_rsa": bad permissions [email protected]: Permission denied (publickey,password,keyboard-interactive).So I change the
id_rsafile permission as described on stackoverflow link above & re-try to connect againssh [email protected] -o IdentitiesOnly=yes -o PasswordAuthentication=no -i C:\Users\feryardiant\.docker\machine\machines\local\id_rsa -p 50496 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Permissions for 'C:\\Users\\feryardiant\\.docker\\machine\\machines\\local\\id_rsa' are too open. It is required that your private key files are NOT accessible by others. This private key will be ignored. Load key "C:\\Users\\feryardiant\\.docker\\machine\\machines\\local\\id_rsa": bad permissions [email protected]: Permission denied (publickey,password,keyboard-interactive). c:\Users\feryardiant>ssh [email protected] -o IdentitiesOnly=yes -o PasswordAuthentication=no -i C:\Users\feryardiant\.docker\machine\machines\local\id_rsa -p 50496 ## . ## ## ## == ## ## ## ## ## === /"""""""""""""""""\___/ === ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~ \______ o __/ \ \ __/ \____\_______/ _ _ ____ _ _ | |__ ___ ___ | |_|___ \ __| | ___ ___| | _____ _ __ | '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__| | |_) | (_) | (_) | |_ / __/ (_| | (_) | (__| < __/ | |_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_| Boot2Docker version 18.05.0-ce, build HEAD : b5d6989 - Thu May 10 16:35:28 UTC 2018 Docker version 18.05.0-ce, build f150324 docker@boot2docker:~$Now, when I want to create new
docker-machineI have to update theid_rsafile permission in order to make it works.Any plan to make the generated SSH key have correct file permission by default?
Apologize for poor english & hopefully that help.
Cheers 🥂
This solution really works for me. The key is to change the permission of the id_rsa file as described. I firstly found the answer in a Chinese blog, and now I also found it here, so add my feedback and appreciation. Once you edit the permission of the rd_rsa file in the right VM directory, you immediately found the "Waiting for SSH to be available..." begin to move ahead, LOL.
In my case on MacOS, checking the log of boot2iso showed the networking going up in 16s, DHCP at 31s, VBoxService at 34s, libdbus failing to load at 34s. Only a second try of docker-machine to connect via ssh with the guest succeeds.
VBoxManage controlvm default poweroff
docker-machine --debug start default
(default) DBG | Checking vm logs: /Users/USER/.docker/machine/machines/default/default/Logs/VBox.log
(default) DBG | Getting to WaitForSSH function...
(default) Waiting for an IP...
(default) DBG | Using SSH client type: external
(default) DBG | Using SSH private key: /Users/USER/.docker/machine/machines/default/id_rsa (-rw-------)
(default) DBG | &{[-F /dev/null -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet -o PasswordAuthentication=no -o ServerAliveInterval=60 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [email protected] -o IdentitiesOnly=yes -i /Users/USER/.docker/machine/machines/default/id_rsa -p 51484] /usr/bin/ssh <nil>}
(default) DBG | About to run SSH command:
(default) DBG | exit 0
[...pause...]
(default) DBG | SSH cmd err, output: exit status 255:
(default) DBG | Error getting ssh command 'exit 0' : ssh command error:
(default) DBG | command : exit 0
(default) DBG | err : exit status 255
(default) DBG | output :
(default) DBG | Getting to WaitForSSH function...
[..repeated attempts with ssh, then showvminfo followed by a successful ssh running ip addr show ...]
(default) DBG | SSH cmd err, output: <nil>:
(default) DBG | COMMAND: /usr/local/bin/VBoxManage showvminfo default --machinereadable
(default) DBG | STDOUT:
(default) DBG | {
(default) DBG | name="default"
(default) DBG | groups="/"
(default) DBG | ostype="Linux 2.6 / 3.x / 4.x (64-bit)"
[...]
(default) DBG | GuestAdditionsFacility_Graphics Mode=0,1631639487081
(default) DBG | }
(default) DBG | STDERR:
(default) DBG | {
(default) DBG | }
(default) DBG | Host-only MAC: 08002787869e
(default) DBG |
(default) DBG | Using SSH client type: external
(default) DBG | Using SSH private key: /Users/USER/.docker/machine/machines/default/id_rsa (-rw-------)
(default) DBG | &{[-F /dev/null -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet -o PasswordAuthentication=no -o ServerAliveInterval=60 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [email protected] -o IdentitiesOnly=yes -i /Users/USER/.docker/machine/machines/default/id_rsa -p 51484] /usr/bin/ssh <nil>}
(default) DBG | About to run SSH command:
(default) DBG | ip addr show
The tail of /Users/USER/.docker/machine/machines/default/default/Logs/VBox.log follows.
00:00:04.676217 AHCI#0: Port 29 reset
00:00:04.837931 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:04.844141 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:04.844497 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0233
00:00:04.845211 VMMDev: Guest Log: BIOS: Booting from CD-ROM...
00:00:05.218241 VMMDev: Guest Log: BIOS: KBD: unsupported int 16h function 03
00:00:05.218739 VMMDev: Guest Log: BIOS: AX=0305 BX=0000 CX=0000 DX=0000
00:00:05.721373 GIM: KVM: VCPU 0: Enabled system-time struct. at 0x0000000024992000 - u32TscScale=0xc587e6bc i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x351c9d731 uVirtNanoTS=0x147d9b8f8 TscKHz=2591998
00:00:05.721408 TM: Switching TSC mode from 'Dynamic' to 'RealTscOffset'
00:00:05.798506 GIM: KVM: Enabled wall-clock struct. at 0x0000000024991008 - u32Sec=1631638787 u32Nano=907434000 uVersion=2
00:00:12.715387 AHCI#0: Reset the HBA
00:00:12.715456 VD#1: Cancelling all active requests
00:00:12.722500 AHCI#0: Port 0 reset
00:00:13.044545 AHCI#0: Port 1 reset
00:00:13.045948 VD#1: Cancelling all active requests
00:00:16.056698 NAT: Link up
00:00:22.778973 VMMDev: Guest Additions information report: Version 5.2.34 r133893 '5.2.34'
00:00:22.779033 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00053100 (Linux >= 2.6, 64-bit)
00:00:22.779137 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:22.779254 VMMDev: vmmDevReqHandler_HeartbeatConfigure: No change (fHeartbeatActive=false)
00:00:22.779310 VMMDev: Heartbeat flatline timer set to trigger after 4 000 000 000 ns
00:00:22.779382 VMMDev: Guest Log: vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds
00:00:22.779649 VMMDev: Guest Log: vboxguest: misc device minor 58, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
00:00:28.262916 NAT: IPv6 not supported
00:00:31.263010 NAT: DHCP offered IP address 10.0.2.15
00:00:31.263408 NAT: DHCP offered IP address 10.0.2.15
00:00:34.006225 VMMDev: Guest Log: VBoxService 5.2.34 r133893 (verbosity: 0) linux.amd64 (Oct 10 2019 20:19:38) release log
00:00:34.006264 VMMDev: Guest Log: 00:00:00.000072 main Log opened 2021-09-14T17:00:16.231653000Z
00:00:34.006919 VMMDev: Guest Log: 00:00:00.000774 main OS Product: Linux
00:00:34.007363 VMMDev: Guest Log: 00:00:00.001218 main OS Release: 4.19.130-boot2docker
00:00:34.007650 VMMDev: Guest Log: 00:00:00.001509 main OS Version: #1 SMP Mon Jun 29 23:52:55 UTC 2020
00:00:34.007975 VMMDev: Guest Log: 00:00:00.001832 main Executable: /sbin/VBoxService
00:00:34.007989 VMMDev: Guest Log: 00:00:00.001833 main Process ID: 2158
00:00:34.007997 VMMDev: Guest Log: 00:00:00.001833 main Package type: LINUX_64BITS_GENERIC
00:00:34.010742 VMMDev: Guest Log: 00:00:00.004596 main 5.2.34 r133893 started. Verbose level = 0
00:00:34.013880 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x1, 0x8000000000000000
00:00:34.019820 VMMDev: Guest Log: 00:00:00.013664 vminfo rtldrNativeLoad: dlopen('libdbus-1.so.3', RTLD_NOW | RTLD_LOCAL) failed: libdbus-1.so.3: cannot open shared object file: No such file or directory
00:00:34.019908 VMMDev: Guest Log: 00:00:00.013765 vminfo Error: Unable to connect to system D-Bus (1/3): D-Bus not installed
00:00:34.021918 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:39.022425 VMMDev: Guest Log: 00:00:05.015737 vminfo Error: Unable to connect to system D-Bus (2/3): D-Bus not installed
00:00:44.025103 VMMDev: Guest Log: 00:00:10.017897 vminfo Error: Unable to connect to system D-Bus (3/3): D-Bus not installed
