From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: KVM <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: Biweekly KVM Test report, kernel ae7a2a3f... qemu a212f79f...
Date: Wed, 04 Jul 2012 17:15:06 +0200 [thread overview]
Message-ID: <4FF45DFA.5000607@siemens.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A1011DF4F@SHSMSX101.ccr.corp.intel.com>
On 2012-07-04 17:03, Ren, Yongjie wrote:
>> -----Original Message-----
>> From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
>> Sent: Wednesday, July 04, 2012 10:43 PM
>> To: Ren, Yongjie
>> Cc: KVM; Avi Kivity
>> Subject: Re: Biweekly KVM Test report, kernel ae7a2a3f... qemu a212f79f...
>>
>> On 2012-07-03 09:11, Ren, Yongjie wrote:
>>> Hi All,
>>>
>>> This is KVM upstream test result against kvm.git next branch and
>> qemu-kvm.git master branch.
>>> kvm.git next branch: ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb
>> based on kernel 3.5.0-rc1
>>> qemu-kvm.git master branch:
>> a212f79fc4596570124fb864425b980c157cd001
>>>
>>> We found 1 new bug and 1 bug got fixed in the past two weeks.
>>>
>>> New issue (1):
>>> 1. [RAS] vCPU hot-add makes the guest abort.
>>> https://bugs.launchpad.net/qemu/+bug/1019179
>>
>> Strange. I thought CPU hot-plugging is broken in qemu-kvm for ages now.
>>
> That should be true.
>
>> Is the test new?
>>
> I just tested CPU hot-plug for kvm guest two weeks ago.
> Before that, I assumed it should work fine, so I filed a bug.
> I think it's also good to have a bug to track this issue.
> And, sorry, it's kind of confusing that I put it as a 'new' issue.
>
No problem! This is actually now more a feature request for upstream
QEMU. Several people are working on preparing the infrastructure to
introduce it there, properly.
Hmm, I wonder if we should simple drop the related monitor command from
qemu-kvm. There are several broken releases now, and upstream will have
a different control interface.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2012-07-04 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 7:11 Biweekly KVM Test report, kernel ae7a2a3f... qemu a212f79f Ren, Yongjie
2012-07-04 14:43 ` Jan Kiszka
2012-07-04 15:03 ` Ren, Yongjie
2012-07-04 15:15 ` Jan Kiszka [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=4FF45DFA.5000607@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=yongjie.ren@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 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.