From: Marcelo Tosatti <mtosatti@redhat.com>
To: Peter Lieven <pl@dlh.net>
Cc: Avi Kivity <avi@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: porting fixes regarding kvm-clock and lost irqs to stable qemu-kvm 0.12.4
Date: Fri, 4 Jun 2010 12:31:02 -0300 [thread overview]
Message-ID: <20100604153102.GB11087@amt.cnet> (raw)
In-Reply-To: <4C06751A.4080507@dlh.net>
On Wed, Jun 02, 2010 at 05:13:30PM +0200, Peter Lieven wrote:
> Hi,
>
> I would like to get latest stable qemu-kvm (0.12.4) to a usable state
> regarding live-migration.
>
> Problems are fixed in git, but there is so much new stuff that has not
> extensively tested and therefore I would like to stay at 0.12.4 at
> the moment.
>
> Therefore I would appreciate your help regarding 2 bugs:
>
> a) -cpu xxx,-kvmclock doesn't work in 0.12.4. It started working first
> after applying a patchset from Avi that is not even in git yet. What
> needs to be done to get it working in 0.12.4 ?
You want to disable kvmclock? -no-kvmclock kernel option.
Note migration should be working fine since kvm.git commit
afbcf7ab8d1bc8c2d04792f6d9e786e0adeb328d.
> b) There is a bug in 0.12.4 which leads to lost irqs. It was reported
> appearing in virtio_blk (#584131) and e1000 (#585113). It is finally
> fixed in GIT. Can someone give me a hint with commit fixed this?
c3f8f61157625d0bb5bfc135047573de48fdc675.
next prev parent reply other threads:[~2010-06-04 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 15:13 porting fixes regarding kvm-clock and lost irqs to stable qemu-kvm 0.12.4 Peter Lieven
2010-06-04 15:31 ` Marcelo Tosatti [this message]
2010-06-04 20:25 ` Peter Lieven
2010-06-05 1:34 ` Faidon Liambotis
2010-06-05 14:58 ` Peter Lieven
2010-06-06 14:53 ` Faidon Liambotis
2010-06-06 16:50 ` Peter Lieven
2010-06-04 20:32 ` Peter Lieven
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=20100604153102.GB11087@amt.cnet \
--to=mtosatti@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
/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;
as well as URLs for NNTP newsgroup(s).