VirtualBox

Opened 14 years ago

Closed 14 years ago

#5487 closed defect (fixed)

Identical names for port forwarding in machine.xml crashes VM at start

Reported by: User54321 Owned by:
Component: network/NAT Version: VirtualBox 3.0.12
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

While being lazy in configuring the port forwarding through NAT I added to the machines .xml config file the 6 lines (both 3 for SSH and HTTP):

      <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/HTTP/HostPort" value="9022"/>
      <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/HTTP/GuestPort" value="22"/>
      <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/HTTP/Protocol" value="TCP"/>

      <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/HTTP/HostPort" value="9080"/>
      <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/HTTP/GuestPort" value="80"/>
      <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/HTTP/Protocol" value="TCP"/>

Copy'n'Paste'd there where paired entries with identical "names"-Attribute, but different port configuration (both HTTP instead of SSH/HTTP). In this case, the VN crahes at bios boot time.

Although it is the user's fault, the VM should not crash directly but rather be tolerant on such an config error and follow a rule like "first port forwarding used" and display an error message.

Change History (1)

comment:1 by Frank Mehnert, 14 years ago

Resolution: fixed
Status: newclosed

Fixed as of VBox 3.1.0.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use