VRDE no luck (VBox 6.0.12 on OpenSUSE 15.1)

[bofh42]

Hello,

I'm having trouble getting VRDE to run ..

• VirtualBox 6.0.12 installed from Distribution
• OpenSUSE Leap 15.1
• VNC-extension pack NOT installed
• Oracle Extension Pack 6.0.12 installed and working

Guest-VM is a Windows 10 64bit, VBox Guest Tools v 6.0.12 installed
Guest runs fine in normal mode
Starting it in headless mode states that VRDE is listening on port 3890 (value given in config)

well, but it's lying: there is nothing listening ....

Log file

• VBox.log

  Logfile

  (90.22 KiB) Downloaded 13 times

showvminfo

Code: Select all

christian@desktopcb:~> VBoxManage showvminfo Windows10
Name:                        Windows10
Groups:                      /
Guest OS:                    Windows 10 (64-bit)
UUID:                        a06d999a-2a57-4c60-a54e-d8ad7d6aac94
Config file:                 /mnt/nfs/data/VirtualBoxVMs/Win10/Windows10/Windows10.vbox
Snapshot folder:             /mnt/nfs/data/VirtualBoxVMs/Win10/Windows10/Snapshots
Log folder:                  /mnt/nfs/data/VirtualBoxVMs/Win10/Windows10/Logs
Hardware UUID:               a06d999a-2a57-4c60-a54e-d8ad7d6aac94
Memory size                  8192MB
Page Fusion:                 disabled
VRAM size:                   256MB
CPU exec cap:                100%
HPET:                        disabled
CPUProfile:                  host
Chipset:                     piix3
Firmware:                    BIOS
Number of CPUs:              4
PAE:                         disabled
Long Mode:                   enabled
Triple Fault Reset:          disabled
APIC:                        enabled
X2APIC:                      disabled
Nested VT-x/AMD-V:           disabled
CPUID Portability Level:     0
CPUID overrides:             None
Boot menu mode:              message and menu
Boot Device 1:               DVD
Boot Device 2:               HardDisk
Boot Device 3:               Not Assigned
Boot Device 4:               Not Assigned
ACPI:                        enabled
IOAPIC:                      enabled
BIOS APIC mode:              APIC
Time offset:                 0ms
RTC:                         local time
Hardw. virt.ext:             enabled
Nested Paging:               enabled
Large Pages:                 disabled
VT-x VPID:                   enabled
VT-x unr. exec.:             enabled
Paravirt. Provider:          Default
Effective Paravirt. Prov.:   HyperV
State:                       running (since 2019-11-25T11:27:40.033000000)
Monitor count:               1
3D Acceleration:             enabled
2D Video Acceleration:       disabled
Teleporter Enabled:          disabled
Teleporter Port:             0
Teleporter Address:
Teleporter Password:
Tracing Enabled:             disabled
Allow Tracing to Access VM:  disabled
Tracing Configuration:
Autostart Enabled:           enabled
Autostart Delay:             0
Default Frontend:
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
SATA (0, 0): /mnt/nfs/data/VirtualBoxVMs/Win10/Windows10/Windows10.vdi (UUID: 71bf1f92-fb0a-4e50-a751-8d8c4812002c)
SATA (1, 0): /mnt/nfs/data/VirtualBoxVMs/VBoxGuestAdditions_6.0.12_v2.iso (UUID: cdc09a08-54d0-4f59-b0c4-305b9c37c661)
NIC 1:                       MAC: 080027BC602E, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:                       MAC: 08002700C079, Attachment: NAT Network 'NatNetwork', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 3:                       disabled
NIC 4:                       disabled
NIC 5:                       disabled
NIC 6:                       disabled
NIC 7:                       disabled
NIC 8:                       disabled
Pointing Device:             USB Tablet
Keyboard Device:             PS/2 Keyboard
UART 1:                      disabled
UART 2:                      disabled
UART 3:                      disabled
UART 4:                      disabled
LPT 1:                       disabled
LPT 2:                       disabled
Audio:                       enabled (Driver: PulseAudio, Controller: HDA, Codec: STAC9221)
Audio playback:              enabled
Audio capture:               enabled
Clipboard Mode:              Bidirectional
Drag and drop Mode:          Bidirectional
Session name:                headless
Video mode:                  1592x1081x32 at 0,0 enabled
[color=#FF0000]VRDE:                        enabled (Address 192.168.80.6, Ports 3890-3895, MultiConn: on, ReuseSingleConn: off, Authentication type: null)[/color]
[color=#FF0000]VRDE port:                   3890[/color]
Video redirection:           disabled
VRDE property               : TCP/Ports  = "3890-3895"
VRDE property               : TCP/Address = "192.168.80.6"
VRDE property               : VideoChannel/Enabled = <not set>
VRDE property               : VideoChannel/Quality = <not set>
VRDE property               : VideoChannel/DownscaleProtection = <not set>
VRDE property               : Client/DisableDisplay = <not set>
VRDE property               : Client/DisableInput = <not set>
VRDE property               : Client/DisableAudio = <not set>
VRDE property               : Client/DisableUSB = <not set>
VRDE property               : Client/DisableClipboard = <not set>
VRDE property               : Client/DisableUpstreamAudio = <not set>
VRDE property               : Client/DisableRDPDR = <not set>
VRDE property               : H3DRedirect/Enabled = <not set>
VRDE property               : Security/Method = <not set>
VRDE property               : Security/ServerCertificate = <not set>
VRDE property               : Security/ServerPrivateKey = <not set>
VRDE property               : Security/CACertificate = <not set>
VRDE property               : Audio/RateCorrectionMode = <not set>
VRDE property               : Audio/LogPath = <not set>
OHCI USB:                    disabled
EHCI USB:                    disabled
xHCI USB:                    enabled

USB Device Filters:
<none>

Available remote USB devices:
<none>

Currently Attached USB Devices:
<none>

Bandwidth groups:  <none>

Shared folders:

Name: 'home', Host path: '/home' (machine mapping), writable, auto-mount, mount-point: 'i:'
Name: 'mnt', Host path: '/mnt' (machine mapping), writable, auto-mount, mount-point: 'y:'
Name: 'windows', Host path: '/mnt/windows' (machine mapping), writable, auto-mount, mount-point: 'd:'

VRDE Connection:             not active
Clients so far:              0

Capturing:                   not active
Capture audio:               not active
Capture screens:             0
Capture file:                /mnt/nfs/data/VirtualBoxVMs/Win10/Windows10/Windows10.webm
Capture dimensions:          1024x768
Capture rate:                512kbps
Capture FPS:                 25kbps
Capture options:

Description:
Windows 10 EDU
Guest:

Configured memory balloon size: 0MB
OS type:                     Windows10_64
Additions run level:         2
Additions version            6.0.12 r133076

Guest Facilities:

Facility "VirtualBox Base Driver": active/running (last update: 2019/11/25 11:27:53 UTC)
Facility "VirtualBox System Service": active/running (last update: 2019/11/25 11:28:43 UTC)
Facility "Seamless Mode": not active (last update: 2019/11/25 11:27:53 UTC)
Facility "Graphics Mode": not active (last update: 2019/11/25 11:27:53 UTC)

console output (nmap, iptables, VBoxHeadless)

Code: Select all

nmap output
------------------------------------
desktopcb:/etc/vnc # nmap 192.168.80.6
Starting Nmap 7.70 ( https://nmap.org ) at 2019-11-25 12:33 CET
Nmap scan report for  (192.168.80.6)
Host is up (0.0000070s latency).
Not shown: 989 closed ports
PORT      STATE SERVICE
22/tcp    open  ssh
111/tcp   open  rpcbind
139/tcp   open  netbios-ssn
445/tcp   open  microsoft-ds
873/tcp   open  rsync
902/tcp   open  iss-realsecure
2049/tcp  open  nfs
5000/tcp  open  upnp
5801/tcp  open  vnc-http-1
5901/tcp  open  vnc-1
16001/tcp open  fmsascon

Nmap done: 1 IP address (1 host up) scanned in 1.70 seconds 

------------------------------------
iptable output
------------------------------------
desktopcb:/etc/vnc # iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

------------------------------------ 
VBoxHeadless output 
------------------------------------
desktopcb:/etc/vbox # su -c 'VBoxHeadless -s Windows10 --vrde on --vrdeproperty "TCP/Ports"=3890-3895 ' -s /bin/bash christian

Oracle VM VirtualBox Headless Interface 6.0.12_SUSE
(C) 2008-2019 Oracle Corporation
All rights reserved.

MoTTY X11 proxy: Unsupported authorisation protocol
MoTTY X11 proxy: Unsupported authorisation protocol
xcb_connection_has_error() returned true
XDG_RUNTIME_DIR (/run/user/0) is not owned by us (uid 1000), but by uid 0! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
MoTTY X11 proxy: Unsupported authorisation protocol
MoTTY X11 proxy: Unsupported authorisation protocol
VRDE server is listening on port 3890.
MoTTY X11 proxy: Unsupported authorisation protocol
MoTTY X11 proxy: Unsupported authorisation protocol 

Next try:

Code: Select all

christian@desktopcb:~> VBoxManage controlvm Windows10 vrde on
christian@desktopcb:~>

Nothing changes ...

I'm really running out of ideas ...

(replacing VRDE with the VNC extension pack (and issuing "--vrdeextenpack VNC" + setting an VNC password) sort of runs:
first it's lying as well, but after "VBoxManage controlvm Windows10 vrde on" there suddenly is a VNC port listening and working
- but well, I don't want VNC to be installed on the machines accessing this headless VM, they should use mstsc only)

Any ideas?

[fth0]

Just a small hint: Your nmap command only scans the most commonly used TCP ports.

[scottgus1]

You also have a complicated command:

su -c 'VBoxHeadless -s Windows10 --vrde on --vrdeproperty "TCP/Ports"=3890-3895 ' -s /bin/bash christian

It's running with overrides to the default RDP settings in the main Virtualbox window's guest settings. It's running with a series of ports instead of just one, and it's running 'su'. (Linux noob alert, sorry: isn't running something 'su' like running a Windows program as Administrator?)

As a test, could you simplify this? Run just VboxHeadless with no su and no overrides, just one port using the guest's settings in the main Virtualbox window, and see if you can RDP into the guest.

Also, even though the open-port listing does not show the port range open, can you RDP into the guest anyway using the first command?

FWIW, running Windows programs as Admin opens more vectors for bad things to happen. Running Virtualbox as Admin is very carefully steered away from except in very special circumstances. Is running as 'su' also to be done carefully or perhaps not done if possible?

[socratis]

00:00:01.652793 VirtualBox VM 6.0.12_SUSE r132055 linux.amd64 (no date no time) release log

It looks like you're using the OpenSUSE-fork version of VirtualBox. You can either ask in their forums/channels for help, or completely remove/uninstall/delete/purge their version and install the official version from the Linux Downloads section of VirtualBox. You can even add VirtualBox as a repository, so you could use your traditional install/upgrade/uninstall tools.

00:00:02.097821 File system of '/mnt/nfs/data/VirtualBoxVMs/VBoxGuestAdditions_6.0.12_v2.iso' (DVD) is nfs

Do not download the Guest Additions (GAs) ISO separately, it's a recipe for a disaster. Always use the GAs that come already bundled with your VirtualBox installation. See Introduction to Guest Additions in the User Manual.


PS. For future reference you should ZIP your logs. It helps you, it helps us, it helps the server, it helps save a (virtual) tree or two...

[bofh42_2]

Just a small hint: Your nmap command only scans the most commonly used TCP ports.

I know . but the prots in question are included

[bofh42_2]

You also have a complicated command:

su -c 'VBoxHeadless -s Windows10 --vrde on --vrdeproperty "TCP/Ports"=3890-3895 ' -s /bin/bash christian

It's running with overrides to the default RDP settings in the main Virtualbox window's guest settings. It's running with a series of ports instead of just one, and it's running 'su'. (Linux noob alert, sorry: isn't running something 'su' like running a Windows program as Administrator?)

As a test, could you simplify this? Run just VboxHeadless with no su and no overrides, just one port using the guest's settings in the main Virtualbox window, and see if you can RDP into the guest.

Also, even though the open-port listing does not show the port range open, can you RDP into the guest anyway using the first command?

FWIW, running Windows programs as Admin opens more vectors for bad things to happen. Running Virtualbox as Admin is very carefully steered away from except in very special circumstances. Is running as 'su' also to be done carefully or perhaps not done if possible?

Yes, it overrides the settings because there is a real VNC running on the standard port.

It's using a rage because it didn't work with a single port, so this is another try.

"su" does NOT mean: running as root
it does mean "switch user". In this case it switches from "root" (excuting the command "su") to the user "christian" using /bin/bash as a shell. So it's just the opposite way around as you suggest.

"Run just VboxHeadless with no su and no overrides, just one port using the guest's settings in the main Virtualbox window, and see if you can RDP into the guest." - well, it did not work at all. That was the first thing I tried.

"Also, even though the open-port listing does not show the port range open, can you RDP into the guest anyway using the first command?" No, I can't. No way.


" Is running as 'su' also to be done carefully or perhaps not done if possible?" - well, you misunderstood the command completely. It does exactly the oppsite of what you are suggesting - in this case.

[bofh42_2]

install the official version from the section of VirtualBox. You can even add VirtualBox as a repository, so you could use your traditional install/upgrade/uninstall tools.

nope, I can't add it as a repository, because it does not exist (yet). There is a repository for OpenSUSE 15.0, but not for 15.1 yet. The 15.0 one does not work with 15.1 - that was the first thing I looked up - but: no luck.

Do not download the Guest Additions (GAs) ISO separately, it's a recipe for a disaster. Always use the GAs that come already bundled with your VirtualBox installation.

There are no GA for the Virtualbox Version coming from OPenSUSE. perhaps they are not allowed to redistribute them?

Well, I'll try the manually installed version - which is a pain when it comes to updating the system.

[socratis]

nope, I can't add it as a repository, because it does not exist (yet). There is a repository for OpenSUSE 15.0, but not for 15.1 yet.

Which reminds me to first check, and then post...

The 15.0 one does not work with 15.1 - that was the first thing I looked up - but: no luck.

Doesn't work in what sense? Where does it fail? Did you have a chance to try the test builds? Do these fail as well?

There are no GA for the Virtualbox Version coming from OPenSUSE. perhaps they are not allowed to redistribute them?

The distro-forked VirtualBox don't include them, I really don't know why. It's actually a sign that you're running the distro-forked VirtualBox, they try to download the GAs when you click on the "Insert Guest Additions CD Image..." menu entry.

[fth0]

Just a small hint: Your nmap command only scans the most commonly used TCP ports.

I know . but the prots in question are included

Why do you think so? Did you manually change the frequency values in the nmap-services file or use a different command line than the one you posted? Because otherwise, the TCP ports 3890-3895 are not scanned by nmap.

[scottgus1]

"su" does NOT mean: running as root....it does mean "switch user"

This could be the problem. Virtualbox is heavily tied into the user account the guests are registered under. (because the default storage folder for the main Virtualbox window's configuration files is in $HOME/.config/VirtualBox.) When a guest is run via vboxmanage, the guest must be registered in the account the vboxmanage command is run under, or the vboxmanage command will misfire. Could be that vboxheadless is the same behavior.

Re just running the guest headless without the 'su' add-on stuff, and a one-port RDP server running:

it did not work at all

Define this a bit more clearly? What exactly didn't work?

[scottgus1]

I don't have a Linux host, just Windows. So the below information may be moot if there is a difference between Windows and Linux behaviors of Virtualbox (I doubt there will be much).

I have a DOS guest that is set to have the Virtualbox RDP server on port 3391. I used this command on it:

vboxheadless -s DOS_6.22_B

The command reports:

Oracle VM VirtualBox Headless Interface 6.0.14
(C) 2008-2019 Oracle Corporation
All rights reserved.

VRDE server is listening on port 3391.

I can use Microsoft's RDP client to remote in on 127.0.0.1:3391.

Now I shut down the guest and try this command:

vboxheadless -s DOS_6.22_B -e "TCP/Ports"=3393

The command reports:

Oracle VM VirtualBox Headless Interface 6.0.14
(C) 2008-2019 Oracle Corporation
All rights reserved.

VRDE server is listening on port 3393.

MS RDP works on 127.0.0.1:3393.

Please log in on the account that your Windows10 guest is registered in the main Virtualbox window, and try the same commands on your host. What happens exactly?