This change should fix issue 297 on the Razor issue list

Issue 297 on the Razor issues list was submitted by a KVM use who found that the 'lshw' command that is used by the Razor Microkernel to gather additional hardware information was hanging for them in a KVM environment unless they included the '-disable dmi' flag.  The changes in this pull request should fix that issue without having to resort to changes to Facter (which is how the user who submitted Issue #297 appears to have "fixed" the problem).  These changes have been tested in a KVM environment running under VMware Fusion; tests on real hardware have not been run (since I'm on an OS X machine, such tests are not possible, locally)