[Computing]Local projects:- editline - jQuery plugins - readline_cpp - parse0x - ptsigslot - shellish - sqlite3x/sq3 - Tech papers - yo5 - zfstream Remote projects: - s11n.net - SpiderApe - toc Stuff for...: - gcc - GNU make - JavaScript - jQuery - QEMU - sqlite3 | Stuff for QEMUQEMU is an Open Source "machine emulator and virtualizer", similar in concept to more well-known projects like VMWare or Bochs. QEMU works remarkably well, performs remarkably well, and is easy to use (orders of magnitude easier to use than Bochs). This page contains some stuff which QEMU users may (or may not) find useful... Screenshot:Here's a screenshot of qemu running DamnSmallLinux and two different installations of Debian (one with X11 and one without):
(Hmmm... it seems the clocks are wrong in the debian installations...) Precompiled QEMU for 32-bit x86:The most vexing problem with qemu is that it cannot be compiled with gcc 4.x. Building it on *nix machines requires gcc 3.x, which has been long out of date. To simplify life for those who do not have gcc 3.x installed, here you can grab a precompiled binary. The package was built on a Kubuntu 7.04 box and "should" work on any Debian 4.0 derivative (Ubuntu, Edubuntu, etc.). It may or may not work on other Linuxes (Linuxis?). Unfortunately, the statically-linked qemu build would not build on my machine, so this binary requires some other shared libraries to be installed (libSDL, libdl, libdirectfb, libfusion, libdirect, libasound, and a few standard (or very common) system libraries).To install, simply unpack the tarball from your root directory. That will install the package under /opt/qemu, so as to not interfere with a system-installed package (typically qemu 0.8.x). qemu-0.9.0-debian4-x86_32-opt-qemu.tar.bz2 (4404214 bytes, last modified 2007.Jun.25) Empty image files:The qemu-img tool makes creating new "image files" (container files for qemu installations) trivial. My minor complaint with that tool is, however, that the created files are "sparse" (at least on filesystems which support this). That means that if you create a 2GB image file, it it doesn't actually take up 2GB of space (only the "used" parts of the file take up space) (again only on filesystems which support this). While admittedly a useful feature, it is also deceptive, in my opinion, because with it you can pack 500 files, each 4GB, on a 10GB hard drive, which is philosophically evil. So... here are a couple non-sparse image files which can be decompressed and used as qemu containers:
These files can also be used as Linux swap files, by the way. A tip for creating non-sparse image files with qemu-img: create a raw-format image as normal:
qemu-img create -f raw myimage.raw 500M
That will create a sparse file which doesn't really take up 500MB. To force it to be non-sparse, simply gzip it and then ungzip it. OS images:Below is a list of OS images i have prepared for QEMU. Note that most of them are "skeleton" images. That is, they are installed but probably not configured to do anything special. To use these images, simply decompress them (using the bzip2 or, for Windows platforms, 7-zip) and then run:
qemu [options] imagefile.raw
Before downloading: be aware that most of these files are huge - more than a gigabyte compressed and possibly up to 3-4GB uncompressed.
|