From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: pv 2.6.31 (kernel.org) and save/migrate, domU BUG Date: Sun, 8 Nov 2009 16:20:19 +0200 Message-ID: <20091108142019.GL1434@reaktio.net> References: <20091107110905.GB1434@reaktio.net> <373a54d1-3dec-4185-b1ca-0363e14329b4@default> <20091108141743.GK1434@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20091108141743.GK1434@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: Jeremy Fitzhardinge , "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org On Sun, Nov 08, 2009 at 04:17:43PM +0200, Pasi K=E4rkk=E4inen wrote: > On Sat, Nov 07, 2009 at 07:32:49AM -0800, Dan Magenheimer wrote: > > > > Well, first, I got 2.6.31.5 to boot in a PV guest in another > > > > machine and it fails to save also. Are you able to save > > > > 2.6.31{,.5} successfully? On latest xen-unstable? > > > > (NOTE: Yes, I do have CONFIG_XEN_SAVE_RESTORE=3Dy... don't > > > > know if that is important.) > > >=20 > > > I'll have to try it later today.. > >=20 > > Let me know. > >=20 >=20 > Ok. I just tried with a Fedora 12 (rawhide) PV guest. I was able to=20 > "xm save" and "xm restore" it without problems.=20 >=20 > But I noticed there was a BUG printed on the guest console: > http://pasik.reaktio.net/xen/debug/dmesg-2.6.31.5-122.fc12.x86_64-saver= estore.txt >=20 > BUG: sleeping function called from invalid context at kernel/mutex.c:94 > in_atomic(): 0, irqs_disabled(): 1, pid: 1052, name: kstop/0 > Pid: 1052, comm: kstop/0 Not tainted 2.6.31.5-122.fc12.x86_64 #1 > Call Trace: > [] __might_sleep+0xe6/0xe8 > [] mutex_lock+0x22/0x4e > [] dpm_resume_noirq+0x21/0x11f > [] xen_suspend+0xca/0xd1 > [] stop_cpu+0x8c/0xd2 > [] worker_thread+0x18a/0x224 > [] ? autoremove_wake_function+0x0/0x39 > [] ? _spin_unlock_irqrestore+0x19/0x1b > [] ? worker_thread+0x0/0x224 > [] kthread+0x91/0x99 > [] child_rip+0xa/0x20 > [] ? int_ret_from_sys_call+0x7/0x1b > [] ? retint_restore_args+0x5/0x6 > [] ? child_rip+0x0/0x20 >=20 Oh, I forgot to mention that this BUG is non-fatal. The guest still works after that.. -- Pasi >=20 > More information about my setup: >=20 > Host/dom0: Fedora 12 (latest rawhide) with included Xen 3.4.1-5 and > custom 2.6.31.5 x86_64 pv_ops dom0 kernel (a couple of days old). >=20 > Guest/domU: Fedora 12 (latest rawhide) with the included/default > 2.6.31.5-122.fc12.x86_64 kernel. >=20 > > > > (On the machine I couldn't boot 2.6.31.5 as a PV guest, there > > > > was absolutely no console output. However, I think tools > > > > are out-of-date on that machine so ignore that.) > > >=20 > > > Did you have "console=3Dhvc0 earlyprintk=3Dxen" in the domU kernel > > > parameters? > >=20 > > No, but that didn't work either. > >=20 >=20 > Ok.. then it crashes really early. >=20 > > > You might also change the xen guest cfgfile so that you have > > > on_crash=3Dpreserve and then when the PV guest is crashed run this: > > >=20 > > > /usr/lib/xen/bin/xenctx -s System.map-domUkernelversion > > >=20 > > > (if you have 64b host the xenctx binary might be under /usr/lib64/) > > >=20 > > > to get a stack trace.. > >=20 > > Very interesting and useful! I was completely unaware of > > xenctx and could have used it many times in tmem development! > >=20 > > The results explain why I can get it to run on > > one machine (an older laptop) and not run on another > > machine (a Nehalem system)... looks like this is maybe > > related to the cpuid-extended-topology-leaf bug that Jeremy > > sent a fix for upstream recently. > >=20 >=20 > Did you try with that patch applied?=20 >=20 > -- Pasi >=20 > > cs:eip: e019:c040342d xen_cpuid+0x46=20 > > flags: 00001206 i nz p > > ss:esp: e021:c0779ee4 > > eax: 00000001 ebx: 00000002 ecx: 00000100 edx: 00000001 > > esi: c0779f1c edi: c0779f18 ebp: c0779f24 > > ds: e021 es: e021 fs: 00d8 gs: 0000 > > Code (instr addr c040342d) > > 24 04 8b 15 a4 02 7c c0 89 54 24 08 8b 0e 0f 0b 78 65 6e 0f a2 <89> 4= 5 00 8b 04 24 89 18 89 0e 89=20 > >=20 > >=20 > > Stack: > > c0779f20 ffffffff ffffffff c07c0360 c0779f18 c0779f1c c0779f20 c066f= d0f > > c0779f18 c0779f24 00000002 16aee301 00000001 00000001 16aee301 00000= 002 > > 0000000b c07c03cc c07c0360 c07c0360 c07c03d8 c0670ed8 c0779f58 00000= 001 > > c07c0360 c0779f60 c066fe6a c0779f60 c0779f60 00000003 00000001 00000= 000 > >=20 > > Call Trace: > > [] xen_cpuid+0x46 <-- > > [] detect_extended_topology+0xae=20 > > [] init_intel+0x140=20 > > [] init_scattered_cpuid_features+0x82=20 > > [] identify_cpu+0x22d=20 > > [] xen_force_evtchn_callback+0xc=20 > > [] check_events+0x8=20 > > [] identify_boot_cpu+0xa=20 > > [] check_bugs+0x8=20 > > [] start_kernel+0x2a0=20 > > [] xen_start_kernel+0x340=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel