By Chris Kawalek on Aug 02, 2013
Happy Friday! Our tip this week is on a little quirk of using Oracle VM 3 with templates developed in Oracle VM 2.
Why do I see new Oracle VM 3 networks named xenbr0 and xenbr1 after importing an Oracle VM Template?
Answer by Gregory King, Principal Best Practices Consultant, Oracle VM Product Management:
Some legacy Oracle VM Templates as well as some newer templates are designed to come pre-configured with network interfaces for Oracle VM 2 environments. Oracle VM 3 doesn’t really know what to do with the pre-configured network devices during the import process of an Oracle VM Template, so the product errors on the side of caution by creating place holders for networks.
This means Oracle VM 3 automatically creates superfluous or false networks using the name of xenbr0, xenbr1, etc. when you import an Oracle VM Template that uses the Oracle VM 2 naming convention for bridges. So you are left with new networks named xenbr0 or xenbr1 that are useless since they are not associated with any servers, network ports or bonds. This can be quite confusing.
The problem is very easy to fix. Simply edit the newly imported Oracle VM Template, replace the networks named xenbr0 and xenbr1 with your real networks, then switch to the Network tab, highlight the networks named xenbr0 and xenbr1 and then delete them.
Here is a step-by-step example...
The next screen shot shows the superfluous networks after the new template has been imported:
The networks named xenbr0 and xenbr1 can safely be removed after they are no longer being used by the newly imported Oracle VM Template. Simply switch to the Repositories tab, find and edit the newly imported template as show in the screenshot below:
Finally, switch to the Networking tab, highlight and then delete the networks named xenbr0 and xenbr1 as shown in the screenshot below:
...and now your Oracle VM networks should look just like they did before importing the template :-)
We'll see you all next week with another tip!