What like? i have setup the ip config on the VM itself, Let me make myself clear its not just linux where the problem is its Windows Hyper v too.
can't really say about windows, but for Linux, you got great tools like tcpdump and such, test the interconnectivity from the host node to the VM , see if its moving packets out trough the network port to start with.
you might need to set your ip route config in some cases.
as for windows, use netmask 255.255.255.255 or you will get null-routed pretty quick
are you going to use the vmac option? or going to use the bridged mode?
You won't get null-routed for 255.255.255.0 masks in a Windows VM, at least if you do it right...
I've been stuck with that whole Failover dilemma for a while too (still have 1 of those cheapass 50 euro boxes there) and, at least for Hyper-V (shouldn't be hard to do it for any other solutions), all you need to do is:
-Go to your manager
-Select the server
-Go to services
-Go to Virtual MAC for VPS
-Go to Associate a virtual MAC to an IP address
-Select the right IP, give it a random name, Set Virtual Mac type: to VMWare, Create a new one and click Validate
Then in Hyper-V:
Add a Virtual Network -> External, set to the main physical network adapter (and select Allow management OS to share this network adapter).
For Linux VM:
add a Legacy Network adapter and set the MAC Address to static and fill in the given MAC address from the manager's Virtual MAC.
For Windows VM:
add a (normal) Network adapter and set the MAC Address to static and fill in the given MAC address from the manager's Virtual MAC.
Then once in the OS set the IP to the failover IP, the subnetmask to 255.255.255.0 and the gateway to XXX.XXX.XXX.254 say 123.456.789.123 would become 123.456.789.254.
I'm 100% confident that it works like that...
(If you really don't get it working I have no issues setting 1 up for you as an example, toke me 5 minutes to setup an Asterisk server today for testing)
Last edited by Robert vd Boorn; 02-25-2011 at 12:43 PM.