Bug 732949
| Summary: | Guest screen becomes abnormal after migration with spice | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Qunfang Zhang <qzhang> | ||||
| Component: | qemu-kvm | Assignee: | Yonit Halperin <yhalperi> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.2 | CC: | bcao, dblechte, juzhang, michen, mkenneth, virt-maint, yhalperi | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | qemu-kvm-0.12.1.2-2.189.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-06 15:56:30 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 743047 | ||||||
| Attachments: |
|
||||||
|
Description
Qunfang Zhang
2011-08-24 09:22:39 UTC
Meet another phenomenon with the same steps in bug description but using a different hardware. Migrate guest during guest running 2Dtom, after finish migration the 2Dtom screen is quiescent instead of dynamic. Guest keyboard and mouse got unavailable. Sometimes I just implement migration while guest is not run any application can also reproduce this. Guest got no interactive after migration. I borrow the hosts from another guy. If need to login the host to have a look, I may ask the guy if the hosts are available. The host hardware for this specific phenomenon: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz stepping : 7 cpu MHz : 3093.206 cache size : 6144 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 4 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 6185.15 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: For the slowness scenario: After some user operations in the guest (e.g., pressing escape, alt-tab), the guest returns to its usual speed. qemu cpu usage, when the guest is slow, is about 30% from the cpu usage when it turns responsive.
Found the problem (at least for the slowness scenario):
src qemu
1) qxl driver waits for interrupt (specifically for QXL_INTERRUPT_DISPLAY)
2) red worker thread calls qxl_send_events with QXL_INTERRUPT_DISPLAY
3) interrupt request is pushed to a pipe
4) Migration occurs before io thread read the pipe and call qxl_set_irq
target qemu
1) qxl driver still waits for the interrupt (which was not sent)
2) when red_worker thread calls qxl_send_events with QXL_INTERRUPT_DISPLAY
it is ignored since qxl->ram->int_pending was set to 1 for
QXL_INTERRUPT_DISPLAY (in qxl_send_events that was called in src_qemu)
==> the driver is starved.
Created attachment 521813 [details]
proposed fix
Reproduced with qemu-kvm-0.12.1.2-2.188.el6 with the same command line and steps as bug description. Can reproduce at the first time migration. Guest screen stops but not dynamically running the 2Dtom. Verified on qemu-kvm-0.12.1.2-2.189.el6, can not reproduce this issue after 20 times migration. So, I will set the status to VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2011-1531.html |