[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Debian wheezy Xen 4.1.4 migration issue with tapdisk
hello? anyone can help me?
J
On 06/07/2013 11:58 AM, Jacek Jarosiewicz wrote:
sorry, the xend.log fragment pasted below is from LIVE migration.
the migration with checkpoint also fails (and I would like to get it up
and running as well as live migration), but with different log message:
[2013-06-05 14:54:54 2714] ERROR (XendDomainInfo:3085)
XendDomainInfo.destroy: domain destruction failed.
Traceback (most recent call last):
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py",
line 3078, in destroy
xc.domain_pause(self.domid)
Error: (3, 'No such process')
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:2406) No device model
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:2408) Releasing devices
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:2414) Removing tap2/51712
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = tap2, device = tap2/51712
[2013-06-05 14:54:54 2714] DEBUG (DevController:649)
deviceDestroyCallback /local/domain/0/backend/vbd/5/51712/hotplug-status.
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:2414) Removing tap2/51728
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = tap2, device = tap2/51728
[2013-06-05 14:54:54 2714] DEBUG (DevController:649)
deviceDestroyCallback /local/domain/0/backend/vbd/5/51728/hotplug-status.
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:2414) Removing vif/0
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:2414) Removing vkbd/0
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = vkbd, device = vkbd/0
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:2414) Removing console/0
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:2414) Removing vfb/0
[2013-06-05 14:54:54 2714] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2013-06-05 14:54:54 2714] ERROR (XendCheckpoint:357)
/usr/lib/xen-4.1/bin/xc_restore 21 5 1 2 0 0 0 0 failed
Traceback (most recent call last):
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendCheckpoint.py",
line 309, in restore
forkHelper(cmd, fd, handler.handler, True)
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendCheckpoint.py",
line 411, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib/xen-4.1/bin/xc_restore 21 5 1 2 0 0 0 0 failed
[2013-06-05 14:54:54 2714] ERROR (XendDomain:1194) Restore failed
Traceback (most recent call last):
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomain.py",
line 1178, in domain_restore_fd
dominfo = XendCheckpoint.restore(self, fd, paused=paused,
relocating=relocating)
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendCheckpoint.py",
line 358, in restore
raise exn
XendError: /usr/lib/xen-4.1/bin/xc_restore 21 5 1 2 0 0 0 0 failed
Cheers,
J
On 06/07/2013 11:26 AM, Jacek Jarosiewicz wrote:
Hi,
I have a problem migrating VMs on Xen 4.1.4 (distribution install in
wheezy).
The actual setup is Opennebula 4.0.1 + Xen
When I try to migrate VM i get the following error in nebula's log:
Wed Jun 5 14:54:54 2013 [VMM][E]: restore: Command "sudo /usr/sbin/xm
restore /var/lib/one//datastores/0/23/checkpoint" failed: Error:
/usr/lib/xen-4.1/bin/xc_restore 21 5 1 2 0 0 0 0 failed
Wed Jun 5 14:54:54 2013 [VMM][E]: Could not restore from
/var/lib/one//datastores/0/23/checkpoint
..and in xend.log i see:
[2013-06-05 15:38:04 24698] INFO (XendDomainInfo:2357) createDevice:
tap2 : {'protocol': 'x86_64-abi', 'uuid':
'8c752883-8b03-5154-a318-aea9d510c99d', 'bootable': 1, 'dev':
'xvda:disk', 'uname':
'tap:tapdisk:aio:/var/lib/one//datastores/0/27/disk.0', 'mode': 'w',
'VDI': '', 'backend': '0'}
[2013-06-05 15:38:04 24698] ERROR (XendDomainInfo:515) VM resume failed
Traceback (most recent call last):
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py",
line 511, in resume
self._createDevices()
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py",
line 2364, in _createDevices
devid = self._createDevice(devclass, config)
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py",
line 2326, in _createDevice
return self.getDeviceController(deviceClass).createDevice(devConfig)
File
"/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/BlktapController.py",
line
174, in createDevice
device = TapdiskController.create(params, file)
File
"/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/BlktapController.py",
line
285, in create
return TapdiskController.exc('create', '-a%s:%s' % (dtype, image))
File
"/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/BlktapController.py",
line
233, in exc
(args, rc, out, err))
TapdiskException: ('create',
'-aaio:/var/lib/one//datastores/0/27/disk.0') failed (512 )
same happens with live migration.
in VM config file I use disk this way:
disk = ['tap2:tapdisk:aio:/var/lib/one//datastores/0/24/disk.0,xvda,w']
..and it works. So my question is - is the blktap2 implementation still
broken in debian wheezy? or is it xen-tools that are broken? or what? :)
Because obviously Xen tries to create disk device using tap:tapdisk:aio:
scheme, which does not work..
How can I fix the issue so that migration works? Please help!
Cheers,
J
--
Jacek Jarosiewicz
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
|
