-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
I made a typo while using unet-provision! Help!
This used to be unrecoverable. Now you can just try again.
One or more uNET nodes shows a status of "parent_to_be" or "child_to_be".
Make sure that the VMs are all in "Bridged Adapter" AND that the NIC card chosen in the "Attached to" popup below is the same on all VMs. There appears to be an error in the Bridged Adapter that blocks certain traffic otherwise. TBD
The topology / visibility of 3 or more nodes is confusing or inconsistent.
Because VirtualBox snapshots store the complete state of the machine, which includes information about the other uNET VMs and their relationships, it's possible for these states to be out of sync with each other. If you reboot all the VMS at (roughly) the same time, or shut them all down and then boot them back up, they will achieve consensus about the state and topology. This is an edge case (time-travelling VMs, essentially) but we are workin on scripts to make it easier to deal with since VM simulations are an important part of our testing. TBD
The mouse pointer / cursor disappears in my VirtualBox VMs
This is an infuriating bug new to the latest VirtualBox release. We've found that "hiding" the VMs for a few minutes and then bringing them forward SOMETIMES fixes the problem. You can then save a Snapshot (under the Machine menu) and restore to that snapshot whenever you relaunch the VM. Not a great work-around, we're hoping to find a better solution.