Saturday, October 25
If you're moving existing OpenVZ containers to a newer OpenVZ server, here are a couple of tips for things that might otherwise drive you insane:
## Filesystem layout for new CTs: either simfs or ploop
NETFILTER="stateful"If you also need NAT, use:
NETFILTER="full"Then things will work just like they used to.
Posted by: Steven Den Beste at Saturday, October 25 2014 10:25 PM (+rSRq)
I like OpenVZ because (a) it's lightweight and (b) the hypervisor level is an ordinary Linux kernel, and lets you see everything going on in all the VMs at once. If I was running virtual machines on someone else's platform, though, I'd want KVM or Xen precisely so they couldn't do that.
Posted by: Pixy Misa at Sunday, October 26 2014 01:01 AM (PiXy!)
Do you honest to Mog think I'm going to use software designed/implemented by morons with the engineering discipline of a 3-year-old with a set of duplo's?
Posted by: dkAllen at Tuesday, October 28 2014 05:18 AM (c/F3T)
Posted by: Steven Den Beste at Tuesday, October 28 2014 06:28 AM (+rSRq)
It was just that we've been running on SimFS for years, and I have migration procedures that work for that, and having the new server running Ploop by default messed that up.
Posted by: Pixy Misa at Tuesday, October 28 2014 08:42 AM (2yngH)
52 queries taking 0.1399 seconds, 281 records returned.
Powered by Minx 1.1.6c-pink.