From: Avi Kivity <avi@redhat.com>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: KVM Test report, kernel d335b15... qemu cb1983b8...
Date: Thu, 16 Dec 2010 10:32:12 +0200 [thread overview]
Message-ID: <4D09CE8C.7040902@redhat.com> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E1E0EDF8584@shsmsx502.ccr.corp.intel.com>
On 12/15/2010 08:05 AM, Hao, Xudong wrote:
> Hi, all,
> This is KVM test result against kvm.git d335b156f9fafd177d0606cf845d9a2df2dc5431, and qemu-kvm.git cb1983b8809d0e06a97384a40bad1194a32fc814.
>
> Currently qemu-kvm build fail on RHEL5 with a undeclared "PCI_PM_CTRL_NO_SOFT_RST" error. I saw there already were fix patch in mail list.
> There are 2 bugs got fixed.
>
> Fixed issues:
> 1. Guest qemu processor will be defunct process by be killed
> https://bugzilla.kernel.org/show_bug.cgi?id=23612
Good to see it was indeed fixed by -rc5.
> 2. [SR] qemu return form "migrate " command spend long time
> https://sourceforge.net/tracker/?func=detail&aid=2942079&group_id=180599&atid=893831
>
Juan, Luiz, any idea what fixed this? I saw it too.
Xudong, please open qemu bugs on launchpad (https://launchpad.net/qemu),
not on sourceforge. Kernel bugs go to the kernel bugzilla as usual.
We'll retire the sourceforge bug tracker.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-16 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 6:05 KVM Test report, kernel d335b15... qemu cb1983b8 Hao, Xudong
2010-12-16 8:32 ` Avi Kivity [this message]
2010-12-16 8:46 ` Hao, Xudong
2010-12-16 10:43 ` Luiz Capitulino
2010-12-16 10:46 ` Avi Kivity
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=4D09CE8C.7040902@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=quintela@redhat.com \
--cc=xudong.hao@intel.com \
/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