From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FyG5F-0002hi-VF for qemu-devel@nongnu.org; Wed, 05 Jul 2006 18:43:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FyG5E-0002gu-B1 for qemu-devel@nongnu.org; Wed, 05 Jul 2006 18:43:01 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FyG5E-0002gd-5m for qemu-devel@nongnu.org; Wed, 05 Jul 2006 18:43:00 -0400 Received: from [195.228.240.50] (helo=mta01.mail.t-online.hu) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FyG5H-00023m-El for qemu-devel@nongnu.org; Wed, 05 Jul 2006 18:43:03 -0400 Date: Thu, 06 Jul 2006 00:41:49 +0200 Subject: Re: [Qemu-devel] No useful documentation. From: NyOS Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-2 MIME-Version: 1.0 References: <1152133046.8295.85.camel@Agape-desktop> <20060705212524.GA27733@mail.shareable.org> <1152135526.8295.107.camel@Agape-desktop> Content-Transfer-Encoding: Quoted-Printable Message-ID: In-Reply-To: <1152135526.8295.107.camel@Agape-desktop> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: daniel.carrera@zmsl.com, qemu-devel@nongnu.org Hi! --------------------------------------- Let's see an example: installation. Qemu is a virtual machine program. So, that's a machine in the machine. There is a computer, called "host", which runs an OS, called Host OS, an= d = Qemu (besides other programs). Qemu is a simple program from the host point of view. To use it, you need at least one disc image. You can create one with the= = qemu-img command: e.g.: qemu-img create my_os.img 2G That will create a simple file (2GiB size), called my_os.img Suppose you have an install iso image, called my_os_install.iso The following command: qemu -cdrom my_os_install.iso -hda my_os.img -boot d will run a virtual machine. It will have two drives, the primary master = is = that 2GiB image. The secondary master is that cdrom image. Note that (from the host point of view) those are still two plain files.= = But from the guest OS (running in the VM), those are real drives. So, the virtual machine is started. It shows in a window what would be = shown in the monitor if that was a real hardware. First you probably need to create partitions, format them, run installer= = to copy files, and so on. If it needs to reboot the guest, feel free to = do = that, Qemu will not stop working. If you don't like windowed mode, press ctrl-alt-f to go fullscreen. When= = you'd like to use your host OS, press ctrl-alt to release mouse grab. Yo= u = can return to the VM any time. When you stop guest OS, and the virtual machine halts, Qemu exits. But t= he = image file is modified (the guest OS remains on that), so, you don't hav= e = to reinstall it every time. If you want, you can compress that to backup, or do anything. Note that closing the VM window is like unplugging the computer. It migh= t = explain next time. 2nd example: adding sound and user networking, and some more memory. qemu -m 256 -soundhw sb16 -hda my_os.img -localtime -net nic -net user -m 256 allocate 256 MiB RAM for the guest (read note) -soundhw sb16 just like putting a soundblaster card into the slot -localtime in case the host OS runs in local time (and not GMT) -net nic -net user called "user mode" networking, which is the simplest way to reach intern= et = from inside. It just works (getting IP address from DHCP automatically)= (If you call qemu without parameters, it will show its possibile paramet= er = list) note: on some systems, you need the following commands (as root) to add = = more memory: umount /dev/shm mount -t tmpfs -o size=3D512m none /dev/shm 3rd example: making kqemu working (I'm not sure, please correct it) (as root) type the following: mknod /dev/kqemu c 250 0 if it worked, the ls -al /dev/kqemu command would answer like that: crw-rw-rw- 1 root 250, 0 Mar 31 01:00 /dev/kqemu call modprobe kqemu to load kqemu kernel module (later you might install it somwhere into = /lib/modules/...) If you start Qemu now, it will probably run significantly faster. --------------------------------------- Use that 'doc' for whatever purpose you want. I don't need it anymore :)= . (but please ask a native speaker to rewrite it :) )