Hi JR,
I just figured out the problem. The VM does NOT allow you to enter IP addresses that have "0" in an octet.
I have seen this problem before on a UPS unit's SNMP management card. You couldn't configure the IP if it had a "0" octet. Likely a programming issue.
Anyways, I changed my 10.0.0.x network to a 10.1.1.x network and it finally took the values.
JR
I can confirm this is a bug. I'll get it fixed shortly and put out a new release.
More issues with this....
It seems like when rebooting either of my ESX hosts, whether sometimes doing clean shutdowns or simulating a server crash by pulling the plug, the 2 LVS nodes do NOT want to communicate anyone and do not even offer up iSCSI. When I try started the LVS nodes, the iSCSI storage never comes online. Furthermore, going into the LVS node menu and selecting Start Node never ends up synchronizing with the other node. The only thing it says is
" 0: cs:standalone st: secondary/unknown ds:consistent/dunkown r----
ns:0 nr:0 dw:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
resync: use: 0/31 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0
BOTH nodes are showingthe identical thing. Again, the iSCSI storage is not online.... The only way I can seem to fix this is to reset both nodes and reconfigure both nodes (I can't find a way OUT of that screen when it's trying to sync... ctrl-c, etc. nothing worked to get back to the menu...).
ON a side note, aside from THIS issue, I am having problems wiht the sole VM that is running on Node1. It's a Win2003 VM and is constantly crashing and becoming unpingable for no apparant reason.....
Is there ANY support available for this? I know it's free.. but I would like to introduce this to a couple clients, however I can't really do so if I'm having problems even getting this up and running.
Please advise. a bit frustrated with this...
Sorry for the delay spotting your posts, and some issues getting the XVS to work. Standalone mode is a state where the nodes are refusing to speak to eachother for some reason, usually a split-brain scenario. This seems likely because both nodes believe they are in a consistent state so you end up with a dead-lock. The reason the iSCSI storage won't come up is because in secondary mode the storage is read-only. You'll need to run some commands at the console to fix this state.
I've not seen these issues in my dev setup and have been using the XVS to host lots of test Windows VMs for some time without issue, so I'm sure we can fix the problems. Can you send me some details of your setup, the hardware you're running, exactly how you failed the node, etc, to support@xtravirt.com? I'll do my best to try and get you up and running.
Cheers,
Alex