public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Test result for KVM, kernel 62d1ea7.. , userspace 667f2deff8..
Date: Mon, 24 Sep 2007 15:57:20 +0200	[thread overview]
Message-ID: <46F7C240.1030501@bull.net> (raw)
In-Reply-To: <46F7B696.1030304-atKUWr5tajBWk0Htik3J/w@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1120 bytes --]

Avi Kivity wrote:
> Farkas Levente wrote:
>> hi,
>> it seems we've got a real tester:-) for ma all of the bellow are serious
>> bugs (tomorrow i'll try to send more detail of our host crash too) and
>> imho the latest 'stable' version was kvm-36. wouldn't be better to
>> postpone all patches and infrastructure changes (virtio and others)
>> until these have been fixed and try to produce a new 'stable' release?
>> i understand then everybody (including myself) would like to see these
>> new features in the latest and greatest kvm release, but at the same
>> time i'd be nice to think about the end users too.
>> may some version cane be labeled as stable (eg 36) and the latest as
>> devel. this can help a lot for those who are not read this list.
>>   
> 
> You can use -no-kvm-irqchip to get stability similar to kvm-36.
>

Perhaps a workaround for end user could be to disable by default kvm irqchip and
add an option to enable it (--use-kvm-irqchip) ?

Laurent
-- 
------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  --------------
          "Software is hard" - Donald Knuth


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

  parent reply	other threads:[~2007-09-24 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 11:56 Test result for KVM, kernel 62d1ea7.. , userspace 667f2deff8 Zhao, Yunfeng
     [not found] ` <10EA09EFD8728347A513008B6B0DA77A02125EEE-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-24 12:23   ` Farkas Levente
     [not found]     ` <46F7AC42.9080909-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-09-24 13:07       ` Avi Kivity
     [not found]         ` <46F7B696.1030304-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-24 13:57           ` Laurent Vivier [this message]
     [not found]             ` <46F7C240.1030501-6ktuUTfB/bM@public.gmane.org>
2007-09-24 14:00               ` Avi Kivity
     [not found]                 ` <46F7C312.4040103-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-24 14:16                   ` Laurent Vivier

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=46F7C240.1030501@bull.net \
    --to=laurent.vivier-6ktuutfb/bm@public.gmane.org \
    --cc=avi-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