Re: [Xen-devel] [BUG] Rhel7u2 guest with kernel 4.6.0 restore and migrate failed

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

On Mon, Jun 13, 2016 at 09:07:14AM +0100, Wei Liu wrote:
> CC Anthony and Stefano
> 
> Anthony, I think this is also related to the QEMU mainline migration
> failure.

I don't think it is. The quote does not have anything regarding using
QEMU mainline. Also the migration failure in mainline does not affect
any release.

> On Mon, Jun 13, 2016 at 05:59:48AM +0000, Zhang, PengtaoX wrote:
> > Bug detailed description:
> > ----------------
> > 1. Rhel7u2 guest with kernel 4.6.0 migrate failed
> > 2. Rhel7u2 guest with kernel 4.6.0 restore failed
> > 3. Rhel7u2 guest with default kernel (3.10.0) can be restored and migrate 
> > successfully
> > 
> > Environment :
> > ----------------
> > HW: Skylake-SP
> > Xen: Xen 4.7.0 RC4
> > Dom0: Linux 4.5.2 stable
> > 
> > Reproduce steps:
> > ----------------
> > Prepare test environment 
> > 1.Install redhat 6.7 OS on Skylake-SP platform  as base OS , then compile 
> > and install  ,xen and Dom0, reboot from xen .
> > 2.Create a rhel7.2 guest with kernel 4.6.0 via :
> >     xl create config.rhel7u2-4.6
> > 
> > Save/Restore test
> > 1.After boot up guest with kernel 4.6.0 then :
> >     xl save $dom_id $save_guest.img
> > 2.After save guest do
> >     xl restore $save_guest.img
> > 3.Current status is guest with kernel 4.6.0 can be save successfully ,but 
> > restore guest failed . Guest with default kernel can be save/restore 
> > successfully .
> > 
> > Migrate test 
> > 1. After boot up guest with kernel 4.6.0 then :
> >     xl migrate $dom_id localhost 
> > 2. Current status is guest with kernel 4.6.0 migrate failed . Guest with 
> > default kernel can be migrate successfully .
> > 
> > Base error log:
> > ----------------
> > rhel7u2_4.6.0_SR_fail.log file only for Save/Restore test , other log file 
> > are for migrate test .
> > 
> > 
> > Regards,
> > Pengtao
> > 
> > 
> 
> 
> In the QEMU log file:
> 
>   qemu-system-i386: Expected vmdescription section, but got 0

I've seen this log message, it does not appear to affect the migration,
as migration usully succeed and this message is always present. I
haven't investigate.

> That means should_send_vmdesc() returns true in migration/savevm.c.
> 
> It could be that we need to explicitly set supress_vmdesc in machine
> description.

That won't work, we should be able to use QEMU with -machine xenfv or
-machine pc,accel=xen.

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel