From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Glauber Costa <glommer@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"quintela@redhat.com" <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PULL] Migration of misc devices
Date: Mon, 18 Apr 2011 10:44:15 -0500 [thread overview]
Message-ID: <4DAC5C4F.2080500@codemonkey.ws> (raw)
In-Reply-To: <4DAC5A65.6040405@siemens.com>
On 04/18/2011 10:36 AM, Jan Kiszka wrote:
> On 2011-04-18 17:12, Anthony Liguori wrote:
>> On 04/17/2011 03:08 PM, Juan Quintela wrote:
>>>
>>>
>>> The following changes since commit a0102082de4026833afbd2525e8a6320d1f92885:
>>>
>>> usb: fix spelling errors in usb-linux.c (2011-04-16 12:24:28 +0100)
>>>
>>> are available in the git repository at:
>>> git://repo.or.cz/qemu/quintela.git vmstate-misc-devices-v2
>>
>> Migration appears to be broken for me. It's not caused by this series
>> but I'm surprised you didn't encounter it. Maybe it's my kernel version?
>>
>> My suspicion is that the cause of this is:
>>
>> commit 0ec329dab938e2d97d12a91f8ed15fec27b325e0
>> Author: Jan Kiszka <jan.kiszka@siemens.com>
>> Date: Mon Feb 7 12:19:26 2011 +0100
>>
>> kvm: x86: Introduce kvmclock device to save/restore its state
>
> Can you prove your suspicion a bit by retrying with -cpu ...,-kvmclock?
> Is your guest using kvmclock? Are you migrating from old to new or
> between new versions?
Heh, it turns out I was migrating from KVM to TCG :-)
This changeset "breaks" that but I don't think I'd count this as a
supported use-case so I don't count it as a regression.
So ignore the noise here.
Regards,
Anthony Liguori
> Jan
>
next prev parent reply other threads:[~2011-04-18 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 20:08 [Qemu-devel] [PULL] Migration of misc devices Juan Quintela
2011-04-18 15:12 ` Anthony Liguori
2011-04-18 15:36 ` Jan Kiszka
2011-04-18 15:44 ` Anthony Liguori [this message]
2011-04-18 15:54 ` Jan Kiszka
2011-04-18 16:42 ` Juan Quintela
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=4DAC5C4F.2080500@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=glommer@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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;
as well as URLs for NNTP newsgroup(s).