Denis Chapligin
2009-Jul-07 17:25 UTC
[Xen-devel] xmp domU migration problem with latest Xen 3.4.1 and linux-2.6.18-xen
Hi Guys on #xen@freenode recommend me to write here. I have two nodes, with two Xeon@#GHz processors without HVM, but with EM64T support. Those nodes are running xen-3.4.1-rc hypervisors (i''ve tried both 64 bit and 32 bit versions) and dom0 with latest 2.6.18.8 kernel from xen''s hg repository. Also i have a domU with the same 2.6.18.8 kernel, runnig with ''vcpus=2'' setting in domain config file. domu runs okay, but when i try to migrate it to other host (both live and not live), domain disappears. Logs show me, that it wasn''t restored on the recepient host. Here goes some technical info: xm dmesg after migration attempt on recepient host: (XEN) mm.c:721:d0 Bad L1 flags 80000000 (XEN) mm.c:1135:d0 Failure in alloc_l1_table: entry 76 (XEN) mm.c:2061:d0 Error while validating mfn a404a (pfn 13eb) for type 20000000: caf=80000002 taf=20000001 (XEN) mm.c:812:d0 Attempt to create linear p.t. with write perms (XEN) mm.c:1295:d0 Failure in alloc_l2_table: entry 64 (XEN) mm.c:2061:d0 Error while validating mfn a510c (pfn 101a4) for type 40000000: caf=80000002 taf=40000001 (XEN) mm.c:1384:d0 Failure in alloc_l3_table: entry 0 (XEN) mm.c:2061:d0 Error while validating mfn a43ab (pfn 1081) for type 60000000: caf=80000002 taf=60000001 (XEN) mm.c:2695:d0 Error while pinning mfn a43ab xend.log entries: [2009-07-07 20:21:12 2134] INFO (XendCheckpoint:417) Reloading memory pages: 0 % [2009-07-07 20:21:16 2134] INFO (XendCheckpoint:417) Received all pages (0 races ) [2009-07-07 20:21:16 2134] INFO (XendCheckpoint:417) ERROR Internal error: Faile d to pin batch of 11 page tables [2009-07-07 20:21:16 2134] INFO (XendCheckpoint:417) Restore exit with rc=1 uname -a on dom0: Linux host 2.6.18.8 #1 SMP Tue Jul 7 18:42:07 EEST 2009 i686 GNU/Linux uname -a on domU Linux domU 2.6.18.8 #1 SMP Tue Jul 7 18:42:07 EEST 2009 i686 GNU/Linux xm info: host : host release : 2.6.18.8 version : #1 SMP Tue Jul 7 18:42:07 EEST 2009 machine : i686 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2992 hw_caps : bfebfbff:20100000:00000000:00000180:0000641d:00000000:0 0000000:00000000 virt_caps : total_memory : 4095 free_memory : 3538 node_to_cpu : node0:0-3 node_to_memory : node0:3538 xen_major : 3 xen_minor : 4 xen_extra : xen_caps : xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : infernix cc_compile_domain : infernix.net cc_compile_date : Tue Jul 7 13:38:30 EEST 2009 xend_config_format : 4 How can i fix this problem? -- Denis Chapligin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2009-Jul-07 18:49 UTC
Re: [Xen-devel] xmp domU migration problem with latest Xen 3.4.1 and linux-2.6.18-xen
On 07/07/2009 18:25, "Denis Chapligin" <chollya@satgate.net> wrote:> I have two nodes, with two Xeon@#GHz processors without HVM, but with > EM64T support. Those nodes are running xen-3.4.1-rc hypervisors (i''ve > tried both 64 bit and 32 bit versions) and dom0 with latest 2.6.18.8 > kernel from xen''s hg repository. > > Also i have a domU with the same 2.6.18.8 kernel, runnig with ''vcpus=2'' > setting in domain config file. domu runs okay, but when i try to > migrate it to other host (both live and not live), domain disappears. > Logs show me, that it wasn''t restored on the recepient host. > > Here goes some technical info: > > xm dmesg after migration attempt on recepient host:Probably one host supports NX (No Execute aka eXecute Disable) and the other doesn''t. Try adding the following line to your domain config file: cpuid=[''0x80000001:edx=xxxxxxxxxxx0xxxxxxxxxxxxxxxxxxxx''] -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel