Cloning a VM and using a different bridge

This qualifies as a bug report and feature request. I cloned a VM I had but want it to run on a local network rather than a global network. When the cloning a VM I am presented with an option to enter the IP and on what eth0/1 to use. I entered a local IP not thinking of the bridge. The machine cloned and came up in the webmin status etc. After seeing i could not SSH into it, I realized what I had missed - the bridge. I then used the System Configuration > Network Interfaces to try and change the bridge from br0 (global) to br1 (local). It just sits there spinning without ever completing. There should be an option on there for bridge as well when there are multiple available when cloning a VM. In order to fix it, I have to manually go into the terminal and edit the .cfg file and recreate via xm create xxx.cfg. It's not a big deal but seems as though it would be easily fixed.

So, for the feature recap - the bridge should be able to set on the clone a VM page. The bug recap - trying to change the bridge on this freshly cloned VM never completes (it may but I waited 5 minutes with no result and figured it times out)



Not an unreasonable suggestion - currently the clone is always on the same bridge as the original though. Was that not what you wanted?

Steffan's picture
Submitted by Steffan on Thu, 10/06/2016 - 23:07 Pro Licensee

Not in this case. I have 1 VM for a db and was cloning it a few times to run as slaves. I didn't want to waste global IPs for slaves only accessible through a MaxScale proxy.

I'll put this on my TODO list for new features..

Steffan's picture
Submitted by Steffan on Fri, 10/07/2016 - 10:08 Pro Licensee

Awesome! Thanks.

Can you think of any reason that the Network Interfaces panel would time out when trying to change that? Seems to only do that in this one case.

That seems like a different problem. Was the VM up or down at the time you tried to make this change?

Steffan's picture
Submitted by Steffan on Fri, 10/07/2016 - 10:23 Pro Licensee

It was running at the time I tried to change it. The funny thing is that the ifcfg-eth0 file was right inside the VM. The only thing that needed to change was from br0 to br1 in the /xen/domain.cfg file.

Changing the bridge would also come with an IP change though, right?

Steffan's picture
Submitted by Steffan on Fri, 10/07/2016 - 11:16 Pro Licensee

When I cloned the VM, it prompted me for the IP. I put in the address in there. The VM started up with that IP address but it was on the wrong bridge. I then tried to edit through Network Configuration and it timed out. I had to shutdown the VM through xm, edit the domain and then start it back up.