On 07/14/2011 01:40 PM, Jan Beulich wrote:
>>> Danilo Godec <[email protected]> 07/14/11 12:34 PM >>>
>No errors are logged in /var/log/xen/* and live migration works for
>Centos DomU's, which suggests that the problem is in the DomU
>(kernel)... Unfortunately I have no idea how to 'catch' what's going on
>there.
Using the xenctx utility (in Dom0) you should be able to see where
the guests are spinning (which is what I assume they are doing).
This is what xenctx shows after unsuccessful migration:
rip: ffffffff800083aa
flags: 00001246 i z p
rsp: ffff88001faa9470
rax: 0000000000000000 rcx: ffffffff800083aa rdx: 0000000000000008
rbx: 0000000000000125 rsi: ffff88001faa9488 rdi: 0000000000000003
rbp: ffff88001faa94d8 r8: 0000000000000000 r9: ffff88001faa9c58
r10: 0000000000000001 r11: 0000000000000246 r12: 0000000000009d20
r13: ffffc90000000000 r14: 0000000000000004 r15: 0000000000000000
cs: e033 ss: e02b ds: 0000 es: 0000
fs: 0000 @ 00007f8cbad5b6f0
gs: 0000 @ ffffc90000000000/0000000000000000
Code (instr addr ffffffff800083aa)
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:
0000000000000001 0000000000000000 ffffffff802feb51 ffff88001faa94ac
0000000000000001 0000000000000000 ffffffff802fedca 0000000800000000
00000000cf4d63b1 0000000000000000 ffffffff80803490 0000000000000125
0000000000000001 ffff88001faa9538 ffffffff803042e4 0000000000000000
Call Trace:
[<ffffffff800083aa>] <--
[<ffffffff802feb51>]
[<ffffffff802fedca>]
[<ffffffff80803490>]
[<ffffffff803042e4>]
[<ffffffff80803490>]
[<ffffffff80803490>]
[<ffffffff805a8348>]
[<ffffffff80470a00>]
[<ffffffff80050567>]
[<ffffffff805a1f70>]
[<ffffffff8000f8eb>]
[<ffffffff8046cb88>]
[<ffffffff8000f8eb>]
[<ffffffff8004f5af>]
[<ffffffff8004f662>]
[<ffffffff8000f8eb>]
[<ffffffff8000fde9>]
[<ffffffff80077316>]
[<ffffffff80843501>]
[<ffffffff800774ce>]
[<ffffffff80245560>]
[<ffffffff808435c3>]
[<ffffffff8005071b>]
[<ffffffff805a1f70>]
[<ffffffff8000f8eb>]
[<ffffffff8046cb88>]
[<ffffffff8000f8eb>]
[<ffffffff8004f5af>]
[<ffffffff8004f662>]
[<ffffffff8000f8eb>]
[<ffffffff8000fde9>]
[<ffffffff80077316>]
[<ffffffff80843501>]
[<ffffffff800774ce>]
[<ffffffff80245560>]
[<ffffffff808435c3>]
[<ffffffff8005071b>]
[<ffffffff80302ba8>]
[<ffffffff8060eed8>]
[<ffffffff8046cb88>]
[<ffffffff80239e7d>]
[<ffffffff80302ba8>]
[<ffffffff805a5a56>]
[<ffffffff80011487>]
[<ffffffff804711a4>]
[<ffffffff80473948>]
[<ffffffff805a5a56>]
[<ffffffff80785380>]
[<ffffffff8000e2a2>]
[<ffffffff80302ba8>]
[<ffffffff800f4fbe>]
[<ffffffff80745820>]
[<ffffffff80003c90>]
[<ffffffff80300940>]
[<ffffffff80749fc0>]
[<ffffffff80745820>]
[<ffffffff8000d175>]
[<ffffffff80785380>]
[<ffffffff80785380>]
[<ffffffffffffffea>]
[<ffffffffffffffff>]
[<ffffffff80302ba8>]
[<ffffffff8086b7c0>]
[<ffffffff8009ec10>]
[<ffffffff8009ecc1>]
[<ffffffff80069443>]
[<ffffffff800696a4>]
[<ffffffff800701d0>]
[<ffffffff800695f0>]
[<ffffffff8006fb16>]
[<ffffffff8000d3ea>]
[<ffffffff80745090>]
[<ffffffff8006fa60>]
[<ffffffff8000d3e0>]
The last part - call trace - is considerably longer then for a normally
running DomU.
Hopefully someone will make some sense out of that, cause I sure can't.
That seems indeed necessary in this case (albeit I would have thought
this gets taken care of automatically): You may need to make sure that
the Xen blkfront driver loads before the ATA one that was servicing your
disk before installing the KMP.
It seems that HVM emulates a 'PIIX3 IDE' controller and the driver seems
to be built-in (i.e. not a kernel module):
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE
[Natoma/Triton II]
This is a part of 'dmesg':
[ 0.409416] vesafb: framebuffer at 0xf0000000, mapped to
0xffffc90001080000, using 3072k, total 4096k
[ 0.409421] vesafb: mode is 1024x768x16, linelength=2048, pages=1
[ 0.409425] vesafb: scrolling: redraw
[ 0.409428] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
[ 0.430756] Console: switching to colour frame buffer device 128x48
[ 0.451763] fb0: VESA VGA frame buffer device
[ 0.451968] ERST: Table is not found!
[ 0.452222] Non-volatile memory driver v1.3
[ 0.452392] Linux agpgart interface v0.103
[ 0.452576] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[ 0.498586] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.556005] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.559929] ata_piix 0000:00:01.1: version 2.13
[ 0.560341] ata_piix 0000:00:01.1: setting latency timer to 64
[ 0.561067] scsi0 : ata_piix
[ 0.561255] scsi1 : ata_piix
[ 0.561443] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc200 irq 14
[ 0.561766] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc208 irq 15
Things go south when 'xen-platform-pci' or 'xen-vbd' module is loaded...
Is there a way to disable a built-in driver??
Danilo
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
