B00TK1D's questions

This is a multi-step question, so bear with me.

I am considering building a small (10 - 20 node) cluster. However, I want normal programs (not designed for clusters) to be able to take advantage of the extra processing speed. In the most ideal scenario, I would like to be able to run a single hypervisor over the whole cluster. As far as I can tell, there is not a good solution to this problem that can take a normal program and run it faster on a cluster.

Therefore, I am brainstorming how I would go about designing such a system, and if it is feasible to attempt. It seems that the inherent problem with clustering is that it takes more time to move data around than it does to process it. (i.e. it takes 2 seconds to transfer a problem from one node to another, but only 1 second to solve it on the first node.) However, I have thought of a possible solution for this.

Let's just say that it is theoretically possible for all the nodes in a cluster to boot off of the same disk. Therefore, they all have direct access to identical data and identical programs. Secondly, let's suppose that the Linux kernel could be modified to send each new command to a different slave node, looping infinitely through all the nodes. Given these two conditions, a user can log into the terminal of the master node and run commands in a normal (non-cluster oriented) format, but the load of the commands will be more or less evenly spread across the cluster.

So with that introduction, here are my two questions:

1. Is it possible to create such an environment in which all the computers boot off of a single disk (probably a NAS)? (I am aware of PXE, but as far as I can tell it does not provide persistent storage, it only hosts the OS.) If it is currently possible, how can it be done?
2. Is it possible to modify the kernel to delegate each new command to a separate node? (This may be able to be done by modifying the bash binary instead of the kernel itself - I am not sure.) If so, please expound on how.

That's the most complicated question I have ever tried to ask on Stack Exchange, so I expect people to have questions in the comments. However, if this solution could actually be implemented, it could potentially revolutionize virtualization.

The title says it all. I am trying to troubleshoot a problem with the battery in a BBU RAID cache. During POST, an error is given something to the effect that the battery is low, the RAID cache is temporarily disabled and will begin working once the battery recharges. The battery is a 3.6v Ni-HM rechargeable battery, but when I take it out and measure its voltage, it is around 5v, no load. Originally, I assumed that this was because it was not under load, but as it turns out it reads the same voltage when I power on the server. This is very confusing to me, that a dead battery would have a higher voltage than it is supposed to.

I only run the server for around 6 hours each day. Is it possible that the battery discharges over night?

As a side note, I have tried connecting a pack of two AA batteries in place of the 'official' battery, but still don't have any luck. (By the way... If you ever do that, don't use alkaline batteries. They explode. You have to use rechargeable batteries. I speak from experience.)

I really need the extra performance boost of the cache, and so am willing to run the server 24/7 to keep the battery charged, but I don't want to if I don't have to.

For Clarification, my server is an HP Proliant ML350, with an HP Smart Array E200i RAID controller.

This is a question that has been bothering me for a while, and I can't seem to find anything online that talks about it. I have a server running VMware Hypervisor ESXi. When I boot up virtual machines on it, they usually take 2-3 minutes to boot up; not a terribly long time, but not instantaneous. However, when I look at the performance logs on the server, neither processor, RAM, or disk usage is around 100%; usually they average around 60%-80% So if the server has work to do, why doesn't it do it at 100%?

It seems to me that at any given moment, the component that is limiting performance should run at 100%. For example, if I have a really slow hard drive, then it should almost always run at 100%. Therefore, at least one of the areas (processor, RAM, disk, and network) should always be at 100%, unless the server is at a complete idle.

Why isn't this the case?