public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Duffy <cduffy-0XdUWXLQalXR7s880joybQ@public.gmane.org>
To: Dor Laor <dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kvm-36 losing (tap-based) network connectivitymid-session
Date: Wed, 29 Aug 2007 22:48:58 -0500	[thread overview]
Message-ID: <46D63E2A.7040004@spamcop.net> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E032160D655FEC-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>

Dor Laor wrote:
> Can you try it without rtc (either use -no-rtc, I'm not sure we have
> this flag or just rm /dev/rtc before you run the vm).

Tried it (and -tdf) without effect.

> What's your host HZ configuration?

CONFIG_HZ=250

> If the above doesn't work, can you repeat the test with -no-kvm?

-no-kvm segfaults immediately on startup.

===
Starting program: /usr/bin/kvm -no-kvm -kernel 
kernel-x86_64-2.6.20-gentoo-r8 -hda grubdisk.img
[Thread debugging using libthread_db enabled]
[New Thread 47987424286272 (LWP 13655)]
Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal
error, but for better emulation accuracy either use a 2.6 host Linux 
kernel or
type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47987424286272 (LWP 13655)]
0x0000000000000000 in ?? ()
(gdb) bt

#0  0x0000000000000000 in ?? ()
#1  0x0000000000481e8b in cpu_x86_exec (env1=<value optimized out>) at 
/usr/src/debug/app-emulation/kvm-36/kvm-36/qemu/cpu-exec.c:750
#2  0x0000000000409a6d in main_loop () at 
/usr/src/debug/app-emulation/kvm-36/kvm-36/qemu/vl.c:6311
#3  0x000000000040de7a in main (argc=0, argv=0x7fffba1c59c8) at 
/usr/src/debug/app-emulation/kvm-36/kvm-36/qemu/vl.c:7774
#4  0x00002ba4f12ea5e6 in __libc_start_main () from /usr/local/lib/libc.so.6
#5  0x0000000000405689 in _start ()
===

-------------------------------------------------------------------------
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/

  parent reply	other threads:[~2007-08-30  3:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30  3:15 kvm-36 losing (tap-based) network connectivity mid-session Charles Duffy
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 [this message]
     [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=46D63E2A.7040004@spamcop.net \
    --to=cduffy-0xduwxlqalxr7s880joybq@public.gmane.org \
    --cc=charles-7s4ginpmXnFeoWH0uzbU5w@public.gmane.org \
    --cc=dor.laor-atKUWr5tajBWk0Htik3J/w@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