Search results

As I recall, IPv6 requires significantly less TCAM space for its routes than IPv4 did. 6500's with slightly less IPv6 TCAM can still hold out for some time as IPv6 begins to grow in adoption. But yes, itis a band-aid solution for the issue at hand. 

We're working on it now. Justin is working with Namecheap to get everything fixed up. When everything is put back as it should be and we've finished investigating, we'll be doing a release about this mess.

I remember reading multiple threads on LET about how SolusVM broke with it, but iirc they patched that quickly. We noticed a few minor hiccups with Feathur, but it was due to the switch to ploop for the default and the ploop libraries not being installed on the node. Turns out that doesn't work...

On the topic of virtualization optimization like OnApp does with the SSH key and such, newer versions of QEMU can be compiled to have a QEMU-agent that you run inside the virtualized guest (iirc there's a qemu-agent for Linux and Windows), which communicates using a virtual serial interface...

It's worth noting that if you do want to switch to ploop, if you change the VE_LAYOUT option, as people rebuild their VPSes or as new ones are created, they'll switch over without affecting the ones using simfs. Likewise for going the other way around. 

I have an HP ENVY 17t-j100 and I like it. Haswell i7-4702MQ, with an NVIDIA GeForce 750M in it. Great for gaming, and with a 1920x1080 17" display it's also pretty nice. It's a little BIGGER than I originally expected, but it still does fine for my uses. 

I like how it still affects WIndows 95, 98, ME, and 2000. But NOT NT 4.0.

Oh please. Red Star OS is best OS.

Some Intel i-series ones don't have it, despite being Haswells. Now, pretty much every Xeon should have it, and hosts SHOULD be using Xeon/Opteron processors for their nodes.  To answer OP's question, it should be fine for OpenVZ, Xen-PV, or any other CONTAINER based system. Where you'll run...

haveged is definitely a lifesaver. Newer servers have rrand on the CPUs (anything with an E3-xxxx v3 or newer IIRC), which also helps. OpenVZ environments are messy sometimes, and if the host node doesn't have a sufficient entropy pool, it can really bog everything down. OpenVZ HNs are also a...

Basically, OpenVZ is developed on the el5/el6 kernel lines that RHEL and CentOS use. Debian uses a different line (not the el lines). Thus, programs developed on and compiled against Debian kernels MIGHT not work properly with the kernels used by OpenVZ. 

Internet Explorer (since IE9) is actually somewhat decent. IE 9 finally started complying to Standards, and IE 10 and 11 improved compliance and features. IE11 is actually a decent browser. The increased competition from Firefox and Chrome finally got Microsoft to kick in to high gear on IE...

Try using inSSIDer to see if you've got others nearby using the same channels. Try turning all but one of your AP's off as well, especially if they're close by. The 2.4GHz band is just too crowded. As soon as I get my new laptop, I'm switching my home over to 5GHz (with 2.4GHz still mixed in for...

Any other homes/Wifi hotspots nearby? 802.11 is very prone to interference. If there are other Wi-Fi APs nearby on the same channel as yours, you'll get interference that screws with your signal. If you can, try using 802.11a (5GHz band), or 802.11n (5GHz band). 5GHz has MUCH less interference...

Intel's newer generation lines are pretty powerful even with low power consumption. The Celeron line is no powerhouse, but they're still pretty decent for their power consumption. The Atom CPUs are supposed to be even LOWER power consumption with decent performance. I remember I once replaced a...

If the external Hard Drive is connected over eSATA or USB 3.0, it should be decent. eSATA would be best in terms of the number of controller interfaces the data passes through. eSATA is handled directly through the SATA controller, while USB 3.0 has to go through multiple controller interfaces...

The issue is that a lot of Enterprise Applications only support Internet Explorer. Usually due to lazy or stupid coding decisions. Migrating off those platforms would be expensive, so they stick with IE. There's also the support and changes timeframe. Firefox and Chrome are CONSTANTLY changing...

The fact is that OpenVZ neglected to throw warnings when attempting to use --iptables (they didn't even provide a deprecation period...). ALSO, they didn't even add the ploop package to the dependencies list on the latest vzctl RPMs so it doesn't get installed automatically. We ran into issues...

Feathur supports CentOS for OpenVZ, and CentOS 6 or Ubuntu for KVM. Ubuntu 14.04 is HIGHLY recommended for KVM, as it ships a more recent version of QEMU than CentOS does. Ubuntu 14.04 ships QEMU 2.0.0 compared to CentOS and its qemu-kvm 0.12.1.2 which is quite positively ANCIENT. 

If it is on an OpenVZ container, contact the host. They need to sync the host node's clock. It it's some other virtualization method, from SSH do "ntpdate time.nist.gov" to sync the clock, then try sertting up NTP in WHM.