Re: [Xen-users] HVM migrate failed on both xen 4.1 and xen 4.2

["kevin.zhang@xxxxxxxxxxx" <kevin.zhang@xxxxxxxxxxx>]

ï

Hi Wei Liu,

 

     Thank you for your reply.

     Last week I tested on xen 4.2.3 and Xen 4.1 and find out that it was the XenAPI C binding problems.

     All works well for both xl and xend toolstack now.    

 

---

Best Regards

From: Wei Liu

Date: 2013-12-19 20:06

To: kevin.zhang@xxxxxxxxxxx

CC: xen-users; wei.liu2@xxxxxxxxxx

Subject: Re: [Xen-users] HVM migrate failed on both xen 4.1 and xen 4.2

On Thu, Dec 19, 2013 at 10:20:01AM +0800, kevin.zhang@xxxxxxxxxxx wrote:

> Hi all,

>

>         These days I am testing xen live migration with xen.

> The result is that:

>        PVM migration works well all the time.

>        However, HVM windows vm migration always failed.  I'm using xen 4.1 and 4.2 with NFS as shared storage, and both failed with HVM migration.

> We are mainly using xend toolstack.  After searching for the error messages, I found lots of people had this problem, and it related to hvm restore function bug.

> Could anyone help us? Thank you very much!

> Error messages are:

> [2013-12-19 10:11:45 2027] INFO (XendCheckpoint:260) restore hvm domain 4, apic=1, pae=1

> [2013-12-19 10:11:45 2027] DEBUG (image:337) Stored a VNC password for vfb access

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: boot, val: dc

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: fda, val: None

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: fdb, val: None

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: soundhw, val: None

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: localtime, val: 0

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: serial, val: ['pty']

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: std-vga, val: 0

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: isa, val: 0

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: acpi, val: 1

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: usb, val: 0

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: usbdevice, val: tablet

> [2013-12-19 10:11:45 2027] DEBUG (image:891) args: gfx_passthru, val: None

> [2013-12-19 10:11:45 2027] INFO (image:822) Need to create platform device.[domid:4]

> [2013-12-19 10:11:45 2027] DEBUG (XendCheckpoint:278) restore:shadow=0xc, _static_max=0x40000000, _static_min=0x0,

> [2013-12-19 10:11:45 2027] DEBUG (XendCheckpoint:305) [xc_restore]: /usr/lib/xen/bin/xc_restore 4 4 6 7 1 1 1 0

> [2013-12-19 10:12:10 2027] INFO (XendCheckpoint:423) xc: error: Failed to allocate memory for batch.!: Internal error

 

Looks like this is the culprit?

 

I looked at the code in question in libxc just now. If it *always*

fails, my very wild guess would be the memory size calculation is

broken when restoring HVM domain so that hypervisor fails to allocate

memory for it.

 

It would be worth knowing whether this is a libxc bug or Xend bug. Could

you try xl? If xl works then it's a Xend bug, otherwise this is probably

a bug in libxc.

 

Wei.

 

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