VirtualBox

Ticket #13532 (closed defect: worksforme)

Opened 6 years ago

Last modified 6 years ago

NAT#0: Configuration error: network '10.0.%octet1%/8' describes not a valid IPv4 network

Reported by: srondeau Owned by:
Component: network/NAT Version: VirtualBox 4.3.16
Keywords: Cc:
Guest type: other Host type: Linux

Description

This occurs in the log when starting a VM defined with NIC1 using NAT. There are many VMs using NAT at the time on different VMs; the actual message the user saw when using "VBoxManage startvm" is:

VBoxManage: error: NAT#0: Configuration error: network '10.0.30400107640ctet18' describes not a valid IPv4 network (VERR_INVALID_PARAMETER). VBoxManage: error: Failed to attach the network LUN (VERR_INVALID_PARAMETER) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Consol e, interface IConsole

I had this happen for two different VM users and two different guest OSes.

Attachments

VBox.log Download (33.4 KB) - added by srondeau 6 years ago.
VirtualBox log file

Change History

Changed 6 years ago by srondeau

VirtualBox log file

comment:1 Changed 6 years ago by srondeau

Although I could not figure out how to fix the problem, there is a workaround -- define a different NAT network; e.g.:

VBoxManage modifyvm ubuntu --natnet1 "10.1.2/24"

comment:2 follow-up: ↓ 3 Changed 6 years ago by frank

What is the output of 'VBoxManage getextradata ubuntu enumerate'? To me it looks like you tried to override the network using an invalid network specification.

Last edited 6 years ago by frank (previous) (diff)

comment:3 in reply to: ↑ 2 Changed 6 years ago by srondeau

Replying to frank:

What is the output of 'VBoxManage getextradata ubuntu enumerate'? To me it looks like you tried to override the network using an invalid network specification.

Although that command returned nothing, pointing the finger back in my direction made me think more about the error. I realized it was a user error, so this ticket can be closed.

comment:4 follow-up: ↓ 5 Changed 6 years ago by frank

  • Status changed from new to closed
  • Resolution set to worksforme

Thanks you for this information!

comment:5 in reply to: ↑ 4 Changed 6 years ago by srondeau

Replying to frank:

Thanks you for this information!

It could still be an error, since VBoxManage accepted an invalid configuration:

VBoxManage modifyvm ubuntu_250 --nic1 nat --natnet1 10.0.%octet1%/8

My script was supposed to replaced %octet1% with a valid octet before issuing the command, but didn't. So the IPv4 subnet specified was invalid. If it had not have been accepted in the first place, the VM would have kept its original settings and the user would seen an error message but would have been able to start the VM.

I changed my script to provide a valid octet, but I think syntax-checking in the --natnetx value would be beneficial.

comment:6 Changed 6 years ago by frank

Well, there could be a sanity check but OTOH VBoxManage is not the universal tool, it's more a helper for functions which are not implemented in the GUI and which require more low-level knowledge. So I don't expect that anybody has time to spend time to implement a proper check here.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use