Dear Maintainer, hello Luc,
I just tried to reproduce this issue.
I started with a minimal buster amd64 qemu VM.
Then following steps led me to that or at least a similar error:
- installed minimal desktop environment, virtualbox and rdesktop
- started virtualbox and created a test VM
- activated in that VM the "Remote Display" server
- start up the VM
- received the "Connection closed" and noticed that I have forgot
to install virtualbox-ext-pack for RDP and installed it.
- started up the VM again
- but still get the "Connection closed" with return value 76.
When starting the VM manually I receive at this system following:
benutzer@debian:~$ LANG=C /usr/lib/virtualbox/VirtualBox --comment test
--startvm 413459d5-ce28-4038-9e7a-9ab7008e2fa1 --no-startvm-errormsgbox
10/11/2018 15:45:43 Listening for VNC connections on TCP port 3389
10/11/2018 15:45:43 Listening for VNC connections on TCP6 port 5900
10/11/2018 15:45:43 ListenOnTCPPort: Address already in use
Unfortunately this looks like getting lost unnoticed anywhere.
And shouln't 3389 be RDP after installing virtualbox-ext-pack?
I tried a stretch amd64 qemu VM with unstable of the date of stretch
release and found it starts up with no problem.
That second VM updated to current date worked also without problem.
The difference was I installed the extension pack just later.
So I noticed in Prefrences - Extensions that the order of
the "VNC" and the "Oracle VM VirtualBox Extension Pack" is
different - it fails when "VNC" is first.
This was also visible with unsorted ls output:
benutzer@debian:~$ ls -lU /usr/lib/virtualbox/ExtensionPacks
insgesamt 8
drwxr-xr-x 3 root root 4096 Nov 10 15:32 VNC
drwxr-xr-x 8 root root 4096 Nov 10 15:39 Oracle_VM_VirtualBox_Extension_Pack
Above is from the failing VM.
Unfortunately I do not know how to manipulate that "directory order".
At least by moving VNC to some other directory I could get this VM also to work.
In the virtualbox log files is also a difference:
benutzer@debian:~$ grep -E "port.*3389" VirtualBox\ VMs/*/Logs/VBox.log*
....
VirtualBox VMs/test/Logs/VBox.log.1:00:00:00.676417 VNC: port = 3389
VirtualBox VMs/test/Logs/VBox.log.2:00:00:00.440089 VRDP: TCP server
listening on port 3389 (IPv4 and IPv6).
In VBox.log.2 the port was taken by RDP, in VBox.log.1 it was VNC.
Another way to check if one is affected is to look at the handshake.
If following is shown then there is a VNC server active at this port.
benutzer@debian:~$ socat - TCP4:10.0.2.15:3389
RFB 003.008
Therefore you, Luc, might want to check if this is really the issue in your
case.
This ordering issue should probably be forwarded to virtualbox-ext-pack
or virtualbox package.
Kind regards,
Bernhard
