Vrde property "TCP/Ports" is ignored in IPV6

Bug #1822996 reported by Nico Orrù
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have multiple VMs on a host, I need a separate VNC port for the consoles.

Unfortunately, I can't set TCP ports for ipv6, as the settings appears to be ignored.

$ sudo su - vbox -c 'VBoxManage modifyvm test_machine_1 --vrdeproperty "TCP/Address=0.0.0.0"'
$ sudo su - vbox -c 'VBoxManage modifyvm test_machine_1 --vrdeproperty "TCP/Ports=5901"'
$ sudo systemctl start vboxvmservice@test_machine_1.service
$ sudo systemctl status vboxvmservice@test_machine_1.service
● vboxvmservice@test_machine_1.service - VBox Virtual Machine test_machine_1 Service
   Loaded: loaded (/etc/systemd/system/vboxvmservice@test_machine_1.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-04-03 11:39:05 UTC; 4s ago
  Process: 7195 ExecStop=/usr/bin/VBoxManage controlvm test_machine_1 savestate (code=exited, status=0/SUCCESS)
 Main PID: 7521 (VBoxHeadless)
    Tasks: 37 (limit: 4915)
   CGroup: /system.slice/system-vboxvmservice.slice/vboxvmservice@test_machine_1.service
           ├─7521 /usr/lib/virtualbox/VBoxHeadless -s test_machine_1
           ├─7531 /usr/lib/virtualbox/VBoxXPCOMIPCD
           └─7536 /usr/lib/virtualbox/VBoxSVC --auto-shutdown

Apr 03 11:39:05 systemd[1]: Started VBox Virtual Machine test_machine_1 Service.
Apr 03 11:39:05 VBoxHeadless[7521]: 03/04/2019 11:39:05 Listening for VNC connections on TCP port 5901
Apr 03 11:39:05 VBoxHeadless[7521]: 03/04/2019 11:39:05 Listening for VNC connections on TCP6 port 5900

$ sudo su - vbox -c 'VBoxManage modifyvm test_machine_2 --vrdeproperty "TCP/Address=0.0.0.0"'
$ sudo su - vbox -c 'VBoxManage modifyvm test_machine_2 --vrdeproperty "TCP/Ports=5902"'
$ sudo systemctl start vboxvmservice@test_machine_2.service
$ sudo systemctl status vboxvmservice@test_machine_2.service
● vboxvmservice@test_machine_2.service - VBox Virtual Machine test_machine_2 Service
   Loaded: loaded (/etc/systemd/system/vboxvmservice@test_machine_2.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-04-03 11:59:05 UTC; 4s ago
  Process: 7216 ExecStop=/usr/bin/VBoxManage controlvm test_machine_2 savestate (code=exited, status=0/SUCCESS)
 Main PID: 9073 (VBoxHeadless)
    Tasks: 24 (limit: 4915)
   CGroup: /system.slice/system-vboxvmservice.slice/vboxvmservice@test_machine_2.service
           └─9073 /usr/lib/virtualbox/VBoxHeadless -s test_machine_2

Apr 03 11:59:05 systemd[1]: Started VBox Virtual Machine test_machine_2 Service.
Apr 03 11:59:05 VBoxHeadless[9073]: 03/04/2019 11:59:05 Listening for VNC connections on TCP port 5902
Apr 03 11:59:05 VBoxHeadless[9073]: 03/04/2019 11:59:05 rfbListenOnTCP6Port: error in bind IPv6 socket: Address already in use

I have tried to change `VNCPort4` `VNCPort6` `TCP6/Ports` properties to no avail.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: virtualbox 5.2.18-dfsg-2~ubuntu18.04.3
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Wed Apr 3 11:41:42 2019
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: virtualbox
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.virtualbox: 2019-03-27T15:50:37.875303

Revision history for this message
Nico Orrù (nigu-orru) wrote :
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Can you please tell me if:
1) it works with latest vbox6 version
2) it is reproducible with the upstream deb file

Changed in virtualbox (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]

Changed in virtualbox (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.