From: Massimo Colombi <mcolombi1@gmail.com>
To: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: "X86_PV_VCPU_MSRS record truncated" during domain restore
Date: Fri, 22 Jul 2016 17:07:24 +0200 [thread overview]
Message-ID: <384635db-16b4-7fd4-51e7-4368b3a62f0b@gmail.com> (raw)
In-Reply-To: <f3e221d2-2f72-a8f6-54cd-37e34312b2f7@citrix.com>
The patches (that are attached to "[PATCH RFC 0/4] Fix issues with
zero-length records in migration v2") work!
I patched locally qubes-builder to import your patches and recreate rpm
files. These patches also work on Xen 4.6.1.
Best regards,
Massimo
On 07/21/2016 10:53 AM, Andrew Cooper wrote:
> On 21/07/2016 09:39, Massimo Colombi wrote:
>> This is the output of verify-stream-v2:
>>
>> [user@dom0 scripts]$ sudo xl save fedora-23-dvm /fedora-23-dvm-savefile
>> Saving to /fedora-23-dvm-savefile new xl format (info 0x3/0x0/1991)
>> xc: info: Saving domain 4, type x86 PV
>> xc: Frames: 912384/912384 100%
>> xc: End of stream: 0/0 0%
>>
>> [user@dom0 scripts]$ ./verify-stream-v2 -f xl -i /fedora-23-dvm-savefile
>> Stream Error:
>> Traceback (most recent call last):
>> File "./verify-stream-v2", line 82, in read_stream
>> VerifyLibxl(info, stream_read).verify()
>> File "/usr/lib64/python2.7/site-packages/xen/migration/libxl.py",
>> line 82, in verify
>> while self.verify_record() != REC_TYPE_end:
>> File "/usr/lib64/python2.7/site-packages/xen/migration/libxl.py",
>> line 136, in verify_record
>> record_verifiers[rtype](self, content[:length])
>> File "/usr/lib64/python2.7/site-packages/xen/migration/libxl.py",
>> line 155, in verify_record_libxc_context
>> VerifyLibxc(self.info, self.read).verify()
>> File "/usr/lib64/python2.7/site-packages/xen/migration/libxc.py",
>> line 132, in verify
>> while self.verify_record() != REC_TYPE_end:
>> File "/usr/lib64/python2.7/site-packages/xen/migration/libxc.py",
>> line 227, in verify_record
>> record_verifiers[rtype](self, content[:length])
>> File "/usr/lib64/python2.7/site-packages/xen/migration/libxc.py",
>> line 429, in <lambda>
>> VerifyLibxc.verify_record_x86_pv_vcpu_generic(s, x, "msrs"),
>> File "/usr/lib64/python2.7/site-packages/xen/migration/libxc.py",
>> line 323, in verify_record_x86_pv_vcpu_generic
>> " bytes long" % (name, minsz))
>> RecordError: X86_PV_VCPU_msrs record length must be at least 8 bytes long
>>
>>
>> On 07/21/2016 02:10 AM, Andrew Cooper wrote:
>>> Is it possible to do an `xl save` equivalent on the domain, and run
>>> tools/python/scripts/verify-stream-v2 against the resulting file? That
>>> should identify whether it is a malformed X86_PV_VCPU_MSRS record but
>>> otherwise intact stream, or whether the stream becomes corrupted
>>> elsewhere?
>> Thanks for your explanation of the bug.
> I should also improve the reported error message.
>
> Do you mind rerunning with an extra -v to dump a list of the records
> found in the stream?
>
> ~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-07-22 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <nmncv2$m3$1@ger.gmane.org>
[not found] ` <20160720113752.GT1161@mail-itl>
[not found] ` <345d27df-0424-c7bd-a099-d933b0a45c18@gmail.com>
2016-07-20 23:20 ` "X86_PV_VCPU_MSRS record truncated" during domain restore (was: Re: [qubes-users] DispVM Doesn't work) Marek Marczykowski-Górecki
[not found] ` <20160720232009.GA24847@mail-itl>
2016-07-21 0:10 ` "X86_PV_VCPU_MSRS record truncated" during domain restore Andrew Cooper
2016-07-21 8:39 ` Massimo Colombi
2016-07-21 8:53 ` Andrew Cooper
2016-07-21 9:21 ` Massimo Colombi
2016-07-22 15:07 ` Massimo Colombi [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=384635db-16b4-7fd4-51e7-4368b3a62f0b@gmail.com \
--to=mcolombi1@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xen.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).