qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: debian-admin@lists.debian.org,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Steal time MSR not set properly during live	migration?
Date: Fri, 28 Aug 2015 16:57:46 +0200 (CEST)	[thread overview]
Message-ID: <1978979044.5160386.1440773866768.JavaMail.zimbra@oxygem.tv> (raw)
In-Reply-To: <557A00AA.2060800@msgid.tls.msk.ru>

Hi,

I have add this bug today on 3 debian jessie guests (kernel 3.16), after migration from qemu 2.3 to qemu 2.4.

Is it a qemu bug or guest kernel 3.16 ?

Regards,

Alexandre Derumier


----- Mail original -----
De: "Michael Tokarev" <mjt@tls.msk.ru>
À: "qemu-devel" <qemu-devel@nongnu.org>, debian-admin@lists.debian.org
Cc: "Marcelo Tosatti" <mtosatti@redhat.com>, "Gleb Natapov" <gleb@redhat.com>
Envoyé: Jeudi 11 Juin 2015 23:42:02
Objet: Re: [Qemu-devel] Steal time MSR not set properly during live	migration?

11.06.2015 23:46, Apollon Oikonomopoulos wrote: 
> On 15:12 Wed 03 Jun , Apollon Oikonomopoulos wrote: 
>> Any ideas? 
> 
> As far as I understand, there is an issue when reading the MSR on the 
> incoming side: there is a KVM_SET_MSRS vcpu ioctl issued by the main 
> thread during initialization, that causes the initial vCPU steal time 
> value to be set using the main thread's (and not the vCPU thread's) 
> run_delay. Then, upon resuming execution, kvm_arch_load_vcpu uses the 
> vCPU thread's run_delay to determine steal time, causing an overflow. 
> The issue was introduced by commit 
> 917367aa968fd4fef29d340e0c7ec8c608dffaab. 
> 
> For the full analysis, see https://bugs.debian.org/785557#64 and the 
> followup e-mail. 

Adding Cc's... 

Thanks, 

/mjt 

      reply	other threads:[~2015-08-28 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 12:12 [Qemu-devel] Steal time MSR not set properly during live migration? Apollon Oikonomopoulos
2015-06-11 20:46 ` Apollon Oikonomopoulos
2015-06-11 21:42   ` Michael Tokarev
2015-08-28 14:57     ` Alexandre DERUMIER [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=1978979044.5160386.1440773866768.JavaMail.zimbra@oxygem.tv \
    --to=aderumier@odiso.com \
    --cc=debian-admin@lists.debian.org \
    --cc=gleb@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).