New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
KVM Node: Network not responding
Hi,
I have a node problem node with KVM virtualization. I install VPS with linux OS but network is not working. Its created using SolusVM and I assign failover IP to VPS.
Its a SoYouStart dedi.
ifconfig from node: http://pastebin.com/20SxS3zW
iptables from node: http://pastebin.com/gU2xvdKb
ifconfig from kvm vps: http://pasteboard.co/27mZaE62.png
eth0 from kvm vps: http://pasteboard.co/27n0w0CZ.png
VPS is running, only problem is network... I tried to ping IP but 'request timed out'.
Any help?
Comments
Did you check network config of the VPS once , also if dhcpd or dhcp is running fine ?
Conact SolusVM support and tell them to install it for you.
Or follow these guides:
https://www.lowendtalk.com/discussion/36845/kvm-on-ovh-sys-using-recommended-configuration-with-virtualizor-solusvm
https://www.lowendtalk.com/discussion/32361/installing-configuring-kvm-on-ovh-with-solusvm
Anyways, if you find any solution, tell me also. I am also suffering from the same problem.
my guess is kvm guest network is not responding, not node
did you guys assign mac addresses to the IPs?
Yes, also network bridge is setup from this https://documentation.solusvm.com/display/DOCS/KVM+Bridge+Setup
Please give the output of route -n.
That's a thing?
Yes. That's the thing he can do...
What OS are you using? CentOS 6 or 7?
Yeah, centos 6
What about SolusVM support ?
You can try to assigning IP to the VM via DHCP and run the following command on the host node:
killall dnsmasq
/etc/init.d/dhcpd start
/etc/init.d/dnsmasq start
Restart the VM and check again.
For OVH/SYS with singular /32 IPs you have to set (assuming you have configured bridge correctly)
ovh_bridged_network_routes = true in usr/local/solusvm/data/config.ini
The configuration for each IP should be as following
Netmask = 255.255.255.255
Gateway = xxx.xxx.xxx.254 (IP of your main server but last octet replaced with 254)
Make sure you also generate MAC for each failover IP & enter it in SolusVM as well.
If you need further help, contact SolusVM & ask for your ticket to be escalated to L3 support.
nah, LowEndHelpDesk is always better than SolusVM support
If is so youstart you need to do like this example.
IP 10.10.10.20
Netmask 255.255.255.0
Gateway 10.10.10.254
Also you need to setup a mac for the IP, and also to update your MAC in solusvm, else it will not work.
Netmask must be 255.255.255.255 or OVH might nullroute your IP for sending too many arp requests. That used to happen a lot with people were new to creating VMs on OVH servers but it is possible that OVH might have become a little lenient with it because I still hear or read from time to time about same thing happening to someone but not as much as in the past though.
also with ovh you may not use it as it may now work, so you do have use the ip they will give you from your block.