xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Anthony Perard <anthony.perard@citrix.com>,
	"zhigang.x.wang@oracle.com" <zhigang.x.wang@oracle.com>
Subject: Re: live migrating hvm from 4.4 to 4.7 fails in ioreq server
Date: Fri, 29 Jul 2016 13:22:39 +0000	[thread overview]
Message-ID: <333f8015cd9e4d6bb68380cbdf898689@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20160729131029.GA16164@aepfle.de>

> -----Original Message-----
> From: Olaf Hering [mailto:olaf@aepfle.de]
> Sent: 29 July 2016 14:11
> To: Paul Durrant
> Cc: Stefano Stabellini; Wei Liu; Andrew Cooper; xen-devel@lists.xen.org;
> Anthony Perard; zhigang.x.wang@oracle.com
> Subject: Re: [Xen-devel] live migrating hvm from 4.4 to 4.7 fails in ioreq
> server
> 
> On Fri, Jul 29, Paul Durrant wrote:
> 
> > >   Could you give the attached patch a try? I believe it should solve the
> > > problem.
> 
> Thanks Paul. I tested it with 4.4.20160610T12110 dom0 as sender and
> 4.6.20160620T12082 as receiver.
> 
> 
> Initially the result was this:
> 
> # cat /var/log/xen/qemu-dm-fv-x64-sles12sp1-clean--incoming.log
> char device redirected to /dev/pts/3 (label serial0)
> xen: ioreq server create: Cannot allocate memory
> qemu-system-x86_64: xen hardware virtual machine initialisation failed
> 
> 
> Now the result it this:
> root@anonymi:~ # cat /var/log/xen/qemu-dm-fv-x64-sles12sp1-clean--
> incoming.log
> char device redirected to /dev/pts/3 (label serial0)
> xen_ram_alloc: do not alloc f800000 bytes of ram at 0 when runstate is
> INMIGRATE
> xen_ram_alloc: do not alloc 800000 bytes of ram at f800000 when runstate is
> INMIGRATE
> xen_ram_alloc: do not alloc 10000 bytes of ram at 10000000 when runstate is
> INMIGRATE
> xen_ram_alloc: do not alloc 40000 bytes of ram at 10010000 when runstate is
> INMIGRATE
> Unknown savevm section or instance 'kvm-tpr-opt' 0
> qemu-system-i386: load of migration failed: Invalid argument
> 
> So appearently it got past the point of the ioreq server issue.
> 

Yes, it certainly looks like it.

> 
> The "kvm-tpr-opt" thing was briefly discussed on 12 May 2016.
> 

I'll have a look for that.

Thanks,

  Paul

> Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-07-29 13:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 12:18 live migrating hvm from 4.4 to 4.7 fails in ioreq server Olaf Hering
2016-05-11 12:22 ` Andrew Cooper
2016-05-11 12:30   ` Olaf Hering
2016-05-11 13:07     ` Olaf Hering
2016-05-12 10:53       ` Wei Liu
2016-05-11 12:38   ` Paul Durrant
2016-05-12 10:55     ` Wei Liu
2016-05-12 12:39       ` Paul Durrant
2016-05-12 13:01         ` Wei Liu
2016-05-12 13:03           ` Paul Durrant
2016-05-12 13:18             ` Olaf Hering
2016-05-12 14:10             ` Wei Liu
2016-05-12 14:13               ` Paul Durrant
2016-05-25 20:57                 ` Konrad Rzeszutek Wilk
2016-05-26  8:30                   ` Paul Durrant
2016-06-03 20:07                     ` Konrad Rzeszutek Wilk
2016-07-26 15:45                     ` Olaf Hering
2016-07-26 15:48                       ` Paul Durrant
2016-07-29 10:11                         ` Paul Durrant
2016-07-29 10:34                           ` Paul Durrant
2016-07-29 13:10                             ` Olaf Hering
2016-07-29 13:22                               ` Paul Durrant [this message]
2016-05-12 13:38           ` Stefano Stabellini

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=333f8015cd9e4d6bb68380cbdf898689@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=zhigang.x.wang@oracle.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).