OS hangs up while taking kdump for guest OS when hypervisor type is qemu and processor model is Haswell

Issue

• When hypervisor type is qemu and processor model is Haswell, kdump for guest OS always fails with the following messages:

[    0.438000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.438000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[    0.438000] ...trying to set up timer (IRQ0) through the 8259A ...
[    0.438000] ..... (found apic 0 pin 2) ...
[    0.438000] ....... failed.
[    0.438000] ...trying to set up timer as Virtual Wire IRQ...

• [Steps to reproduce]

1. Create virtual machine with hypervisor type kvm by using virt-manager on the host OS, and install RHEL7.3 to the VM.

2. Change hypervisor type to qemu and processor model to Haswell by using virsh edit command.

3. In guest OS, start kdump service.
   (crahskernel parameter should be properly set. /etc/kdump.conf and /etc/sysconfig/kdump is not need to be changed from default.)

4. Take a dump by using kdump in the guest OS, by executing following commands.

   # echo 1 > /proc/sys/kernel/sysrq
   # echo c > /proc/sysrq-trigger
   

• Note that if the hypervisor type is kvm or processor model is another one such as Conroe, this issue doesn't happen.