And here's another mind blower: If you have a machine with a VMX enabled CPU, you boot it to RHEL5, and cat /proc/cpuinfo, everything works as expected. If you boot that same machine to RHEL4, it masks the VMX flag.
Actually, what happens is that /proc is created at boot time. The cpuinfo file is created and formatted, based up on the kernels interpretation. Sine VMX wans't around in RHEL4 days, it doesn't know how to translate the bits and bytes of the flag.
Thursday, January 15, 2009
VMX Disabled in BIOS
I was trying to build out a full-virt VM, and was disappointed to find get an error:
Then I learned a new trick. When we cat /proc/cpuinfo, we are looking straight into the CPU. But... That doesn't mean a feature isn't disabled either in the BIOS or on the motherboard. To see what the system's capabilities, we have to go to /sys. In this case we need to:
On the HP I was working on, virtualization was disabled in the BIOS. That seemed strange, until a co-worker found the setting in the BIOS security settings. Oh, that makes sense-- VM's are a security risk. Either that or it cuts into the number of physical machines HP sells.
Now that it is enabled in BIOS, we get:
In all fairness, it's not only an HP issue. I found that Compaq is disabling this also.
What's that you say? They are the same company? Nooooo.
Can't do --hvm on this system: HVM guest is not supported by your CPU or enabled in your BIOSI knew that wasn't right: vmx showed up in the cpu flags.
Then I learned a new trick. When we cat /proc/cpuinfo, we are looking straight into the CPU. But... That doesn't mean a feature isn't disabled either in the BIOS or on the motherboard. To see what the system's capabilities, we have to go to /sys. In this case we need to:
$ cat /sys/hypervisor/properties/capabilitiesIf vmx was working, we'd see a list of hvm capabilites. (Remember: vmx and svm are proprietary, hvm is open.)
xen-3.0-x86_32p
On the HP I was working on, virtualization was disabled in the BIOS. That seemed strange, until a co-worker found the setting in the BIOS security settings. Oh, that makes sense-- VM's are a security risk. Either that or it cuts into the number of physical machines HP sells.
Now that it is enabled in BIOS, we get:
$ cat /sys/hypervisor/properties/capabilitiesMolto bueno.
xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
In all fairness, it's not only an HP issue. I found that Compaq is disabling this also.
What's that you say? They are the same company? Nooooo.
Monday, January 12, 2009
Who put that there?
Top 10 Evil Computers
From Wired, Top 10 Evil Computers. I'm suprised Number 10 wasn't Number 1, but then I guess I'm old. So old, in fact, that my favorite is Number 3. (Cool YouTube link.)
Sunday, January 04, 2009
Effects of Automobiles on the Atmosphere
Meteorologists stated that the US climate model changed after the grounding of commercial aircraft as a result of 9/11. Once the aircraft were back in the air, the model changed back. Now, NASA has evidence as to the degree of impact that automobiles are having an effect on the atmosphere.
For two months prior to the summer olympics, the Chinese government banned cars from Beiging, The effect was a 50% reduction in toxic output. Why only 50%? They still ran buses, trains, and cargo trucks.
For two months prior to the summer olympics, the Chinese government banned cars from Beiging, The effect was a 50% reduction in toxic output. Why only 50%? They still ran buses, trains, and cargo trucks.
64-bit Flash 10 on Fedora 10
I just tried to load the Flash Player for F10 x64, with no luck. Several pages lead me down the wrong paths, including downloading a TAR, and directly importing the SO. I found a post by Naresh Kumar who said to drop the SO in:
~/mozilla/pluginsrather than
/usr/lib/mozilla/pluginsNow it works.
Subscribe to:
Comments (Atom)