From: "Daniel P. Berrange" <berrange@redhat.com>
To: andreas.ames@de.transport.bombardier.com
Cc: kvm@vger.kernel.org
Subject: Re: Problem with bridged tap interface
Date: Wed, 23 Feb 2011 13:37:16 +0000 [thread overview]
Message-ID: <20110223133715.GF26589@redhat.com> (raw)
In-Reply-To: <OF96885699.D449DB0D-ONC1257840.003E1D62-C1257840.003FB1C8@cone.bombardier.com>
On Wed, Feb 23, 2011 at 12:34:45PM +0100, andreas.ames@de.transport.bombardier.com wrote:
> Hi all,
>
> sorry for the previous partial e-mail, I hit the send button accidentally
> ;-).
>
> I have a setup with a kvm-based virtual machine running a stock RedHat 6.1
> (yes, that old) on a rather current debian host.
>
> 1. uname in host: 2.6.26-2-amd64 #1 SMP Wed May 12 18:03:14 UTC 2010
> x86_64 GNU/Linux
>
> 2. uname in guest: 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 i686 unknown
>
> eth0 of the guest is connected via tap0 to a kernel bridge, that is in
> turn connected via the host's eth1 to a Gigabit link. On the kvm
> command-line I configure the guest-nic as "model=ne2k_pci".
>
> The problem is, that I frequently loose network access from/to the guest.
There have been QEMU NIC model implementation bugs that exhibit
that characteristic. If you have the drivers available in the
guest, then I'd recommend trying out different NIC models than
ne2k, since that's probably the least actively maintained NIC
model. At least try rtl8139, but ideally the e1000 too.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2011-02-23 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 11:34 Problem with bridged tap interface andreas.ames
2011-02-23 13:37 ` Daniel P. Berrange [this message]
2011-02-24 15:02 ` andreas.ames
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=20110223133715.GF26589@redhat.com \
--to=berrange@redhat.com \
--cc=andreas.ames@de.transport.bombardier.com \
--cc=kvm@vger.kernel.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