From: Steve Kwee <kwee-/uwWY36kK6L+/zaKxxHzyw@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Step by step instructions for KVM networking
Date: Sun, 25 Mar 2007 21:10:24 +0000 (UTC) [thread overview]
Message-ID: <loom.20070325T230047-748@post.gmane.org> (raw)
In-Reply-To: 20070226181124.96530.qmail@web36803.mail.mud.yahoo.com
Daniel Qarras <dqarras@...> writes:
>
> Hi Avi, all,
>
> > I tried it now, it's simple and it even works:
> >
> > 1. Add BRIDGE=sw0 to ifcfg-eth0
> > 2. Create a new ifcfg-sw0 that has TYPE=Bridge, and any dhcp/ip
> > configuration you previously had in ifcfg-eth0
>
> I've now managed to get several KVM hosts working in a local intranet
> based on your help, thanks! Below are finally step-by-step instructions
> that work at least on Fedora Core 6, running other FC6 virtual hosts:
>
:
:
Hi all,
some more hints that would have saved me a lot of time:
If your eth0 is a wireless device, it might be a good idea to switch to another
device to try this. Many wireless devices have problems with bridged networking.
I switched to my wired network after a lot of testing and had success.
If you do not provide a mac addr on the commandline of qemu / kvm a static
macaddr will be used, giving you problems starting with vm no2.
In the guest an interface eth0 is instantiated with this fixed macaddr
which can be configured as usual
If you provide a macaddr the interface is instantiated as eth1 instead of eth0.
I do not understand why, maybe someone can acknoledge this fact.
Anyway thinks worked when I switched to eth1 in my hosts.
An article that helped me a lot was:
http://kidsquid.com/cgi-bin/moin.cgi/QemuNetwork
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-03-25 21:10 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
[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 [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=loom.20070325T230047-748@post.gmane.org \
--to=kwee-/uwwy36kk6l+/zakxxhzyw@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