[Xen-bugs] [Bug 1328] New: live migration with DomU's vcpu = 1

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1328

           Summary: live migration with DomU's vcpu = 1
           Product: Xen
           Version: 3.0.1
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ikedaj@xxxxxxxxxxxxxxxxx


I am trying to have DomU migrate with --live option,
and notice the following behavior.

case 1)
Dom0's vcpu = 4, DomU's vcpu = 1
live migration is really unstable...
if xend is restarted, the migration might succeed, but it's still unstable.

/var/log/xen/xend.log (destination node)

[2008-08-19 17:30:03 xend 13275] DEBUG (balloon:127) Balloon: 4202040 KiB free;
need 2097152; done.
[2008-08-19 17:30:03 xend 13275] DEBUG (XendCheckpoint:215) [xc_restore]:
/usr/lib64/xen/bin/xc_restore 4 6 1 2 0 0 0
[2008-08-19 17:30:07 xend 13275] INFO (XendCheckpoint:351) ERROR Internal
error: read: p2m_size
[2008-08-19 17:30:07 xend 13275] INFO (XendCheckpoint:351) Restore exit with
rc=1
[2008-08-19 17:30:07 xend.XendDomainInfo 13275] DEBUG (XendDomainInfo:1560)
XendDomainInfo.destroy: domid=6
[2008-08-19 17:30:07 xend.XendDomainInfo 13275] DEBUG (XendDomainInfo:1568)
XendDomainInfo.destroyDomain(6)
[2008-08-19 17:30:07 xend.XendDomainInfo 13275] ERROR (XendDomainInfo:1575)
XendDomainInfo.destroy: xc.domain_destroy failed.
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
1573, in destroyDomain
    xc.domain_destroy(self.domid)
Error: (3, 'No such process')
[2008-08-19 17:30:07 xend 13275] ERROR (XendDomain:278) Restore failed
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 273,
in domain_restore_fd
    return XendCheckpoint.restore(self, fd)
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line
219, in restore
    forkHelper(cmd, fd, handler.handler, True)
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line
339, in forkHelper
    raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_restore 4 6 1 2 0 0 0 failed


case 2)
Dom0's vcpu = 4, DomU's vcpu = 2
it's seems that the migration is sure to be done well.

case 3)
Dom0's vcpu = 1, DomU's vcpu = 1
I set "nosmp" in /boot/grub/menu.lst on both of Dom0 and DomU.
the migration process also works well.


and I found the following bug entry.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=134

Is this fix still available ?
There is no suspend/resume functions in Xen 3.0.


# xm info
host                   : x3650c
release                : 2.6.18-92.el5xen
version                : #1 SMP Tue Apr 29 13:31:30 EDT 2008
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
sockets_per_node       : 2
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2992
hw_caps                :
bfebfbff:20000800:00000000:00000140:0004e3bd:00000000:00000001
total_memory           : 16383
free_memory            : 10
node_to_cpu            : node0:0-3
xen_major              : 3
xen_minor              : 1
xen_extra              : .2-92.el5
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.2 20071124 (Red Hat 4.1.2-41)
cc_compile_by          : brewbuilder
cc_compile_domain      : build.redhat.com
cc_compile_date        : Tue Apr 29 13:12:52 EDT 2008
xend_config_format     : 2


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs