Hi,
Live migration was working well for me with 3.1.
Recently I move to 3.2, and now live migration does not work anymore.
Here is what i obtain on source node :
----
xm migrate --live webdav node2
Error: /usr/lib/xen-3.2-1/bin/xc_save 26 6 0 0 1 failed
Usage: xm migrate <Domain> <Host>
[...]
----
And in the xend.log (still on the source node) :
----
[2008-03-03 10:12:52 15205] INFO (XendDomainInfo:1504) createDevice: vbd
: {''uuid'':
''be6c074b-5d31-a7fc-26a1-48b1f5e3878a'',
''bootable'': 1,
''devid'': 2049, ''driver'':
''paravirtualised'', ''dev'':
''sda1'', ''uname'':
''phy:/dev/mapper/webdavroot-part1'', ''mode'':
''w''}
[2008-03-03 10:12:52 15205] ERROR (XendDomainInfo:1950)
XendDomainInfo.resume: xc.domain_resume failed on domain 6.
Traceback (most recent call last):
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line
1944, in resumeDomain
self._createDevices()
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line
1506, in _createDevices
devid = self._createDevice(devclass, config)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line
1478, in _createDevice
return self.getDeviceController(deviceClass).createDevice(devConfig)
File
"/usr/lib/xen-3.2-1/lib/python/xen/xend/server/DevController.py",
line 113, in createDevice
raise VmError("Device %s is already connected." % dev_str)
VmError: Device sda1 (2049, vbd) is already connected.
[2008-03-03 10:12:52 15205] DEBUG (XendDomainInfo:1952)
XendDomainInfo.resumeDomain: completed
[2008-03-03 10:12:52 15205] DEBUG (XendCheckpoint:144)
XendCheckpoint.save: resumeDomain
----
On the destination node, the log does not show any error, but the domU
is still
frozen, and the only thing I can do is destroying it (and same thing on
source node,
I should then destroy the domU as it is frozen to) :
----
[2008-03-03 10:12:22 4485] DEBUG (XendCheckpoint:210)
restore:shadow=0x0, _static_max=0x40000000, _static_min=0x0,
[2008-03-03 10:12:22 4485] DEBUG (balloon:132) Balloon: 1050692 KiB
free; need 1048576; done.
[2008-03-03 10:12:22 4485] DEBUG (XendCheckpoint:227) [xc_restore]:
/usr/lib/xen-3.2-1/bin/xc_restore 24 2 1 2 0 0 0
[2008-03-03 10:12:22 4485] INFO (XendCheckpoint:365) xc_domain_restore
start: p2m_size = 40800
[2008-03-03 10:14:34 4485] DEBUG (XendDomainInfo:1883)
XendDomainInfo.destroy: domid=2
[2008-03-03 10:14:34 4485] DEBUG (XendDomainInfo:1900)
XendDomainInfo.destroyDomain(2)
----
After the error, the VM list is like this :
- source node :
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 880 8 r-----
30826.9
...
webdav 6 1024 2
-b---- 12.6
...
- destination node :
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 7033 4
r----- 44.0
webdav 2 1024 0
-bp--- 0.0
For information, the domU is installed on a SAN LUN.
The Xen 3.2 install is the Debian Testing one, and kernel in dom0 is
2.6.18.8 from
Xen source (64 bits dom0).
Have I missed something I should change in config from 3.1 to 3.2 in
order to have
live migration working ? Does anyone has the same problem ?
Any clue is welcome !
Cheers,
--
Yann Cézard - Administrateur Systèmes Serveurs
Centre de Ressources Informatiques de l''UPPA (http://cri.univ-pau.fr)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Yann Cezard a écrit :> Hi, > > Live migration was working well for me with 3.1. > Recently I move to 3.2, and now live migration does not work anymore. > Here is what i obtain on source node : > ---- > xm migrate --live webdav node2 > Error: /usr/lib/xen-3.2-1/bin/xc_save 26 6 0 0 1 failed > Usage: xm migrate <Domain> <Host> > [...] > ---- > > [...] > > For information, the domU is installed on a SAN LUN. > The Xen 3.2 install is the Debian Testing one, and kernel in dom0 is > 2.6.18.8 from > Xen source (64 bits dom0). > > Have I missed something I should change in config from 3.1 to 3.2 in > order to have > live migration working ? Does anyone has the same problem ? > > Any clue is welcome ! > > Cheers, > >After having investigate a little this week, it seems that I can migrate 64bits domU, but not 32 bits ones. In fact, the problem is that "xm save" fails on saving 32 bits domU, and works fine on 64 bits domU. ----------- [2008-03-07 11:06:28 15975] DEBUG (XendCheckpoint:89) [xc_save]: /usr/lib/xen-3.2-1/bin/xc_save 5 7 0 0 0 [2008-03-07 11:06:28 15975] DEBUG (XendCheckpoint:336) suspend [2008-03-07 11:06:28 15975] DEBUG (XendCheckpoint:92) In saveInputHandler suspend [2008-03-07 11:06:28 15975] DEBUG (XendCheckpoint:94) Suspending 7 ... [2008-03-07 11:06:28 15975] DEBUG (XendDomainInfo:467) XendDomainInfo.shutdown(suspend) [2008-03-07 11:06:28 15975] DEBUG (XendDomainInfo:1085) XendDomainInfo.handleShutdownWatch [2008-03-07 11:06:28 15975] DEBUG (XendDomainInfo:1085) XendDomainInfo.handleShutdownWatch [2008-03-07 11:06:28 15975] INFO (XendDomainInfo:1273) Domain has shutdown: name=migrating-scratchy id=7 reason=suspend. [2008-03-07 11:06:28 15975] INFO (XendCheckpoint:99) Domain 7 suspended. [2008-03-07 11:06:28 15975] DEBUG (XendCheckpoint:107) Written done [2008-03-07 11:06:28 15975] ERROR (XendCheckpoint:141) Save failed on domain scratchy (7). Traceback (most recent call last): File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py", line 109, in save forkHelper(cmd, fd, saveInputHandler, False) File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py", line 353, in forkHelper raise XendError("%s failed" % string.join(cmd)) XendError: /usr/lib/xen-3.2-1/bin/xc_save 5 7 0 0 0 failed [2008-03-07 11:06:28 15975] DEBUG (XendDomainInfo:1922) XendDomainInfo.resumeDomain(7) [2008-03-07 11:06:28 15975] DEBUG (XendDomainInfo:1952) XendDomainInfo.resumeDomain: completed [2008-03-07 11:06:28 15975] DEBUG (XendCheckpoint:144) XendCheckpoint.save: resumeDomain ----------- Isn''t it possible to save/migrate 32 bits domU with 64 bits dom0 ? Thanks -- Yann Cézard - Administrateur Systèmes Serveurs Centre de Ressources Informatiques de l''UPPA (http://cri.univ-pau.fr) Bat IFR, rue Jules Ferry, 64000 PAU Tél.: +33 (0)5 59 40 77 94 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seemingly Similar Threads
- Internal error during live migration saving
- Snapshot fail, when snapshot a vm the second time. (already update to xen-4.0.1 and kernel-2.6.32.25)
- Snapshot fail, when snapshot a vm the second time. (already update to xen-4.0.1 and kernel-2.6.32.25)
- Re: Reg REMUS on two VMs
- Xen LVM DRBD live migration