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.
Comments
I'm pretty sure KVM wouldn't work without some special setup of the network interfaces as I doubt those extra IPs support virtual MACs which you need for OVH VMs. You could do OVZ though, shouldn't be an issue.
Yup, I'll give it a try tomorrow
Afair all extra IPs at OVH support virtual MACs...
For OVH VPS SSD line extra IPs are 2€/mo
Are you sure?
https://www.ovh.com/us/vps/vps-geolocation.xml
If you pay in USD, then it is $3. Point is it is not onetime fee for VPS SSD plans.
How would the performance be?
Add up to 16 IP addresses with geolocations in the US and Canada. Each IP is billed $3.00 during installation, you can attach IPs from different countries to a single VPS, whatever the model.
It's bill $3/ip for the first 16 I believe then it's $3/mo.
Well, maybe you're right.. They just don't state that as FREE 16 IPs like they do for their SYS or OVH dedicated servers.
Ovh vps free IPs? Does this mean I can transfer my 12 v4 from SYS to OVH VPS?
Disk space is too limited imo. And 100mbit isn't ideal for SSHFS mounts either.
I'm just trying this, but now I am stuck here:
Don't know how to solve this. The IP is attached to the VPS.
Just wanna to know if there is an update?
Depends on what you want to do.
OpenVZ/LXC is possible, but you can't create virtual MAC's for OVH VPS Failover IPs, so you are stuck with using NAT.
Or ARP Proxy if you want to give your nested VM a public IP. No need to create a virtual MAC.
Basically you create a bridge (e.g. br0) with your main public IP assigned, enable ARP Proxy on br0, enable IP Forwarding, create the nested VM with network configured as bridge (br0), set your failover IP and use your main public IP as your gateway.
Oh and don't forget to add the route to your VM from your host.
If you ever get this sorted out, I'm in for a small box to play around and idle. PM me the price if necessary.
I'm posting this here for prosperity and archive purpose...
Well, I know it's been a long time but I did just install OpenVZ on OVH Cloud S1-8 (sandbox) with perfectly working failover IPs. So, I wanted to share my results.
I used the @jarland ovz scripts and it went very well. Then I installed the OVZ Web Panel, which is a bit dated but suit my needs (no clients here:)
Then I linked some Failovers to the sandbox (no MAC required), then added the Failovers to the ovz panel et voilà.
The container ping from the outside world without issues ;-)
Let me know if you have any questions.
The container bench.sh: