Re: [Xen-devel] shutdown/migration stop working on paravirt domU

[Vasiliy Tolstov <v.tolstov@xxxxxxxxx>]

2012/1/19 Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx>:
>> >
>> > Which kernel version of DomU?
>>
>> 2.6.32.26 from xen git tree and Â2.6.18-194.26.1.el5xen
>
> First order is to upgrade your kernel and see if the problem exists
> with a newer 2.6.32.X tree. then also try 3.0 or 3.1 kernel.
>>


This is possible, but my question is - why on some version of the
kernel on same node some damins coud not properly watch xenstore?

>>
>> >
>> > Play a bit with xenctx to get an idea where the guest is stuck at.
>> >
>>
>> Ok, nice. When i need to run xenctx and what i need to see in its output?
>
> <sigh> Google for it. There should be tons of examples of how to use it
> to figure out where the guest is stuck at.

Ok. I create two equal domU with memory=512M and maxmemory = 512M,
copy System.map to dom0 and check xenctx output. Domains runs on same
node and only differs in uptime.
Domain, that correct works on xenstore watches:

/usr/lib64/xen/bin/xenctx -s /root/System.map-2.6.32.26 --stack-trace -a 178
rip: ffffffff810093aa hypercall_page+0x3aa
flags: 00001246 i z p
rsp: ffffffff81539f00
rax: 0000000000000000   rcx: ffffffff810093aa   rdx: ffffffff810093aa
rbx: ffffffff81595ac0   rsi: 0000000000000000   rdi: 0000000000000001
rbp: ffffffff81539f18    r8: 0000000000000000    r9: ffff880003130398
r10: 0000000000000000   r11: 0000000000000246   r12: 6db6db6db6db6db7
r13: ffffffff815e1cc0   r14: ffffffff815e3720   r15: 0000000000000000
 cs: e033        ss: e02b        ds: 0000        es: 0000
 fs: 0000 @ 00007f4f534bd740
 gs: 0000 @ ffff8800030cd000/0000000000000000

cr0: 8005003b
cr2: 7f8497d2d130
cr3: 8644bd000
cr4: 00002660

dr0: 00000000
dr1: 00000000
dr2: 00000000
dr3: 00000000
dr6: ffff0ff0
dr7: 00000400
Code (instr addr ffffffff810093aa)
cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b
59 c3 cc cc cc cc cc cc cc


Stack:
 ffff8800030c0000 0000000000000000 ffffffff8100e19b ffffffff81539f28
 ffffffff8101835c ffffffff81539f48 ffffffff81010320 ffffffff815e3720
 0000000000000000 ffffffff81539f58 ffffffff813d2ab2 ffffffff81539f98
 ffffffff815afd34 ffffffff81539f98 ffffffff815e3720 00000000016c6818

Stack Trace:
* [<ffffffff810093aa>] hypercall_page+0x3aa  <--
    ffff8800030c0000
    0000000000000000
  [<ffffffff8100e19b>] xen_safe_halt+0x10
    ffffffff81539f28
  [<ffffffff8101835c>] default_idle+0x25
    ffffffff81539f48
  [<ffffffff81010320>] cpu_idle+0x58
    ffffffff815e3720
    0000000000000000
    ffffffff81539f58
  [<ffffffff813d2ab2>] rest_init+0x66
    ffffffff81539f98
  [<ffffffff815afd34>] start_kernel+0x3a2
    ffffffff81539f98
    ffffffff815e3720
    00000000016c6818
    0000000000000000
    0000000000000000
    0000000000000000
    ffffffff81539fb8
  [<ffffffff815af2c3>] x86_64_start_reservations+0xae
    ffffffff815a65a0
    ffffffff81001000
    ffffffff81539ff8
  [<ffffffff815b1762>] xen_start_kernel+0x41d
    809822011f898975
    000106a500100800
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000


Domain that not notified on xenstore watches:
/usr/lib64/xen/bin/xenctx -s /root/System.map-2.6.32.26 --stack-trace -a 676
rip: ffffffff810093aa hypercall_page+0x3aa
flags: 00001246 i z p
rsp: ffffffff81539f00
rax: 0000000000000000   rcx: ffffffff810093aa   rdx: ffffffff810093aa
rbx: ffffffff81595ac0   rsi: 0000000000000000   rdi: 0000000000000001
rbp: ffffffff81539f18    r8: 0000000000000000    r9: ffffffff81690380
r10: 0000000102299e62   r11: 0000000000000246   r12: 6db6db6db6db6db7
r13: ffffffff815e1cc0   r14: ffffffff815e3720   r15: 0000000000000000
 cs: e033        ss: e02b        ds: 0000        es: 0000
 fs: 0000 @ 00007fa607454700
 gs: 0000 @ ffff880002f36000/0000000000000000

cr0: 8005003b
cr2: 7f07e7a480a0
cr3: b3c37f000
cr4: 00002660

dr0: 00000000
dr1: 00000000
dr2: 00000000
dr3: 00000000
dr6: ffff0ff0
dr7: 00000400
Code (instr addr ffffffff810093aa)
cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b
59 c3 cc cc cc cc cc cc cc


Stack:
 ffff880002f30000 0000000000000000 ffffffff8100e19b ffffffff81539f28
 ffffffff8101835c ffffffff81539f48 ffffffff81010320 ffffffff815e3720
 0000000000000000 ffffffff81539f58 ffffffff813d2ab2 ffffffff81539f98
 ffffffff815afd34 ffffffff81539f98 ffffffff815e3720 00000000016c6818

Stack Trace:
* [<ffffffff810093aa>] hypercall_page+0x3aa  <--
    ffff880002f30000
    0000000000000000
  [<ffffffff8100e19b>] xen_safe_halt+0x10
    ffffffff81539f28
  [<ffffffff8101835c>] default_idle+0x25
    ffffffff81539f48
  [<ffffffff81010320>] cpu_idle+0x58
    ffffffff815e3720
    0000000000000000
    ffffffff81539f58
  [<ffffffff813d2ab2>] rest_init+0x66
    ffffffff81539f98
  [<ffffffff815afd34>] start_kernel+0x3a2
    ffffffff81539f98
    ffffffff815e3720
    00000000016c6818
    0000000000000000
    0000000000000000
    0000000000000000
    ffffffff81539fb8
  [<ffffffff815af2c3>] x86_64_start_reservations+0xae
    ffffffff815a65a0
    ffffffff81001000
    ffffffff81539ff8
  [<ffffffff815b1762>] xen_start_kernel+0x41d
    809822011f898975
    000106a500100800
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000


-- 
Vasiliy Tolstov,
Clodo.ru
e-mail: v.tolstov@xxxxxxxxx
jabber: vase@xxxxxxxxx

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