*** Bug 1313887 has been marked as a duplicate of this bug. ***
Tested with win7-32 and win2008-64 guest and install qemu-ga-x86/x64.msi with qemu-ga-win-7.3.2-1, the result is pass when setting password with "crypted":false Host: kernel-2.6.32-667.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.496.el6.x86_64 Guest: virtio-win-1.8.0.iso qemu-ga-win-7.3.2-1(qemu-ga-x86.msi && qemu-ga-x64.msi ) 1. boot guest: /usr/libexec/qemu-kvm -S -name avocado-vt-vm1 -machine rhel6.6.0 -nodefaults -vga std -m 8G -smp 8 -drive file=/home/win7-32-virtio.qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=0 -drive id=drive_virtio,if=none,snapshot=off,aio=native,cache=none,media=cdrom,file=/usr/share/virtio-win2/virtio-win-1.8.0.iso -device ide-drive,id=virtio,drive=drive_virtio -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=00:52:0a:5c:f1:1d -vnc :1 -rtc base=localtime,clock=host,driftfix=slew -boot order=cd,menu=on -enable-kvm -monitor stdio -qmp tcp:0:1235,server,nowait -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtserialport,bus=virtio-serial0.0,chardev=qga0,name=org.qemu.guest_agent.0 2. install vioser driver and install qemu-ga-win msi in guest 3. change the Administrator password with "crypted":false # echo -n "123456" | base64 MTIzNDU2 # nc -U /tmp/qga.sock { "execute": "guest-info" } {"return": {"version": "0.12.1", "supported_commands": [{"enabled": true, "name": "guest-set-user-password"}, {"enabled": true, "name": "guest-set-vcpus"}, {"enabled": true, "name": "guest-get-vcpus"}, {"enabled": true, "name": "guest-network-get-interfaces"}, {"enabled": true, "name": "guest-suspend-hybrid"}, {"enabled": true, "name": "guest-suspend-ram"}, {"enabled": true, "name": "guest-suspend-disk"}, {"enabled": true, "name": "guest-fstrim"}, {"enabled": true, "name": "guest-fsfreeze-thaw"}, {"enabled": true, "name": "guest-fsfreeze-freeze"}, {"enabled": true, "name": "guest-fsfreeze-status"}, {"enabled": true, "name": "guest-file-flush"}, {"enabled": true, "name": "guest-file-seek"}, {"enabled": true, "name": "guest-file-write"}, {"enabled": true, "name": "guest-file-read"}, {"enabled": true, "name": "guest-file-close"}, {"enabled": true, "name": "guest-file-open"}, {"enabled": true, "name": "guest-shutdown"}, {"enabled": true, "name": "guest-info"}, {"enabled": true, "name": "guest-set-time"}, {"enabled": true, "name": "guest-get-time"}, {"enabled": true, "name": "guest-ping"}, {"enabled": true, "name": "guest-sync"}, {"enabled": true, "name": "guest-sync-delimited"}]}} {"execute":"guest-set-user-password","arguments":{"crypted":false,"username":"Administrator","password":"MTIzNDU2"}} {"return": {}} 4. Login guest with the new passowrd. login successfully. Set this bug to verified status.
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. https://rhn.redhat.com/errata/RHBA-2017-0561.html