Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Each time after implement the "guest-get-vcpus" command, the guest agent is not available any more. The commands could not be executed successfully unless restart the qemu-ga service inside guest (or kill "qemu-ga" daemon and re-do "qemu-ga -d").
Version-Release number of selected component (if applicable):
Host:
kernel-2.6.32-429.el6.x86_64
qemu-kvm-0.12.1.2-2.415.el6.x86_64
Guest:
qemu-guest-agent-0.12.1.2-2.415.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Boot a guest with virtio-serial:
# /usr/libexec/qemu-kvm -M rhel6.5.0 -cpu SandyBridge -m 2G -smp 2,sockets=1,cores=2,threads=1,maxcpus=16 -enable-kvm -name win7-32 -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 -smbios type=1,manufacturer='Red Hat',product='RHEV Hypervisor',version=el6,serial=koTUXQrb,uuid=feebc8fd-f8b0-4e75-abc3-e63fcdb67170 -k en-us -rtc base=localtime,clock=host,driftfix=slew -nodefaults -monitor stdio -qmp tcp:0:6666,server,nowait -boot menu=on -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor unix:/tmp/monitor-unix,nowait,server -drive file=/home/RHEL6.5-64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:2e:28:1c,bus=pci.0,addr=0x4 -vga std -vnc :10 -usb -device usb-tablet -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0
2. Install qemu-guest-agent package inside guest and start qemu-ga service.
3. Execute some qemu-ga commands:
{"execute":"guest-ping"}
{"return": {}} ===> Succeed
3.
{"execute":"guest-get-vcpus"}
{"return": [{"online": true, "can-offline": false, "logical-id": 0}, {"online": true, "can-offline": true, "logical-id": 1}]}
======> Succeed here.
4. Repeat step 3 again:
{"execute":"guest-get-vcpus"}
======> No response.
5. {"execute":"guest-ping"} ===> No response
6. Restart qemu-ga service inside guest
{"execute":"guest-ping"}
{"return": {}}
======> Work again.
Actual results:
Each time after implement "guest-get-vcpus" guest agent command, the guest agent will not work any more unless restart the qemu-ga inside guest.
Expected results:
Guest agent should always work.
Additional info:
Comment 2RHEL Program Management
2013-11-11 00:45:18 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Component reported version version used for reproducing
------------ ------------------------- ----------------------------
host kernel 2.6.32-429.el6.x86_64 2.6.32-431.11.2.el6.x86_64
qemu-kvm 0.12.1.2-2.415.el6.x86_64 0.12.1.2-2.424.el6.x86_64
guest kernel ? 2.6.32-431.el6.x86_64
guest agent 0.12.1.2-2.415.el6.x86_64 0.12.1.2-2.423.el6.x86_64
I used a 2VCPU guest, and I passed the commands to qga with the
virsh qemu-agent-command --block DOMAIN QMP_COMMAND
virsh command.
If you can still reproduce the bug, please
- provide your guest kernel version
- provide your qga config from the guest (/etc/sysconfig/qemu-ga)
- before starting the guest agent, configure abrt (or normal coredumps),
and please capture a qemu-ga process coredump in the guest, while it is
apparently hung.
Thanks.
Hi, Laszlo
Unfortunately I could not reproduce the issue with exactly the same host and guest version with comment 0. I will update info here once I have a chance to reproduce it.
Thanks,
Qunfang
Description of problem: Each time after implement the "guest-get-vcpus" command, the guest agent is not available any more. The commands could not be executed successfully unless restart the qemu-ga service inside guest (or kill "qemu-ga" daemon and re-do "qemu-ga -d"). Version-Release number of selected component (if applicable): Host: kernel-2.6.32-429.el6.x86_64 qemu-kvm-0.12.1.2-2.415.el6.x86_64 Guest: qemu-guest-agent-0.12.1.2-2.415.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Boot a guest with virtio-serial: # /usr/libexec/qemu-kvm -M rhel6.5.0 -cpu SandyBridge -m 2G -smp 2,sockets=1,cores=2,threads=1,maxcpus=16 -enable-kvm -name win7-32 -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 -smbios type=1,manufacturer='Red Hat',product='RHEV Hypervisor',version=el6,serial=koTUXQrb,uuid=feebc8fd-f8b0-4e75-abc3-e63fcdb67170 -k en-us -rtc base=localtime,clock=host,driftfix=slew -nodefaults -monitor stdio -qmp tcp:0:6666,server,nowait -boot menu=on -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor unix:/tmp/monitor-unix,nowait,server -drive file=/home/RHEL6.5-64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:2e:28:1c,bus=pci.0,addr=0x4 -vga std -vnc :10 -usb -device usb-tablet -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 2. Install qemu-guest-agent package inside guest and start qemu-ga service. 3. Execute some qemu-ga commands: {"execute":"guest-ping"} {"return": {}} ===> Succeed 3. {"execute":"guest-get-vcpus"} {"return": [{"online": true, "can-offline": false, "logical-id": 0}, {"online": true, "can-offline": true, "logical-id": 1}]} ======> Succeed here. 4. Repeat step 3 again: {"execute":"guest-get-vcpus"} ======> No response. 5. {"execute":"guest-ping"} ===> No response 6. Restart qemu-ga service inside guest {"execute":"guest-ping"} {"return": {}} ======> Work again. Actual results: Each time after implement "guest-get-vcpus" guest agent command, the guest agent will not work any more unless restart the qemu-ga inside guest. Expected results: Guest agent should always work. Additional info: