qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: NyOS <lista@nyos.homelinux.net>
To: daniel.carrera@zmsl.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] No useful documentation.
Date: Thu, 06 Jul 2006 00:41:49 +0200	[thread overview]
Message-ID: <op.tb8mnzwat9pcbo@mail.chello.hu> (raw)
In-Reply-To: <1152135526.8295.107.camel@Agape-desktop>

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, and  
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. You  
can return to the VM any time.

When you stop guest OS, and the virtual machine halts, Qemu exits. But the  
image file is modified (the guest OS remains on that), so, you don't have  
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 might  
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 internet  
 from inside. It just works (getting IP address from DHCP automatically)

(If you call qemu without parameters, it will show its possibile parameter  
list)

note: on some systems, you need the following commands (as root) to add  
more memory:

umount /dev/shm
mount -t tmpfs -o size=512m 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 :) )

  parent reply	other threads:[~2006-07-05 22:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05 20:57 [Qemu-devel] No useful documentation Daniel Carrera
2006-07-05 21:07 ` Rick Vernam
2006-07-05 21:12 ` Nathaniel McCallum
2006-07-05 21:19   ` Daniel Carrera
2006-07-05 21:25     ` Rick Vernam
2006-07-05 21:40       ` Daniel Carrera
2006-07-05 22:48         ` Flavio Visentin
2006-07-05 22:52           ` Daniel Carrera
2006-07-05 23:11             ` benb
2006-07-05 23:02               ` WaxDragon
2006-07-05 23:06           ` benb
2006-07-05 23:36             ` Flavio Visentin
2006-07-06  0:19               ` benb
2006-07-05 21:29     ` Nathaniel McCallum
2006-07-05 21:31     ` Larry Brigman
2006-07-05 21:25 ` Jamie Lokier
2006-07-05 21:38   ` Daniel Carrera
2006-07-05 22:25     ` Jamie Lokier
2006-07-05 22:45       ` benb
2006-07-05 22:41     ` NyOS [this message]
2006-07-05 21:34 ` benb
2006-07-05 21:22   ` Daniel Carrera
2006-07-05 21:46     ` Udo 'Robos' Puetz
2006-07-05 22:01       ` Daniel Carrera
2006-07-06  0:00         ` Mike Swanson
2006-07-06  8:16           ` Daniel Carrera
2006-07-06 11:03             ` denis.scheidt
2006-07-05 22:30       ` Jamie Lokier
2006-07-05 22:34 ` Ronnie Misra
2006-07-05 22:38   ` Daniel Carrera
2006-07-05 22:56     ` benb
2006-07-09  9:26 ` [Qemu-devel] " Emmanuel Charpentier
  -- strict thread matches above, loose matches on Subject: below --
2006-07-05 21:05 [Qemu-devel] " Dugger, Donald D

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.tb8mnzwat9pcbo@mail.chello.hu \
    --to=lista@nyos.homelinux.net \
    --cc=daniel.carrera@zmsl.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).