Bug 1218937
Summary: | QEMU Guest Agent VSS Provider is not started after guest tools install | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Ondra Machacek <omachace> | ||||
Component: | virtio-win | Assignee: | Yvugenfi <yvugenfi> | ||||
virtio-win sub component: | qemu-ga-win | QA Contact: | Pavel Stehlik <pstehlik> | ||||
Status: | CLOSED NOTABUG | Docs Contact: | |||||
Severity: | unspecified | ||||||
Priority: | unspecified | CC: | ailan, bazulay, gklein, juzhang, lijin, lsurette, lveyde, omachace, pmatyas, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, srevivo, weliao, wyu, xiagao, ykaul, yvugenfi | ||||
Version: | 7.1 | ||||||
Target Milestone: | pre-dev-freeze | ||||||
Target Release: | 7.3 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Cause:
Wrong behaviour during package re-install
Consequence:
VSS server was removed and not restarted
Fix:
Change upgrade\re-install behaviour of the installer
Result:
VSS server works after re-install
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-03-23 09:32:23 UTC | Type: | Bug | ||||
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: | 1261822, 1288337, 1401400 | ||||||
Attachments: |
|
Description
Ondra Machacek
2015-05-06 08:44:16 UTC
Lev, is this a WGT install issue? Or a sub-component issue? (In reply to Sandro Bonazzola from comment #1) > Lev, is this a WGT install issue? Or a sub-component issue? If any, it's an issue of Qemu GA installer, however we need to verify that the issue is real first. I re-assigned the bug to Yossi Hindin. Hi Ondra, Do you see the VSS provider service at all or the service exists and is in stopped state? Can you please post screenshot of service manager? Best regards, Yan. Hi, Can you also please describes steps to reproduce the issue. Best regards, Yan. Created attachment 1024958 [details]
services screenshot
Hi Yan,
I've attached sreenshot of services. Please note that this state is after installation without windows restart, service has setup to be started automatically so after restart - it's started.
The steps are in the description. I've just installed all applications with Rhev-tools installer and didn't restart windows.
(In reply to Ondra Machacek from comment #5) > Created attachment 1024958 [details] > services screenshot > > Hi Yan, > > I've attached sreenshot of services. Please note that this state is after > installation without windows restart, service has setup to be started > automatically so after restart - it's started. > > The steps are in the description. I've just installed all applications with > Rhev-tools installer and didn't restart windows. Hi Ondra, My question is: is this a clean installation, or is it an update from any previous version of RHEV Tools? I couldn't reproduce this with clean installation, but I had reproduced it with an update from a previous version of RHEV Tools (I used 3.5-1 as the base version with an update to 3.5-9). The actual reason it happens with an update is due to a known issue, that Qemu-GA doesn't handles well a repair - a situation when the same version is installed over itself. It's clean installation. How to test: 1. Install qemu-ga-win 2. Check that {"execute":"guest-ping"} works 3. Check that {"execute":"guest-fsfreeze-status"} works 4. Run same installer again 5. Check that {"execute":"guest-ping"} works 6. Check that {"execute":"guest-fsfreeze-status"} works The build with fix: https://brewweb.devel.redhat.com/buildinfo?buildID=452407 Please help to verify this bug. Host: 3.10.0-324.el7.x86_64 qemu-kvm-rhev-2.3.0-30.el7.x86_64 Tree: url --url="http://download.englab.nay.redhat.com/pub/rhel/nightly/RHEL-7.2-20151012.n.0/compose/Server/x86_64/os" Guest: win2012-64 qemu-ga-x64.msi http://download.devel.redhat.com/brewroot/packages/qemu-ga-win/7.2.1/1/win/qga/installer/x64/qemu-ga-x64.msi Install qemu-ga-win-7.2.1-1 (clean installation);the QEMU Guest Agent VSS Provider server stop like Attachments, manual start this service, re-install qemu-ga, this service stop. Guest: win2008-32 qemu-ga-x86.msi http://download.devel.redhat.com/brewroot/packages/qemu-ga-win/7.2.1/1/win/qga/installer/x86/qemu-ga-x86.msi Install qemu-ga-win-7.2.1-1 (clean installation);the QEMU Guest Agent VSS Provider server stop like Attachments, manual start this service, re-install qemu-ga, this service stop. How to test: 1. Install qemu-ga-win 2. Check that {"execute":"guest-ping"} works 3. Check that {"execute":"guest-fsfreeze-status"} works 4. Run same installer again 5. Check that {"execute":"guest-ping"} works 6. Check that {"execute":"guest-fsfreeze-status"} works --this result is ok {"execute":"guest-ping"} {"return": {}} {"execute":"guest-fsfreeze-status"} {"return": "thawed"} cmd: /usr/libexec/qemu-kvm -name rhel7.2 \ -M pc-i440fx-rhel7.2.0,accel=kvm,usb=off,vmport=off \ -cpu SandyBridge -m 4096 -realtime mlock=off -smp 4 \ -drive file=/home/win2008-32-virtio.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0 \ -boot menu=on \ -netdev tap,id=hostnet0,vhost=on,script=/etc/ovs-ifup,downscript=/etc/ovs-ifdown \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:55:66:77:88:99,bus=pci.0,addr=0x3 \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 \ -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 \ -device virtserialport,bus=virtio-serial0.0,chardev=qga0,name=org.qemu.guest_agent.0 \ -spice port=6600,disable-ticketing, \ -monitor stdio \ -qmp tcp:0:4444,server,nowait so I think this bug didn't fix But what about the command? {"execute":"guest-fsfreeze-status"} The main problem was the the service was removed and not reinstalled at all. In this case the service should be started on first use. Best regards, Yan. Hi Yan: (In reply to Yan Vugenfirer from comment #15) > But what about the command? {"execute":"guest-fsfreeze-status"} > > The main problem was the the service was removed and not reinstalled at all. > > In this case the service should be started on first use. > > > Best regards, > Yan. {"execute":"guest-fsfreeze-status"}---this comment 9 tell tested, if this service stop, the command can work well, so this service has relation with the command?{"execute":"guest-fsfreeze-status"} Install qemu-ga-win-7.2.1-1 (clean installation), the service didn't started on first use,must manual start or reboot system, this service can start. so I don't know where is this bug fixed point. Hi Yan, As the erratum deadline is approaching,could you reply comment#16? If this bug is not fixed,we need to remove it from the rhel7.2 errata. The main issue was that with VSS service none of the guest_fsfreeze* commands would work. If they work (the services is sorted after initial usage) - then the problem is solved. Hi Yan, I retest on win2008R2_64, qemu-ga-win-7.0-9 and qemu-ga-win-7.2.1-1 Install qemu-ga-win, the VSS service did't started. and the guest_fsfreeze* commands can work well. after exec commands, this service still stop status. so qemu-ga-win-7.0.9 and qemu-ga-win-7.2.1.1 has the same result. which this problem fixed point or I can't reproduce this problem? please correct me if I made wrong. Thanks Let's reject it, until I will investigate the BZ. re-assign this bug according to comment#19 and comment#20. Reproduced this bug in qemu-ga-win-7.4.2-1 according to comment 0. pkg: qemu-ga-win-7.4.2-1 virtio-win-1.9.0-3.el7 kernel-3.10.0-606.el7.x86_64 qemu-kvm-rhev-2.8.0-5.el7.x86_64 Steps: 1. install win2012r2 guest. 2. after installation, install serial driver 3. install qemu-ga-x64.msi 4. check service manager 5. run qemu-ga cmd in host 6. check service manager results: after step 4, QEMU Guest Agent VSS Provider is not started. (attachment) after step 5, # nc -U /tmp/qga.sock {"execute":"guest-ping"} {"return": {}} {"execute":"guest-fsfreeze-status"} {"return": "thawed"} {"execute":"guest-fsfreeze-freeze"} {"return": 2} after step 6,QEMU Guest Agent VSS Provider is started after exec {"execute":"guest-fsfreeze-freeze"} . So, QEMU Guest Agent VSS Provider is still not started after qemu-ga installation. Reassign this bug. In any case the behaviour of the VSS server is changing. There is no real need to start the VSS server after installation. Agent will start it only during freeze command. I will update the expected behaviour after the commits are submitted. Closing base on comment #25 |