From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2841731 ] Guest migration fail on PAE host
Date: Thu, 27 Aug 2009 01:21:56 +0000 [thread overview]
Message-ID: <E1MgTga-0007By-Rq@d55xhf1.ch3.sourceforge.com> (raw)
Bugs item #2841731, was opened at 2009-08-21 00:19
Message generated for change (Settings changed) made by jiajun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2841731&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qemu
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Jiajun Xu (jiajun)
Assigned to: Nobody/Anonymous (nobody)
Summary: Guest migration fail on PAE host
Initial Comment:
Environment:
------------
Host OS (ia32/ia32e/IA64):pae
Guest OS (ia32/ia32e/IA64):pae
Kernel Commit:84a3c0818fe9d7a1e34c188d6182793f213a6a66
Userspace Commit:5d01efd67f08855a311c866c8fff0b68b5fd0690
Host Kernel Version: 2.6.31-rc2
Bug detailed description:
--------------------------
On PAE host, guest migration will fail with host kernel call trace. There is no such issue on 64-bit host.
And the latest kvm tree also has the same issue:
kvm.git: 779cc54dbccaa3a00d70a9d61d090be5d9ccc903
qemu.git: 9e3269181e9bc56feb43bcd4e8ce0b82cd543e65
Host kernel call trace:
########
Pid: 12053, comm: qemu-system-x86 Tainted: G D (2.6.31-rc2 #1)
EIP: 0060:[<c043e023>] EFLAGS: 00210202 CPU: 0
EIP is at lock_hrtimer_base+0x11/0x33
EAX: f5d1541c EBX: 00000010 ECX: 000004a9 EDX: f5c1bc7c
ESI: f5d1541c EDI: f5c1bc7c EBP: f5c1bc74 ESP: f5c1bc68
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process qemu-system-x86 (pid: 12053, ti=f5c1b000 task=f61cb410
task.ti=f5c1b000)
Stack:
f5d1541c ffffffff 000004a9 f5c1bc8c c043e097 f9b7f7cb f5d1541c 00000000
<0> 000004a9 f5c1bc98 c043e0f0 f5d153d0 f5c1bcb0 f9b9b4df 00000000 bfd8a102
<0> f3c1e000 f5d15440 f5c1bcc0 f9b9b56d bfd8a10c f3c1e000 f5c1bda0 f9b8c26b
Call Trace:
[<c043e097>] ? hrtimer_try_to_cancel+0x16/0x62
[<f9b7f7cb>] ? kvm_flush_remote_tlbs+0xd/0x1a [kvm]
[<c043e0f0>] ? hrtimer_cancel+0xd/0x18
[<f9b9b4df>] ? pit_load_count+0x98/0x9e [kvm]
[<f9b9b56d>] ? kvm_pit_load_count+0x21/0x35 [kvm]
[<f9b8c26b>] ? kvm_arch_vm_ioctl+0x91e/0x9f5 [kvm]
[<f9b7f3b4>] ? kvm_set_memory_region+0x2f/0x37 [kvm]
[<f9b809c7>] ? kvm_vm_ioctl+0xafb/0xb45 [kvm]
[<c043ddf8>] ? enqueue_hrtimer+0x5d/0x68
[<c043e258>] ? __hrtimer_start_range_ns+0x15d/0x168
[<c043e272>] ? hrtimer_start+0xf/0x11
[<f9cd51cd>] ? vmx_vcpu_put+0x8/0xa [kvm_intel]
[<f9b83e8b>] ? kvm_arch_vcpu_put+0x16/0x19 [kvm]
[<f9b8b943>] ? kvm_arch_vcpu_ioctl+0x7d5/0x7df [kvm]
[<c041f1e5>] ? kmap_atomic+0x14/0x16
[<c046ec2f>] ? get_page_from_freelist+0x27c/0x2d2
[<c046ed72>] ? __alloc_pages_nodemask+0xd7/0x402
[<c04714a6>] ? lru_cache_add_lru+0x22/0x24
[<f9b7f6b5>] ? kvm_dev_ioctl+0x22d/0x250 [kvm]
[<f9b7fecc>] ? kvm_vm_ioctl+0x0/0xb45 [kvm]
[<c049a9ab>] ? vfs_ioctl+0x22/0x67
[<c049af1d>] ? do_vfs_ioctl+0x46c/0x4b7
[<c05fb0fb>] ? sys_recv+0x18/0x1a
[<c0446bef>] ? sys_futex+0xed/0x103
[<c049afa8>] ? sys_ioctl+0x40/0x5a
[<c04028a4>] ? sysenter_do_call+0x12/0x22
Code: c0 ff 45 e4 83 45 dc 24 83 7d e4 02 0f 85 cf fe ff ff 8d 65 f4 5b 5e 5f
5d c3 55 89 e5 57 89 d7 56 89 c6 53 8b 5e 20 85 db 74 17 <8b> 03 e8 0e dd 23 00
89 07 3b 5e 20 74 0d 89 c2 8b 03 e8 8a dd
EIP: [<c043e023>] lock_hrtimer_base+0x11/0x33 SS:ESP 0068:f5c1bc68
CR2: 0000000000000010
---[ end trace f747f57e7d1b76c8 ]---
########
Reproduce steps:
----------------
(1)qemu-img create -b /share/xvs/img/app/ia32p_SMP.img -f qcow2 /share/xvs/var/tmp-img_CPL_LM_40_1228273473_1
(2)qemu -m 256 -net nic,macaddr=00:16:3e:39:78:1c,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/xvs/var/tmp-img_CPL_LM_40_1228273473_1 -incoming tcp:localhost:4444
(3) Press "Ctrl+Alt+2" to switch to qemu monitor
(4) Run "migrate tcp:localhost:4444"
----------------------------------------------------------------------
>Comment By: Jiajun Xu (jiajun)
Date: 2009-08-26 18:21
Message:
The bug is fixed by kvm.git: b4eba884776b5ab77fef1febbd3203e54a66d0bd.
Verified with kvm commit: 323d3b06db8bf2d8e4c5ed1a390668ae7b1b84bf and
qemu commit: f3600c589a9ee5ea4c0fec74ed4e06a15b461d52, the bug is fixed.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2841731&group_id=180599
next reply other threads:[~2009-08-27 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 1:21 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-21 7:19 [ kvm-Bugs-2841731 ] Guest migration fail on PAE host SourceForge.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1MgTga-0007By-Rq@d55xhf1.ch3.sourceforge.com \
--to=noreply@sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.