From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Daniel Paquet <daniel.paquet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Guest OS lock up with 100% cpu usage when using tap
Date: Wed, 19 Sep 2007 18:42:59 +0200 [thread overview]
Message-ID: <46F15193.3090309@qumranet.com> (raw)
In-Reply-To: <9a1a10a40709190930q549e5c73peacd0a1a1556ea14-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Daniel Paquet wrote:
> Hello,
>
> This is a followup from my last message stating that my guest os
> dont load up correctly. The problem was that my xp or vista guest os
> uses 100% cpu at startup and frequent lockup then continue to load.
>
> I played a bit with my startup parameters to find out that the problem
> is related the to tap network interface, everything starts okay if I
> remove the tap network from the startup parameters.
>
> So my original startup was :
> kvm -no-rtc -hda disks/vista.qcow2 -localtime -m 512 -net
> nic,model=ne2k_pci,macaddr=00:00:00:00:00:01 -net tap,ifname=tap0 &
>
> And now I used
> kvm -no-rtc -hda disks/vista.qcow2 -localtime -m 512 -net
> nic,model=ne2k_pci,macaddr=00:00:00:00:00:01 &
>
> And the guest os boots correctly. I have this problem with kvm-33 and
> upward to kvm-40 (I didn't tryed older releases as I need vista).
>
> The thing is that I am using the tap interface to communicate with my
> guest os and supply them with an Internet connection. So anyone have a
> clue or something I may supply to help resolve this issue?
>
Interesting. Maybe your network is flooded with broadcasts. Try
running wireshark or tcpdump on the tap interface and see if something
is flowing through it at a high rate.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-19 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 16:30 Guest OS lock up with 100% cpu usage when using tap Daniel Paquet
[not found] ` <9a1a10a40709190930q549e5c73peacd0a1a1556ea14-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-19 16:42 ` Avi Kivity [this message]
[not found] ` <46F15193.3090309-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-19 17:00 ` Daniel Paquet
2007-09-19 17:18 ` Daniel Paquet
[not found] ` <9a1a10a40709191018r78013446lb6bd3f280c708052-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-19 17:21 ` Avi Kivity
[not found] ` <46F15AA8.8030304-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-19 17:48 ` Daniel Paquet
[not found] ` <9a1a10a40709191048w6ad0af3es8960e98dc08df2f5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-19 17:49 ` Avi Kivity
[not found] ` <46F16139.80400-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-19 18:10 ` Daniel Paquet
[not found] ` <9a1a10a40709191113t2e4a09bfs16701d31689368c2@mail.gmail.com>
[not found] ` <9a1a10a40709191113t2e4a09bfs16701d31689368c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-19 18:16 ` Avi Kivity
[not found] ` <46F1677A.8040808-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-19 18:27 ` Daniel Paquet
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=46F15193.3090309@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=daniel.paquet-Re5JQEeQqe8AvxtiuMwx3w@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 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.