TOPIC:

now im trying to create vm's on both the master and slave and i get error attempted an operation on on a VM that needed it to be in state 'halted' but was in state 'running'. on two out of 4 vm's in the creation phase...

guess what .... hard reboot on the slave server... and now the iscsi repository is broken again. i think at this point due to the lack of stability, support, and forum activity. its unfortuitly time to abort HA-lizard, and HA-ISCSI. Conceptionally and theorically this would have been a great solution to my production environment but the instabilities make it not an option. Maybe down the road when newer versions come out this might be able to be re looked at for our envirnoment.

Sorry to hear you have given up on this project. If you decide to revisit it again in the future you should consider paid support to get the installation completed.

its sad that it boils down to money to get this testing complete and up and running. how can i go to my boss and say that this setup isn't working. i have followed the setup multiple times step by step. and can replicate the issue but the only way i can have someone help me figure it out is to pay for support. why would i want to pay for something that im not positive even works?

anyone else on this forum have any ideas or desire to help. I would greatly appreciate it

So i have determined the issues that plagued my ISCSI backend from not connecting with the slave server after a reboot. So things are up and running again. If I take and do an orderly shutdown on my slave host the vm's now migrate over to the master. If I simulate a power failure on the slave host by pulling the plug the vm's do not migrate why is that. I thought that HA provided this am I wrong?