Search results

I used the standard kernel without the proxmox patches. If I get time at some point I might add in the firmware patches, but considering the stability right now, I don't see that as necessary.

I do not have to reinstall the kernel with each release of Proxmox, but yes the kernel did need patched to support the SPERC8 (shared storage array) NOT the local node storage. Each node is connected to a 1 gbps line. The bridge between the two chassis however are 2x100 mbps (temporarily), so...

In regards to your questions, I seem to be one of the only people currently discussing the use of these drivers. That being said, I have found them to be very stable in my current production environment since the installation of this kernel. The big drawback is that the only way to run these...

Did everything work out ok for you with the kernel?

Yes, the only source-code added during recompilation is the addition of the PERC8 storage driver, under megaraid_sas. The other issues I was referring to, are issues with the chassis KVM, and are simply precompile-time options set via make. ~xmo

No problem, I hope it helps. You can install it after the normal proxmox install, or if you prefer, you can install it on top of debian, and pull in the repos from proxmox. Either way should work just fine. I install on-top of proxmox, as that has only the required packages for the hypervisor...

This is the compiled kernel in deb format: http://www.filedropper.com/linux-image-31217-vrtx31217-vrtx-1000customamd64 I also have all the source and an installer for re-compilation in the future, should there be more kernel related updates that need to be done. The reason it's compiled on 3.12...

Ok, so here's the deal. The organization I work for was looking into purchasing some VRTX servers from Dell. Dell jumped around in circles explaining and refuting the support of the VRTX server on Linux. All the actual "blades" you can get (m520 for example) are in fact supported on Linux, only...