![]() ![]() Or possibly a combination (cached translations). That's a great opportunity for Linux to feather in support of offering packages in LLVM IR format, with either a compile-to-native-binary during install (optimizing for the target platform) or a later binding, like at execution time. In the Linux world, there's adoption of multiarch support, which allows binaries for multiple architectures to be installed on the same filesystem. With today's maturity of LLVM, there's no reason for any of this. A) that leaves a lot of performance on the table, and B) it means the code will not run on other architectures. Generally, you end up compiling/targeting some kind of lower-common-denominator, by way of compiler flags etc. A lot of the current CPU-based power consumption in a datacenter is a waste because we don't employ this technique.ģ) Entire software distributions, all in LLVM IR format (i.e. So, accelerating migration equates to higher load capacity. If we could migrate VMs in zero seconds, we'd boost the load to near 100% all the time. Now let's think about why we run nominal loads at such low values - because of load spikes. It turns out this technique is very effective, especially for cases where there are lots of similar VMs. Given SAN or NAS, mostly you're transferring memory state. And then used that as a way to migrate a lot less VM memory, because a lot of the memory you need to transfer is already on the destination server. Imagine if you applied the concept of memory de-dup within a server, to equivalent memory identification across servers. And for some HPC apps, that's days or weeks.Ģ) Higher VM densities and big power savings using a software VM migration acceleration trick. Otherwise, this kind of parallel computing app gets stuck on a hardware node once it starts. And thus, the derivative technologies such as workload balancing (DRS) and power management (DPM). What's the VMware-like solution for OpenCL? Why not have a virtualized OpenCL which allows people to write GPGPU apps, but late-bind them to whatever hardware is available at the time? With virtualization at the layer between the "host program" and OpenCL device, that cracks the door open for live migration of GPGPU workloads, just like for CPU (ala vMotion). Hess: What are your ideas about the next generation of virtualization and data center computing?ġ) Virtualization for GPGPU. ![]() If you don't have a package deal, you don't have safety. Until then, it's really important that every piece have safety built in, and the solutions are thought out end-to-end. It's kind of a paradox-the less you trust it, the more safe it becomes. Then you can run on completely untrusted crap, and still have secure computing. Personally, I think one of the most exciting unsolved problems out there is to figure out how to run workloads without the hosting hardware/software having any clue what the workload is. But everything the VM touches, from the network equipment to the storage would have to be 100% in order to be really safe. Having a trusted secure path right from power on through boot is a start. Hess: How can we make cloud computing safer? I think that's a very rational reason for concern. And that hardware is potentially shared or adjacent to the hardware storing someone else's data. Lawton: It should be your data is on someone else's hardware. Hess: Why is security such a concern for cloud computing? ![]() I think ultimately these will be the same question. Bochs will allow you to run Win 95 and associated software on your Unix/X11 workstation, displaying a window on your workstation, simulating a monitor on a PC.Lawton: See answer above. For instance, let's say your workstation is a Unix/X11 workstation, but you want to run Win'95 applications. This allows you to run OS's and software within the emulator on your workstation, much like you have a machine inside of a machine. The 'typical' use of bochs is to provide complete x86 PC emulation, including the x86 processor, hardware devices, and memory. Bochs was originally written by Kevin Lawton and is currently maintained by this project.īochs can be compiled and used in a variety of modes, some which are still in development. Bochs can be compiled to emulate many different x86 CPUs, from early 386 to the most recent x86-64 Intel and AMD processors which may even not reached the market yet.īochs is capable of running most Operating Systems inside the emulation including Linux, DOS or Microsoft Windows. It includes emulation of the Intel x86 CPU, common I/O devices, and a custom BIOS. Bochs is a highly portable open source IA-32 (x86) PC emulator written in C++, that runs on most popular platforms. ![]()
0 Comments
Leave a Reply. |