All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: Wei Liu <wei.liu2@citrix.com>, George Dunlap <george.dunlap@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	osstest service owner <osstest-admin@xenproject.org>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [xen-unstable test] 128240: regressions - FAIL
Date: Mon, 01 Oct 2018 20:02:13 +0200	[thread overview]
Message-ID: <76dd7d919faa6560aa025b4eb57301e97914b26b.camel@suse.com> (raw)
In-Reply-To: <20181001153557.y4jgo37xzbaa5tgg@zion.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1308 bytes --]

On Mon, 2018-10-01 at 16:35 +0100, Wei Liu wrote:
> On Mon, Oct 01, 2018 at 04:19:07PM +0100, George Dunlap wrote:
> > Wait, the migration code reads the scheduler parameters -- even if
> > these
> > have not been explicitly set by the admin -- and sends them along
> > with
> > the migration stream?  And if the remote scheduler is different,
> > the
> > migration fails?
> > 
> > That's not so good. :-)
> 
> But one can argue that the guest is specific configured that way so
> it's
> parameters should be preserved. We normally analyse things on a case
> by
> case basis.
> 
Sure, but then this means that, in the restore path, we should query
the scheduler which is in use on the host.

If it is the same one that we also see in the migration stream, we try
to set the parameters. If it is a different one, we skip the setparam
all together (which is basically what Juergen is suggesting later in
the thread, AFAICT).

I don't think I've ever worked on migration, but I can try to look into
fixing this (tomorrow).

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2018-10-01 18:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30 21:59 [xen-unstable test] 128240: regressions - FAIL osstest service owner
2018-10-01  9:04 ` Jan Beulich
2018-10-01 14:33   ` Wei Liu
2018-10-01 15:10     ` Jan Beulich
2018-10-01 15:17       ` Wei Liu
2018-10-01 15:19         ` George Dunlap
2018-10-01 15:35           ` Wei Liu
     [not found]             ` <fc2bbc89cfc7d9066fe0b1fd76ddd2ff@citrix.com>
     [not found]               ` <26110706a1830c111efd93ec76accd40@citrix.com>
     [not found]             ` <fc2bbc89„cfc7„d906„6fe0„b1fd76ddd2ff@citrix.com>
2018-10-01 15:40             ` Andrew Cooper
2018-10-01 15:48               ` George Dunlap
2018-10-01 16:07                 ` Juergen Gross
2018-10-01 17:58                   ` Dario Faggioli
2018-10-02 10:06                     ` George Dunlap
2018-10-02 10:36                       ` Dario Faggioli
2018-10-02  8:29                   ` Jan Beulich
     [not found]                   ` <5BB32C7802000078001ED8FA@suse.com>
2018-10-02  9:24                     ` Dario Faggioli
2018-10-02  9:36                       ` Jan Beulich
     [not found]                       ` <5BB33C3202000078001ED99C@suse.com>
2018-10-02  9:58                         ` Dario Faggioli
2018-10-01 18:02             ` Dario Faggioli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-02  8:45 Juergen Gross
     [not found] <osstest128240mainreport@xen.org>
     [not found] <osstest„128240„mainreport@xen.org>

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=76dd7d919faa6560aa025b4eb57301e97914b26b.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@citrix.com \
    --cc=osstest-admin@xenproject.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.