From: Daniel Bareiro <daniel-listas@gmx.net>
To: KVM General <kvm@vger.kernel.org>
Subject: Re: Loss of network connectivity with high load
Date: Wed, 16 Jun 2010 00:36:43 -0300 [thread overview]
Message-ID: <20100616033643.GB28074@defiant.freesoftware> (raw)
In-Reply-To: <201006151613.03906.iggy@theiggy.com>
[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]
Hi, Brian.
On Tuesday, 15 June 2010 16:13:03 -0500,
Brian Jackson wrote:
> > I'm using Linux 2.6.31.13 compiled with the kernel.org source code
> > on KVM host with Debian GNU/Linux Lenny amd64. Also I'm using Debian
> > GNU/Linux Lenny amd64 virtual machine with kernel 2.6.26-2 from
> > Debian repositories. I'm using qemu-kvm 0.12.3.
> >
> > These are the parameters I'm using to start the virtual machine:
> >
> >
> > escher:~# ps ax|grep kvm
> > 6299 ? Rl 113:40 /usr/local/qemu-kvm/bin/qemu-system-x86_64
> > -drive file=/dev/vm/belvedere-raiz,cache=none,if=virtio,boot=on -drive
> > file=/dev/vm/belvedere-u01,cache=none,if=virtio -drive
> > file=/dev/vm/belvedere-u02,cache=none,if=virtio -drive
> > file=/dev/vm/belvedere-u03,cache=none,if=virtio -drive
> > file=/dev/vm/belvedere-u04,cache=none,if=virtio -drive
> > file=/dev/vm/belvedere-u05,cache=none,if=virtio -drive
> > file=/dev/vm/belvedere-u06,cache=none,if=virtio -drive
> > file=/dev/vm/belvedere-u07,cache=none,if=virtio -drive
> > file=/dev/vm/belvedere-u08,cache=none,if=virtio -drive
> > file=/dev/vm/belvedere-u09,cache=none,if=virtio -m 3072 -smp 2 -net
> > nic,model=virtio,macaddr=00:16:3e:00:00:56 -net tap -daemonize -vnc :2
> > -k es -localtime -monitor telnet:localhost:4002,server,nowait -serial
> > telnet:localhost:4042,server,nowait
> >
> >
> > When I try to copy directories of several gigabytes in this VM using
> > rsync to other hosts, this virtual machine loses connectivity with
> > the rest of the network. Checking, using a serial console
> > connection, /var/log/syslog and /var/log/messages in search of the
> > problem, I don't see information that might give a clue to the
> > problem.
> >
> > This problem is not with the network driver by default (rtl8139), so
> > I think that should be something related to Virtio.
> There have been a few bugs similar to this reported that should be
> pretty easy to find. Basically, I'd say try 0.12.4, it should have a
> few fixes in this area over 0.12.3.
I was testing with qemu-kvm 0.12.4 but I'm having the same problem. I
re-read the announce about qemu-kvm 0.12.4 sent by Avi, but I didn't
find in it some reference about fixes related to Virtio.
If there's anything else I can try, please tell me.
Regards,
Daniel
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-06-16 3:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 21:00 Loss of network connectivity with high load Daniel Bareiro
2010-06-15 21:13 ` Brian Jackson
2010-06-16 3:36 ` Daniel Bareiro [this message]
2010-06-16 10:19 ` Daniel Bareiro
2010-06-16 14:14 ` Avi Kivity
2010-06-16 18:10 ` Daniel Bareiro
2010-06-22 6:32 ` Thomas Besser
2010-06-22 12:32 ` Thomas Besser
2010-06-22 12:50 ` RW
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=20100616033643.GB28074@defiant.freesoftware \
--to=daniel-listas@gmx.net \
--cc=dbareiro@gmx.net \
--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