So, I stored via Cloudmin a virtual kvm server, and, restored onto another machine. Each of our systems have TWO ethernet ports, so, there is a br0 and a br1. Each of two servers restored onto a new system, showed no second port after the restore.
In looking at the file under /etc/webmin/servers, the *.serv file, I see the following discrepancy:
Original line:
kvm_net=tap,vlan=0,script=/kvm/testfeeds.cloudmin.commservhost.com-eth0.sh tap,vlan=1,script=/kvm/testfeeds.cloudmin.commservhost.com-eth1.sh
From the restore to machine:
kvm_net=tap,vlan=0,script=/kvm/testfeeds.cloudmin.commservhost.com-eth0.sh
Of course. the files were missing as well under /kvm (these are from source machine):
-rwxr-xr-x. 1 root root 457 May 13 08:49 /kvm/testfeeds.cloudmin.commservhost.com-eth1.sh -rw-r--r--. 1 root root 5 May 13 08:49 /kvm/testfeeds.cloudmin.commservhost.com-eth1.tap
Comments
Submitted by JamieCameron on Sun, 05/24/2015 - 18:02 Comment #1
When you did this restore, did Cloudmin have to re-create the VM on the new host? Or were you just restoring over an existing VM?
Submitted by sfatula on Sun, 05/24/2015 - 21:11 Comment #2
This was a move, so, it was creating new VM on the new host. Used the cloudmin restore function, nothing special. And, cloudmin backup function on original machine. Both were lvm.
Submitted by JamieCameron on Mon, 05/25/2015 - 18:07 Comment #3
Was this second interface added when the VM was originally created, or did it only get added later on?
It looks like Cloudmin currently only restores the number of interfaces that existed when the VM was first created (which seems like a bug).
Submitted by sfatula on Mon, 05/25/2015 - 18:24 Comment #4
I wouldn't know, it would have been created at least a year ago.
Submitted by JamieCameron on Mon, 05/25/2015 - 18:34 Comment #5
Looking through the code, I have confirmed that adding the interfaces in that order will cause this problem. I will be fixed in the next Cloudmin release though.
Submitted by Issues on Mon, 06/08/2015 - 18:37 Comment #6
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Mon, 06/08/2015 - 18:37 Comment #7
Automatically closed -- issue fixed for 2 weeks with no activity.