From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Zhao, Yunfeng" <yunfeng.zhao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: KVM Test result, kernel a843332b.. , userspace 356c9ff5..
Date: Mon, 20 Aug 2007 12:09:05 +0300 [thread overview]
Message-ID: <46C95A31.90707@qumranet.com> (raw)
In-Reply-To: <46C9551A.7020005-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity wrote:
> Zhao, Yunfeng wrote:
>> Hi, all,
>> This is today's KVM test result against kvm.git
>> a843332b0445c9d60e4c9bda965b10cbe632a088 and kvm-userspace.git
>> 356c9ff52b05e2d0f2b2eee9f861ad7c3ab3babd.
>>
>> Host crash issue still exists on latest KVM, even boot one linux guest
>> will cause host to crash, so most our tests failed.
>>
>> I have uploaded the serial output in the issue below:
>> 1. Host crashes when boot a linux guest
>> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1776079&gro
>> up_id=180599
>>
>> We found that this regression happens between kvm.git
>> 9bcbb7df435e154b148662df3721f71847a9342c and kvm.git :
>> 83aecfbf44f3ba92abde47957a3c9175f1ec7165.
>>
>> It is blocking our testing, and also effecting the development of
>> developer.
>>
>
> Sorry, I forgot about it since all works well here. Will try to
> reproduce.
>
Now fixed and pushed (200b412d5f84907f2de0e27b95e70493d0741fa3 in
kvm-userspace.git). I didn't see the issue because I usually use
--with-patched-kernel and run kvm.git directly.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
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/
prev parent reply other threads:[~2007-08-20 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 8:25 KVM Test result, kernel a843332b.. , userspace 356c9ff5 Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77AA3F01F-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-20 8:47 ` Avi Kivity
[not found] ` <46C9551A.7020005-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-20 9:09 ` Avi Kivity [this message]
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=46C95A31.90707@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=yunfeng.zhao-ral2JQCrhuEAvxtiuMwx3w@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