Tried to migrate RHEL 5.3 guest to remote machine. It fails to migrate with
the
below soft lockup message on guest.
I haven't faced this issue, with qemu-kvm-10.1. Remote migration fails with
qemu-kvm-0.10.4.
=================
BUG: soft lockup - CPU#0 stuck for 10s! [init:1]
Pid: 1, comm: init
EIP: 0060:[<c044d1e9>] CPU: 0
EIP is at handle_IRQ_event+0x39/0x8c
EFLAGS: 00000246 Not tainted (2.6.18-125.el5 #1)
EAX: 0000000c EBX: c06e7480 ECX: c79a8da0 EDX: c0734fb4
ESI: c79a8da0 EDI: 0000000c EBP: 00000000 DS: 007b ES: 007b
CR0: 8005003b CR2: 08198f00 CR3: 079c7000 CR4: 000006d0
[<c044d2c0>] __do_IRQ+0x84/0xd6
[<c044d23c>] __do_IRQ+0x0/0xd6
[<c04074ce>] do_IRQ+0x99/0xc3
[<c0405946>] common_interrupt+0x1a/0x20
[<c0428b6f>] __do_softirq+0x57/0x114
[<c04073eb>] do_softirq+0x52/0x9c
[<c04059d7>] apic_timer_interrupt+0x1f/0x24
[<c053a6ae>] add_softcursor+0x13/0xa2
[<c053ab36>] set_cursor+0x3a/0x5c
[<c053ab9e>] con_flush_chars+0x27/0x2f
[<c0533a31>] write_chan+0x1c5/0x298
[<c041e3d7>] default_wake_function+0x0/0xc
[<c05315ea>] tty_write+0x147/0x1d8
[<c053386c>] write_chan+0x0/0x298
[<c0531ffd>] redirected_tty_write+0x1c/0x6c
[<c0531fe1>] redirected_tty_write+0x0/0x6c
[<c0472cff>] vfs_write+0xa1/0x143
[<c04732f1>] sys_write+0x3c/0x63
[<c0404f17>] syscall_call+0x7/0xb
=======================
Source machine:
Machine: x3850
Kernel: 2.6.30-rc6-git4
qemu-kvm-0.10.4
Destination machine:
Machine: LS21
Kernel: 2.6.30-rc6-git3
qemu-kvm-0.10.4
Steps to Reproduce:
1. Install RHEL 5.3 guest on x3850 with above mentioned kernel on qemu
version
2. NFS mount the dir containing the guest image on Destination(LS21)
3. Boot the rhel guest
4. Wait for guest migration on LS21 by following command
qemu-system-x86_64 -boot c rhel5.3.raw -incoming tcp:0:4444
5. Start the migration on source(x3850)
a. On guest press Alt+Ctl+2 to switch to qemu prompt
b. Run "migrate -d tcp:'Destination IP':4444"
6. Above command hang the guest for around 3 or 4 min and give the call
trace
on dmesg showing the soft lockup on guest.
Few other details:
Tried to migrate from ls21 to another ls21 and faced the same failure.
I haven't faced this issue, when i was using qemu-10.1
Migration of RHEL 5.3 guest from ls21 to another ls21 succeeded with
qemu-10.1
Regards
Pradeep
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
