public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: James Dickens <jamesd.wi@gmail.com>
To: William Cohen <wcohen@redhat.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: running systemtap on qemu
Date: Wed, 28 Sep 2005 17:59:00 -0000	[thread overview]
Message-ID: <cd09bdd10509281059673f2dc5@mail.gmail.com> (raw)
In-Reply-To: <433AC7B8.1040402@redhat.com>

On 9/28/05, William Cohen <wcohen@redha.com> wrote:
> I am probably not the only one that doesn't always have a spare machine
> handy to try something out on. Tuesday I set up an FC4 image on QEMU on
> my FC3 laptop. I have attached a writeup describing what I did.
>
> -Will
>

great idea, i use a trial version of vmware and get faster results but
same intent

[snip]
> The next step is to set up a FC4 image. For this you will need a file
> to act as the virtual disk drive and the ISO image for the FC4 DVD.  A
> 8Gigabyte virtual disk drive file can be created for QEMU with:
>
> qemu-img create qemu-fc4.img 8G

i have found that you can get by with  a 4G disk if you follow my
recomendations outlined below.

>
> The FC4 DVD ISO,FC4-i386-DVD.iso, can be obtained from:
>
> http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/iso/FC4-i386-DVD.iso
>
> Now you can install FC4 on the virtual disk drive with QEMU. QEMU can
> grab the mouse and keyboard, you can toggle back to the regular system
> with <cntl>-<alt>. Start the installation with:
>
> qemu -boot d -cdrom FC4-i386-DVD.iso qemu-fc4.img
>
> This will boot off the DVD iso. Now you can do the normal installation
> using the normal defaults for things. When selecting packages at a
> minimum SystemTap will need the kernel-devel and the gcc compiler
> packages. The "Workstation" installation should be sufficient; to keep
> the amount of space required down and reduce the installation time
> avoid an "everything" install. Refer to the following URL for more information
> about installation:
>
i use a custom install,  no X, nothing extra just develepopment tools.

> http://fedora.redhat.com/docs/fedora-install-guide-en/fc4/
>
> The installation of the packages will take a while.  Allow the RPM
> install to complete. When asked select the reboot and go through the
> normal first boot. After this you have an FC4 image you can play with
> on QEMU. You will need to shut down the system in the normal manner,
> e.g. selecting shutdown on log out.  To restart the FC4 image you use
> the following command:
>
> qemu   qemu-fc4.img
>

> You will want to update the packages in the FC4. The machine
> will need a network connection to connect to the YUM repository. Log
> in as root on the FC4 system running on QEMU. Open a terminal and run
> the upgrade:
>
> yum update

this is over kill, you can get by with just following these instructions

http://sources.redhat.com/ml/systemtap/2005-q3/msg00470.html

a bit more steps, but it ends up being much faster.

James Dickens
uadmin.blogspot.com


[snip]

      reply	other threads:[~2005-09-28 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 16:40 William Cohen
2005-09-28 17:59 ` James Dickens [this message]

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=cd09bdd10509281059673f2dc5@mail.gmail.com \
    --to=jamesd.wi@gmail.com \
    --cc=systemtap@sources.redhat.com \
    --cc=wcohen@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).