From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Farkas Levente <lfarkas-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: (long) kvm and virt-manager not ready for daily usage
Date: Sat, 08 Sep 2007 16:51:00 -0500 [thread overview]
Message-ID: <1189288260.2304.1.camel@squirrel> (raw)
In-Reply-To: <46E30AFA.5060800-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
On Sat, 2007-09-08 at 22:50 +0200, Farkas Levente wrote:
> Anthony Liguori wrote:
> >> the host see as i've 4 cpu. i've got a change to gives more cpu to the
> >> guest, what's more they starts, but after a few minutes running the
> >> system crash. not just the guest os but the host os crash without any
> >> kind of info, log or any useful info what was the cause of it, but hard
> >> reset helps:-((( first of all it's serious problem, even if it's a known
> >> bug and documented somewhere (but there is not any kind of docs about
> >> neither kvm nor virt-manager/libvirt and what i can find that very
> >> limited), since all of the new hvm cpu (which is required for kvm) has
> >> more core, so the guest can't use the real power of the cpu this means
> >> i've to put a lots of guests with one virtual cpu to the host or
> >> currently can't exploit these cpus.
> >
> > I'm having difficulty understanding what your problem is. Are you
>
> after i reread my sentences it was difficult for me too:-(
>
> > saying that guest SMP isn't working for you? The host OS definitely
> > shouldn't crash. Can you be more specific about what configs you are
> > using? There was a host oops fixed in kvm-36 so upgrading may help you.
>
> exactly. i've got 4 phisical core (Intel Core 2 Quad) and i try to give
> 4 cpus for 2 guests and 2 cpus for a third guest and restart libvirtd.
> the result was that even the host system crash without any stack trace
> or kernel panic and only the hard reset helps.
Could you try to reproduce the problem with kvm-36? Host crash bugs are
very important to fix especially one so easily reproducible.
Regards,
Anthony Liguori
-------------------------------------------------------------------------
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-08 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 11:15 (long) kvm and virt-manager not ready for daily usage Farkas Levente
[not found] ` <46E28438.5000403-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-09-08 1:24 ` Izik Eidus
2007-09-08 12:35 ` Luca
[not found] ` <68676e00709080535ie3f6e56l822041e307cc16e1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-08 13:06 ` [kvm-devel] " Farkas Levente
[not found] ` <46E29E57.7070104-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-09-08 13:47 ` Luca
2007-09-08 15:18 ` Anthony Liguori
2007-09-08 20:50 ` [kvm-devel] " Farkas Levente
[not found] ` <46E30AFA.5060800-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-09-08 21:51 ` Anthony Liguori [this message]
2007-09-09 10:21 ` Farkas Levente
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=1189288260.2304.1.camel@squirrel \
--to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=lfarkas-lWVWdrzSO4GHXe+LvDLADg@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