migrating failed with rcu_preempt message on proxmox 8

ppyy

Member
Oct 16, 2021
9
0
6
53
https://gitlab.com/qemu-project/qemu/-/issues/2006

Host environment​


  • Operating system: Proxmox 8.1(Debian 12.2)
  • OS/kernel version: Linux pve0.wx.xxxx.com 6.5.11-4-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-4 (2023-11-20T10:19Z) x86_64 GNU/Linux
  • Architecture: x86_64
  • QEMU flavor: pve-qemu-kvm
  • QEMU version: 8.1.2-4
  • QEMU command line:
  • hardware: Dell R630, Xeon CPU E5-2686, H330 Raid

when i migrate the VM from one host to another, it fails and give messages:


[ 584.109502] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 584.109534] rcu: 1-...!: (0 ticks this GP) idle=1408/0/0x0 softirq=8428/8428 fqs=0 (false positive?)
[ 584.109556] (detected by 0, t=5252 jiffies, g=2953, q=74 ncpus=2)
[ 584.109561] Sending NMI from CPU 0 to CPUs 1:
[ 584.109587] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xb/0x10
[ 584.110564] rcu: rcu_preempt kthread timer wakeup didn't happen for 5251 jiffies! g2953 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
[ 584.110585] rcu: Possible timer handling issue on cpu=1 timer-softirq=8006
[ 584.110597] rcu: rcu_preempt kthread starved for 5252 jiffies! g2953 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[ 584.110614] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
[ 584.110645] rcu: RCU grace-period kthread stack dump:
[ 584.110658] task:rcu_preempt state:I stack:0 pid:15 ppid:2 flags:0x00004000
[ 584.110667] Call Trace:
[ 584.110672] <TASK>
[ 584.110688] __schedule+0x351/0xa20
[ 584.110699] ? rcu_gp_cleanup+0x480/0x480
[ 584.110704] schedule+0x5d/0xe0
[ 584.110705] schedule_timeout+0x94/0x150
[ 584.110709] ? __bpf_trace_tick_stop+0x10/0x10
[ 584.110714] rcu_gp_fqs_loop+0x141/0x4c0
[ 584.110717] rcu_gp_kthread+0xd0/0x190
[ 584.110720] kthread+0xe9/0x110
[ 584.110725] ? kthread_complete_and_exit+0x20/0x20
[ 584.110728] ret_from_fork+0x22/0x30
[ 584.110735] </TASK>
[ 584.110736] rcu: Stack dump where RCU GP kthread last ran:
[ 584.110747] Sending NMI from CPU 0 to CPUs 1:
[ 584.110757] NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xb/0x10
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!