From: Charles Duffy <cduffy-0XdUWXLQalXR7s880joybQ@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: kvm-36 losing (tap-based) network connectivity mid-session
Date: Wed, 29 Aug 2007 22:15:47 -0500 [thread overview]
Message-ID: <fb5cp5$goi$1@sea.gmane.org> (raw)
kvm-36 is repeatedly timing out partway through a long network transfor
and failing to resume. Both host and guest are 64-bit. This has happened
with a number of prior releases as well; it does not appear to be a
recently-introduced issue.
My command line looks like the following:
$ qemu-system-x86_64 -kernel kernel-x86_64-2.6.20-gentoo-r8 -initrd
initramfs.igz -hda hda -hdb hdb -append "panic=30 console=ttyS0
action=install" -nographic -net nic -net
'tap,ifname=tap0,script=./tap0-start'
/dev/kvm is quite certainly being used, as KVM immediately segfaults on
startup without it (or in the presence of the -no-kvm option).
dmesg on the host shows a great number of "rtc: lost some interrupts at
1024Hz" messages.
The end of a typical session looks much like the following:
====
79000K .......... .......... .......... .......... .......... 4% 5.43M
4:33
79050K .......... .......... .......... .......... .......... 4% 6.10M
4:03
79100K .......... .......... .......... .......... .......... 4% 8.14M
3:02
79150K ...... 4% 5.96M
4:09
02:45:23 (2.06 MB/s) - Read error at byte 81055847/1639127012
(Connection timed out). Retrying.
--02:45:23--
http://10.0.0.30/gentoo-installer/deployed_server-stage4-amd64-2007.0.tar.bz2
(try: 2) => `/mnt/gentoo/deployed_server-stage4-amd64-2007.0.tar.bz2'
Connecting to 10.0.0.30:80... Hangcheck: hangcheck value past margin!
failed: Connection timed out.
Retrying.
--02:45:53--
http://10.0.0.30/gentoo-installer/deployed_server-stage4-amd64-2007.0.tar.bz2
(try: 3) => `/mnt/gentoo/deployed_server-stage4-amd64-2007.0.tar.bz2'
Connecting to 10.0.0.30:80... failed: Connection timed out.
Retrying.
--02:46:23--
http://10.0.0.30/gentoo-installer/deployed_server-stage4-amd64-2007.0.tar.bz2
(try: 4) => `/mnt/gentoo/deployed_server-stage4-amd64-2007.0.tar.bz2'
====
Network access works, and then suddenly doesn't. I am more reliably able
to reproduce this issue using -net tap than -net user.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-08-30 3:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 3:15 Charles Duffy [this message]
2007-08-30 3:41 ` kvm-36 losing (tap-based) network connectivitymid-session Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160D655FEC-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-08-30 3:48 ` Charles Duffy
[not found] ` <46D63E2A.7040004-0XdUWXLQalXR7s880joybQ@public.gmane.org>
2007-09-09 11:38 ` Avi Kivity
[not found] ` <46E3DB52.5040203-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-09 20:41 ` Charles Duffy
2007-09-21 23:49 ` [RESOLVED] kvm-36 losing (tap-based) network connectivity mid-session Charles Duffy
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='fb5cp5$goi$1@sea.gmane.org' \
--to=cduffy-0xduwxlqalxr7s880joybq@public.gmane.org \
--cc=charles-7s4ginpmXnFeoWH0uzbU5w@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