On 01.10.2015 14:25, Paolo Bonzini wrote:
Hi Paolo,
> Applied. Do you also know what caused the warning, and/or would you
like me to take a look?
The trace we're getting is this:
[<ffffffff8100471d>] dump_trace+0x7d/0x2d0
[<ffffffff81004a04>] show_stack_log_lvl+0x94/0x170
[<ffffffff81005cc1>] show_stack+0x21/0x50
[<ffffffff81510f42>] dump_stack+0x41/0x51
[<ffffffff81055362>] warn_slowpath_common+0x82/0xc0
[<ffffffffa0388cc1>] skip_emulated_instruction+0xe1/0x160 [kvm_amd]
[<ffffffffa038908b>] io_interception+0x3b/0x80 [kvm_amd]
[<ffffffffa031667c>] vcpu_enter_guest+0x6bc/0xc70 [kvm]
[<ffffffffa031aa08>] kvm_arch_vcpu_ioctl_run+0x1d8/0x450 [kvm]
[<ffffffffa0305ec1>] kvm_vcpu_ioctl+0x2e1/0x580 [kvm]
[<ffffffff811b3f24>] do_vfs_ioctl+0x2d4/0x4b0
[<ffffffff811b4188>] SyS_ioctl+0x88/0xa0
[<ffffffff8151f209>] system_call_fastpath+0x16/0x1b
[<00007f8f7b5fabe7>] 0x7f8f7b5fabe6
The colleague who was investigating this is not here today, but from
what I remember it seems to only happen when nested virtualisation is
being used. I don't know more about it right now, bisecting pointed out
f104765b4f81fd74d69e0eb161e89096deade2db . Since it was logging so
rapidly on our autotester machines (which are running 200-250 VMs
nested) that we are continuously run out of disk space I just tried to
come up with a stop-gap fix until this has been properly analyzed.
Thanks,
Dirk
--
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
