WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Problem migrating domains

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Problem migrating domains
From: "Pierre Petliczew" <Pierre.Petliczew@xxxxxx>
Date: Wed, 27 Feb 2008 17:29:16 +0100
Delivery-date: Wed, 27 Feb 2008 08:29:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello list !

I got a problem concerning migration of domUs.

After starting migration with 'xm migrate domdirectinstall xxx.xxx.xxx.xxx' 
domU appears at xm top as 'migrating-domdirectinstall' (Source) and as 
'domdirectinstall' (Target).

But then nothing happens. It seems that the command hangs up. So logging up on 
the consol with 'xm console migrating-domdirectinstall' (Host) I got the 
following output on the console.

talaos:~ # xm console migrating-domdirectinstall
Setting mem allocation to 131072 kiB
------------[ cut here ]------------
kernel BUG at include/asm/mach-xen/asm/maddr.h:34!
invalid opcode: 0000 [#1]
SMP
last sysfs file: /devices/xen/vif-0/net/eth0/type
Modules linked in: iptable_filter ip_tables ip6table_filter ip6_tables x_tables 
                                                                             
ipv6 nfs lockd nfs_acl sunrpc dm_rdac scsi_mod dm_hp_sw dm_emc dm_multipath 
af_p                                                                            
 acket dm_snapshot dm_mod xenblk xennet
CPU:    0
EIP:    0061:[<c01107d9>]    Tainted: G      N VLI
EFLAGS: 00010006   (2.6.22.17-0.1-xen #1)
EIP is at pgd_walk+0xe1/0x19a
eax: 00055555   ebx: 55555000   ecx: 55555061   edx: 00008800
esi: 00000001   edi: c1613000   ebp: c1613000   esp: c17e7f4c
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0069
Process suspend (pid: 1641, ti=c17e6000 task=c6aa4030 task.ti=c17e6000)
Stack: 00000000 00000000 00000061 01613000 00000001 00000000 00000000 c0110a56
       c1c46260 c011120b c17e7fc4 c022a646 c022a97e c6aa4030 6332edf5 00000032
       00000000 c6aa4154 c1bee880 00000000 c0395e40 c6a87f4c 00000003 00000001
Call Trace:
 [<c0110a56>] __pgd_pin+0x17/0x36
 [<c011120b>] mm_pin_all+0x32/0x4a
 [<c022a646>] xen_suspend+0x0/0x30
 [<c022a97e>] take_machine_down+0x7e/0x382
 [<c022a646>] xen_suspend+0x0/0x30
 [<c022ad0d>] __xen_suspend+0x8b/0xba
 [<c022a653>] xen_suspend+0xd/0x30
 [<c012be42>] kthread+0x38/0x5e
 [<c012be0a>] kthread+0x0/0x5e
 [<c0104b43>] kernel_thread_helper+0x7/0x10
 =======================
Code: 24 08 c1 fb 05 c1 e3 0c 09 d9 f6 c1 01 74 3b 89 c8 c1 e8 0c 80 3d 5a 3b 
36                                                                              
c0 00 75 22 8b 15 80 57 3f c0 85 d2 74 08 39 d0 72 04 <0f> 0b eb fe c1 e0 02 03 
                                                                             05 
a4 86 39 c0 8b 00 25 ff ff ff 7f c1
EIP: [<c01107d9>] pgd_walk+0xe1/0x19a SS:ESP 0069:c17e7f4c


Host is a P4 and target is pretty old Athlon at 1GHz, but architecture should 
be the same (x86) or am I wrong at that point.

-Pierre


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Problem migrating domains, Pierre Petliczew <=