From: Zhang Haoyu <zhhy.zhanghaoyu@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>, stefanha@redhat.com
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: bridge mode without network rework
Date: Wed, 24 Dec 2014 09:02:33 +0800 [thread overview]
Message-ID: <549A10A9.2020509@gmail.com> (raw)
On 2014-12-20 02:07:27, Paolo Bonzini wrote:
>
> On 19/12/2014 11:59, tlau@tetrioncapital.com wrote:
> > Since we decided not to go with KVM due to stability issue, we could let this go, thanks.
>
> That's a pity. That said, your decision to not go with KVM due to
> stability is a bit strange:
>
> 1) unless you are using open source Xen, you are presumably going for a
> commercial solution that would cost you money anyway. Have you thought
> of asking for commercial support, either from Canonical (since you were
> using Ubuntu) or from anyone else?
>
> 2) I saw now that you were using 3.13. I'm sorry for not having noticed
> that early, but have you tried upgrading the kernel? There is a known
> bug with Ivy Bridge EP and hv_vapic, but it's fixed on newer kernels
> (3.16). If you are not going to pay anyone for support, you probably
Hi, Paolo,
do you mean the commit fc57ac2 KVM: lapic: sync highest ISR to hardware apic on EOI ?
I want to backport it to our product.
Thanks,
Zhang Haoyu
> should have thought about this yourself. If you hadn't thought about
> it, and you are going for an open source solution (which I hope), you
> probably should re-evaluate the plan of not paying anyone for support,
> either a company or someone with enough expertise.
>
> Paolo
next reply other threads:[~2014-12-24 1:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 1:02 Zhang Haoyu [this message]
2014-12-24 8:21 ` bridge mode without network rework Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2014-12-08 2:36 Thomas Lau
2014-12-09 10:55 ` Stefan Hajnoczi
2014-12-09 11:21 ` tlau
2014-12-19 10:56 ` Stefan Hajnoczi
2014-12-19 10:59 ` tlau
2014-12-19 18:07 ` Paolo Bonzini
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=549A10A9.2020509@gmail.com \
--to=zhhy.zhanghaoyu@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.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