The quick background on what I am trying to accomplish:
I have multiple-node per chassis rack units. I am trying to remove the top chassis and replace with newer hardware. As a result, I am trying to move all VMs to the second chassis.
Here is the basic setup
Chassis - Node - What is on node
Chassis0 - Prox1 - old home of vbulletin VM
Chassis1 - Prox2 - WordpressVM
Chassis1 - Prox3 - Prox3 - new home of vbulletinVM
The vbulletin VM is given a static route to the internal (10.0.x.x) IP address of the CentOS VM. Triple checked this.
We copied the drive from Prox1 to Prox3 and I can confirm that it is on the local directory for Prox3:
I can also see that it is using CPU memory on Prox3 and I can see it running in the web interface on Prox3.
The issue
When I shutdown Prox1 the following happens:
Prox2 - wordpressVM works fine
Prox3 - vbulletinVM becomes inaccessible
Any ideas? I have read a bunch of documentation but cannot find a lead as to what this might be.
I have multiple-node per chassis rack units. I am trying to remove the top chassis and replace with newer hardware. As a result, I am trying to move all VMs to the second chassis.
Here is the basic setup
Chassis - Node - What is on node
Chassis0 - Prox1 - old home of vbulletin VM
Chassis1 - Prox2 - WordpressVM
Chassis1 - Prox3 - Prox3 - new home of vbulletinVM
The vbulletin VM is given a static route to the internal (10.0.x.x) IP address of the CentOS VM. Triple checked this.
We copied the drive from Prox1 to Prox3 and I can confirm that it is on the local directory for Prox3:
Code:
root@proxhv03:~# find / -name vm-102-disk-1.raw
/var/lib/vz/images/102/vm-102-disk-1.rawThe issue
When I shutdown Prox1 the following happens:
Prox2 - wordpressVM works fine
Prox3 - vbulletinVM becomes inaccessible
Any ideas? I have read a bunch of documentation but cannot find a lead as to what this might be.