On Sun, 2011-04-03 at 14:25 -0400, Kyle Gonzales wrote: > > > I have had experience with using Dell DRAC cards in servers since 2003, > but the feature has been available since 2001. HP iLo has been > available since at least 2002, and has been standard in their enterprise > servers since 2006. So these types of features have been available for > nearly 10 years.
Why don't you do a hands on presentation on Linux disaster recovery using DRAC or iLO? > Do older servers have the necessary processor extensions to use KVM? > Probably not. However, let's keep in mind that AMD has released > processors for the server and desktop space that support hardware > assisted virtualization since 2006. Intel first released theirs in 2005. > > Source: http://en.wikipedia.org/wiki/X86_virtualization > > So older kit is 5+ year old systems. Alternatively you will run into > issues with systems built with non-enterprise class processors/boards > within the past 5 years. And what is RHEL's life cycle? 5+ year old hardware can easily still be in use. Considering RHEL 3 won't be EOL till 2013, the EOL life cycle has begun. That won't happen for RHEL 4 till 2012. https://access.redhat.com/support/policy/updates/errata/ > As for the laptops, the issue is usually with consumer laptops which > either do not have processors with VT extensions or whose firmware does > not allow it. Business grade laptops, like Thinkpads, do not generally > have this issue. I believe even laptops from Linux friendly vendors > like System76 make sure they are virtualization friendly. I had an IBM > Thinkpad with a Core 2 Duo processor that contained virtualization > extensions in 2007. Ran KVM without issue. That was 4 years ago. What laptop do you presently have now? What OS is that running? -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com --------------------------------------------------------------------- Archive http://marc.info/?l=jaxlug-list&r=1&w=2 RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml Unsubscribe [email protected]
