Bug 616389
Summary: | balloon: qemu become no response for query balloon after stop guest with balloon service start | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Shirley Zhou <szhou> | ||||
Component: | qemu-kvm | Assignee: | Amit Shah <amit.shah> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.0 | CC: | llim, mkenneth, mshao, tburke, virt-maint, ykaul | ||||
Target Milestone: | beta | Keywords: | RHELNAK | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-02-02 12:59:55 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: | 580954 | ||||||
Attachments: |
|
Description
Shirley Zhou
2010-07-20 10:45:16 UTC
Created attachment 433125 [details]
virt manager screenshot
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** When the balloon service is run in the guest it can provide more info. Why is that a bug? (In reply to comment #4) > When the balloon service is run in the guest it can provide more info. > Why is that a bug? If we stop balloon service in guest, then stop guest from monitor, then check balloon info, balloon info shows. While if balloon service start, then stop guest from monitor,then check balloon info, monitor become no response. additional info for query balloon info when guest status is paused. 02:00:31.465: debug : qemuMonitorJSONCommandWithFd:217 : Send command '{"execute":"stop"}' for write with FD -1 02:00:31.466: debug : qemuMonitorJSONIOProcessLine:115 : Line [{"timestamp": {"seconds": 1281938431, "microseconds": 466241}, "event": "STOP"}] 02:00:31.466: debug : qemuMonitorJSONIOProcessEvent:86 : mon=0x7f9a5c009660 obj=0x7f9a74142610 02:00:31.466: debug : qemuMonitorJSONIOProcessEvent:99 : handle STOP handler=0x478480 data=(nil) 02:00:31.466: debug : qemuMonitorJSONIOProcessLine:115 : Line [{"return": {}}] 02:00:31.466: debug : qemuMonitorJSONIOProcess:188 : Total used 97 bytes out of 97 available in buffer 02:00:31.466: debug : qemuMonitorJSONCommandWithFd:222 : Receive command reply ret=0 errno=0 14 bytes '{"return": {}}' 02:00:31.467: debug : qemudGetProcessInfo:4600 : Got status for 5809/0 user=1487 sys=1231 cpu=3 02:00:31.467: debug : qemuMonitorJSONCommandWithFd:217 : Send command '{"execute":"query-balloon"}' for write with FD -1 02:00:32.337: debug : qemudGetProcessInfo:4600 : Got status for 5809/0 user=1488 sys=1235 cpu=2 02:00:33.331: debug : qemudGetProcessInfo:4600 : Got status for 5809/0 user=1489 sys=1240 cpu=2 02:00:34.335: debug : qemudGetProcessInfo:4600 : Got status for 5809/0 user=1491 sys=1245 cpu=3 02:00:35.337: debug : qemudGetProcessInfo:4600 : Got status for 5809/0 user=1493 sys=1249 cpu=3 02:00:36.337: debug : qemudGetProcessInfo:4600 : Got status for 5809/0 user=1494 sys=1256 cpu=3 02:00:37.338: debug : qemudGetProcessInfo:4600 : Got status for 5809/0 user=1494 sys=1262 cpu=3 02:00:38.338: debug : qemudGetProcessInfo:4600 : Got status for 5809/0 user=1495 sys=1268 cpu=3 02:00:39.339: debug : qemudGetProcessInfo:4600 : Got status for 5809/0 user=1496 sys=1274 cpu=3 At this time, I send resume command from virsh, error happens: virsh # resume rhel6-test-clone error: Failed to resume domain rhel6-test-clone error: Timed out during operation: cannot acquire state change lock It's a qemu issue, the guest is not running, qemu should provide the last number of sore error code Looks like a duplicate of bug 626544 and bug 623903. Can you try again and let us know? Marking this as a duplicate of bug 623903. This one was discovered before the previous two bugs, but the fix went in one of the other. If it's not a dup, please re-open. *** This bug has been marked as a duplicate of bug 623903 *** |