From: "Ing. Ricardo Brisighelli" <ricardo@estilo.com.ar>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Julien Grall <julien.grall@arm.com>, xen-devel@lists.xen.org
Subject: Re: [xl restore and migrating problem - hardware compatibility]
Date: Fri, 23 Dec 2016 19:56:19 -0300 [thread overview]
Message-ID: <11067138.3bJAmV3OH1@rick> (raw)
In-Reply-To: <a0a173e8-fc15-68e9-8e71-46135c8dad6a@citrix.com>
El Vie 23 Dic 2016 17:16:32 Andrew Cooper escribió:
> On 23/12/16 17:00, Andrew Cooper wrote:
> > On 23/12/16 16:32, Ing. Ricardo Brisighelli wrote:
> >> Hi, i'm gentoo user and try with xen 4.6.3 and 4.7.1 in both version
> >> have the
> >> same problem.
> >>
> >> My cpu is AMD A10-7860K
> >
> > This issue has been reported before ("[Xen-devel] "X86_PV_VCPU_MSRS
> > record truncated" during domain restore").
> >
> > I submitted patches to fix it ("Fix issues with zero-length records in
> > migration v2" in July even), which made no progress. As the author of
> > migration v2, and unfortunately of this bug, I stand by v1 of my fix
> > without any further modification.
> >
> > You can find the patches here:
> > https://xenbits.xen.org/gitweb/?p=people/andrewcoop/xen.git;a=shortlog;h=r
> > efs/heads/tools-fix-zero-length-records
> If you don't want to take patches, you should be able to work around the
> issue by booting Xen with
>
> cpuid_mask_ext_ecx=fbffffff
>
> Specifically, you are looking to hide the DBEXT feature from Xen so it
> doesn't choose to insert them into the migration stream to start with.
> This migration bug only manifests when the hardware is capable, but the
> VM isn't using the feature.
>
> ~Andrew
Hi Andrew, first i try boot xen with cpuid_mask_ext_ecx=fbffffff, restore and
migration works well, then try apply the patchs
tools/python: Adjust migration v2 library to warn about...
tools/libxc: Avoid generating inappropriate zero-length...
tools/libxc: Tolerate zero-length records in migration...
remove cpuid_mask, recompile and install xen-4.7.1, reboot and the problem
persist. I'm missing something?
Regards
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-23 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 16:32 [xl restore and migrating problem - hardware compatibility] Ing. Ricardo Brisighelli
2016-12-23 17:00 ` Andrew Cooper
2016-12-23 17:16 ` Andrew Cooper
2016-12-23 22:56 ` Ing. Ricardo Brisighelli [this message]
2016-12-23 23:22 ` Andrew Cooper
2016-12-24 13:24 ` Ing. Ricardo Brisighelli
2016-12-26 20:43 ` Doug Goldstein
2016-12-28 14:50 ` Julien Grall
2017-01-04 11:00 ` Wei Liu
2016-12-28 14:58 ` Julien Grall
2016-12-28 15:00 ` Processed: " xen
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=11067138.3bJAmV3OH1@rick \
--to=ricardo@estilo.com.ar \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.