From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Daniel Qarras <dqarras-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Step by step instructions for KVM networking
Date: Thu, 22 Feb 2007 11:17:29 +0200 [thread overview]
Message-ID: <45DD5FA9.2010602@qumranet.com> (raw)
In-Reply-To: <786483.53715.qm-uAqfo9yIfQuvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
Daniel Qarras wrote:
> Hi all,
>
> I've played with Xen on my Fedora and it's been working fine. Now I'm
> testing KVM with 2.6.20 kernel and it's working nicely, too, but I'm
> unable to setup a full-blown networking, i.e., a mode where also
> icmp/udp work. User-mode networking works well, e.g., yum and firefox
> run just fine under KVM.
>
> Could someone please post a step by step list how to enable
> non-usermode networking with KVM/QEMU on Fedora? I've googled
> for this and found instructions (mostly for Debian) but I've not been
> able to set up this on Fedora.
>
In general the setup is exactly like qemu, so any howto for qemu is
applicable.
Here's what I do:
- copy scripts/kvm from the kvm tarball to /etc/init.d, chkconfig and
start the kvm service. that sets up a bridge
- copy scripts/qemu-ifup into a new directory /etc/kvm. make sure it is
executable.
- run qemu like this:
qemu-system-x86_64 -net nic -net tap,script=/etc/kvm/qemu-ifup [other
options]...
> (My test machine has one NIC with a 10.x.x.x address in an intranet. I
> would want that my KVM guests have, e.g., 192.168.x.x static addresses
> and they can ping each other, the host machine, and access outside
> world with tcp/udp/icmp etc. So something what Xen does now
> automatically on Fedora. Connection initiated from outside world are
> not essential but would of course be a nice bonus.)
>
The configuration above would put the guests on the same ethernet
segment, so you'd need to assign them addresses in the 10.0.0.0/8 subnet.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-02-22 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 18:57 Step by step instructions for KVM networking Daniel Qarras
[not found] ` <786483.53715.qm-uAqfo9yIfQuvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2007-02-22 9:17 ` Avi Kivity [this message]
[not found] ` <45DD5FA9.2010602-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-22 17:48 ` Daniel Qarras
[not found] ` <20070222174843.13805.qmail-xjuEXE6AJAOvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2007-02-25 8:31 ` Avi Kivity
[not found] ` <45E1494D.6010907-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-25 8:50 ` Avi Kivity
[not found] ` <45E14DE5.7050401-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-26 18:11 ` Daniel Qarras
2007-03-25 21:10 ` Steve Kwee
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=45DD5FA9.2010602@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=dqarras-/E1597aS9LQAvxtiuMwx3w@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