public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Koen de Jonge <koen-OoqVcbiag8BWk0Htik3J/w@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: installing kvm on debian 4.0 r0
Date: Fri, 17 Aug 2007 21:47:51 +0200	[thread overview]
Message-ID: <46C5FB67.7040301@procolix.com> (raw)

Hi All,

Below is how I installed kvm-35 on my debian etch installation, it may 
be included in the wiki :)

I installed the amd64 version of debian 4.0 r0 on my amd4800+
I did all 'apt-get update' and 'apt-get upgrade' steps to get the system 
updated with all latest patches.
And off course I did 'apt-get install linux-image-2.6-amd64 to get the 
2.6.18-5-amd64 kernel.

I then used these to make the system workable:
apt-get install openssh-server
apt-get install sudo

Then I used these as prerequisite packages for kvm:
apt-get install gcc-3.4
apt-get install libsdl1.2-dev
apt-get install zlibc
apt-get install zlib1g-dev
apt-get install uuid-dev
apt-get install linux-kernel-headers
apt-get install libasound2-dev

I then downloaded kvm-35 and did:
tar zxf kvm-35.tar.gz
cd kvm-35
./configure --prefix=/usr/local/kvm
make
make install
modprobe kvm-amd

I then wanted to test the i386 debian netinstall iso doing this:
/usr/local/kvm/bin/qemu-img create -f qcow test.img 2G
/usr/local/kvm/bin/qemu-system-x86_64 -hda test.img -cdrom 
debian-40r0-i386-netinst.iso -boot d -m 265

It was very, very fast, even better than using ubuntu 7.04 but that 
wasn't a fully 64 bit host os, and this debian is.

Are you developers interested in warnings like these?
/root/kvm-35/qemu/slirp/tcp_subr.c: In function `tcp_newtcpcb':
/root/kvm-35/qemu/slirp/tcp_subr.c:210: warning: cast from pointer to 
integer of different size
/root/kvm-35/qemu/slirp/tcp_subr.c: In function `tcp_close':
/root/kvm-35/qemu/slirp/tcp_subr.c:286: warning: cast to pointer from 
integer of different size
/root/kvm-35/qemu/slirp/tcp_subr.c:288: warning: cast to pointer from 
integer of different size
/root/kvm-35/qemu/slirp/tcp_subr.c:289: warning: cast to pointer from 
integer of different size
/root/kvm-35/qemu/slirp/tcp_subr.c:289: warning: cast to pointer from 
integer of different size
/root/kvm-35/qemu/slirp/tcp_subr.c:290: warning: cast to pointer from 
integer of different size

Greetz,
Koen

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

             reply	other threads:[~2007-08-17 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 19:47 Koen de Jonge [this message]
     [not found] ` <46C5FB67.7040301-OoqVcbiag8BWk0Htik3J/w@public.gmane.org>
2007-08-18 15:53   ` installing kvm on debian 4.0 r0 Koen de Jonge
     [not found]     ` <46C715F5.80601-OoqVcbiag8BWk0Htik3J/w@public.gmane.org>
2007-08-18 16:44       ` Luca
     [not found]         ` <68676e00708180944l2db80c12ycd073d0804647bbb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-18 17:58           ` Koen de Jonge
2007-08-19  8:49   ` Avi Kivity

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=46C5FB67.7040301@procolix.com \
    --to=koen-ooqvcbiag8bwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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