From: Oliver Francke <Oliver.Francke@filoo.de>
To: "qemu@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Fwd: [Qemu-stable] connectivity problem with Windows 7 + heavy network-traffic
Date: Wed, 22 May 2013 11:27:58 +0200 [thread overview]
Message-ID: <519C8F9E.6060809@filoo.de> (raw)
In-Reply-To: <518A0703.2040807@filoo.de>
[-- Attachment #1: Type: text/plain, Size: 2431 bytes --]
Hi Stefan,
thanks for your attention. See all infos below including complete
command-line.
Thnx,
Oliver.
-------- Original Message --------
Subject: [Qemu-stable] connectivity problem with Windows 7 + heavy
network-traffic
Date: Wed, 08 May 2013 10:04:19 +0200
From: Oliver Francke <Oliver.Francke@filoo.de>
To: qemu-stable@nongnu.org <qemu-stable@nongnu.org>
Hi,
I have a couple of reports vom people, where the network-link goes down.
I did some live-migration, and the RTL8139 card was connected again, up
to the next traffic-burst.
( just cmd, one ftp download + two uploads parallel... let it run for
couple of minutes until drop...)
No way within windows to recover the card except reboot.
All is fine with qem-1.2.0, I have no problem to make some exceptions
for these VM's, but cool would
be some possibility to narrow down the problem, which is there in
qemu-1.3.x up to 1.5.0-rc0.
The host is for example an AMD opteron 6172 ( 24 cores).
Switch is openvswitch-1.9.x, nothing special.
Here my call to qemu:
/usr/local/qemu-1.5.0/bin/qemu-system-x86_64 -usbdevice tablet
-enable-kvm -daemonize -pidfile /var/run/qemu-server/761.pid -monitor
unix:/var/run/qemu-server/761.mon,server,nowait -vnc
unix:/var/run/qemu-server/761.vnc,password -qmp
unix:/var/run/qemu-server/761.qmp,server,nowait -nodefaults -serial none
-parallel none -device rtl8139,mac=00:F1:70:00:2F:90,netdev=vlan0d0
-netdev
type=tap,id=vlan0d0,ifname=tap761i0d0,script=/etc/fcms/add_if.sh,downscript=/etc/fcms/downscript.sh
-name 1155823384-4 -m 2048 -vga cirrus -k de -smp sockets=1,cores=2
-device virtio-blk-pci,drive=virtio0 -drive
format=raw,file=rbd:1155823384/vm-761-disk-1.rbd:rbd_cache=false,cache=writeback,if=none,id=virtio0,media=disk,index=0
-drive
format=raw,file=rbd:1155823384/vm-761-swap-1.rbd:rbd_cache=false,cache=writeback,if=virtio,media=disk,index=1
-drive if=ide,media=cdrom,id=ide1-cd0 -drive
if=ide,media=cdrom,id=ide1-cd1 -rtc base=localtime -no-hpet -bootorder=dc
No problems whatsoever with all Linux-distros ( running hundreds of
them). I left out the -rtc and -no-hpet, not any better.
Any comments and help welcome,
Oliver.
--
Oliver Francke
filoo GmbH
Moltkestraße 25a
33330 Gütersloh
HRB4355 AG Gütersloh
Geschäftsführer: S.Grewing | J.Rehpöhler | C.Kunz
Folgen Sie uns auf Twitter: http://twitter.com/filoogmbh
[-- Attachment #2: Type: text/html, Size: 3716 bytes --]
next parent reply other threads:[~2013-05-22 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <518A0703.2040807@filoo.de>
2013-05-22 9:27 ` Oliver Francke [this message]
2013-05-22 12:51 ` [Qemu-devel] Fwd: [Qemu-stable] connectivity problem with Windows 7 + heavy network-traffic Stefan Hajnoczi
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=519C8F9E.6060809@filoo.de \
--to=oliver.francke@filoo.de \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.