Hide Forgot
Description of problem: with rhev-agent64 installed in win2012R2 guest,host cannot receive any data from guest. Version-Release number of selected component (if applicable): rhev-guest-tools-iso-3.2-17 qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64 kernel-2.6.32-433.el6.x86_64 seabios-0.6.1.2-28.el6.x86_64 virtio-win-prewhql-74 How reproducible: 100% Steps to Reproduce: 1.boot win2012R2 guest with: /usr/libexec/qemu-kvm -drive file=win2k12R2.qcow2,if=none,cache=none,media=disk,format=qcow2,id=drive-ide0-0-1 -device ide-drive,id=ide0-0-1,drive=drive-ide0-0-1,bootindex=0 -usb -device usb-tablet -spice disable-ticketing,port=5901 -vga qxl -global qxl-vga.revision=3 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -netdev tap,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:7f:f9:F6,bus=pci.0 -chardev file,path=/root/console.log,id=serial1 -device isa-serial,chardev=serial1,id=s1 -cpu Penryn -M rhel6.5.0 -monitor stdio -name win2012R2-balloon-74 -smp 4,maxcpus=4,cores=2,threads=2,sockets=1 -m 4G -enable-kvm -cdrom /usr/share/rhev-guest-tools-iso/rhev-tools-setup.iso -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,path=/tmp/tt0,server,nowait,id=chardev0 -device virtserialport,chardev=chardev0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0 2.install RHEV-agent64.msi (64bit) 3.open services.msc to check whether RHEV-agents service is running click start --->type "services.msc" 4.check the cpu usage in task manager press ctrl+alt+del to open task manager 5.on the host ,open the listenning port #nc -U /tmp/tt0 Actual results: After step5,and do some randome operation,no data transferred from guest to host. When uninstall the rhev-agent,one message display: { "__name__" : "uninstalled" } Expected results: host can receive some data ,like {"__name__": "os-version", "version": "Win xx"} Additional info: retest with rhev-guest-tools-iso-3.3-6,it works fine.
Two questions: 1. Is the rhev-agent is running? Because in the actual results part you wrote that you do see a message passed through the virtio-serial. 2. What happen if you do step #5 (connect to the listening port) *before* you install the guest tools. Thanks.
(In reply to Gal Hammer from comment #1) > Two questions: > > 1. Is the rhev-agent is running? Because in the actual results part you > wrote that you do see a message passed through the virtio-serial. > > 2. What happen if you do step #5 (connect to the listening port) *before* > you install the guest tools. > > Thanks. Actually the uninstalled message is sent during uninstallation of the RHEV-Agent, and afaik that's done by the installer. So therefore I am a bit confused about seing the message at all. Just to be sure please attach the rhev-agent logs
(In reply to Vinzenz Feenstra [evilissimo] from comment #2) > (In reply to Gal Hammer from comment #1) > > Two questions: > > > > 1. Is the rhev-agent is running? Because in the actual results part you > > wrote that you do see a message passed through the virtio-serial. > > > > 2. What happen if you do step #5 (connect to the listening port) *before* > > you install the guest tools. > > > > Thanks. > > Actually the uninstalled message is sent during uninstallation of the > RHEV-Agent, and afaik that's done by the installer. So therefore I am a bit > confused about seing the message at all. I know that the message is send from the uninstaller program (guess who put it there :-#). The thing is that if the message was send, it means that the driver is working. > Just to be sure please attach the rhev-agent logs
(In reply to Gal Hammer from comment #1) > Two questions: > > 1. Is the rhev-agent is running? Because in the actual results part you > wrote that you do see a message passed through the virtio-serial. Yes,the rhev-agent service is running > 2. What happen if you do step #5 (connect to the listening port) *before* > you install the guest tools. Connect to the listening port before installing rhev-agent,it's the same result. > Thanks.
Created attachment 832948 [details] rhev files under "C:\Program Files (x86)\Redhat\RHEV"
(In reply to Vinzenz Feenstra [evilissimo] from comment #2) > (In reply to Gal Hammer from comment #1) > > Two questions: > > > > 1. Is the rhev-agent is running? Because in the actual results part you > > wrote that you do see a message passed through the virtio-serial. > > > > 2. What happen if you do step #5 (connect to the listening port) *before* > > you install the guest tools. > > > > Thanks. > > Actually the uninstalled message is sent during uninstallation of the > RHEV-Agent, and afaik that's done by the installer. So therefore I am a bit > confused about seing the message at all. > > Just to be sure please attach the rhev-agent logs I have uploaded the rhev files in guest under "C:\Program Files (x86)\Redhat\RHEV",hope that is what you want,anything else please let me know.
(In reply to lijin from comment #6) > (In reply to Vinzenz Feenstra [evilissimo] from comment #2) > > (In reply to Gal Hammer from comment #1) > > > Two questions: > > > > > > 1. Is the rhev-agent is running? Because in the actual results part you > > > wrote that you do see a message passed through the virtio-serial. > > > > > > 2. What happen if you do step #5 (connect to the listening port) *before* > > > you install the guest tools. > > > > > > Thanks. > > > > Actually the uninstalled message is sent during uninstallation of the > > RHEV-Agent, and afaik that's done by the installer. So therefore I am a bit > > confused about seing the message at all. > > > > Just to be sure please attach the rhev-agent logs > > I have uploaded the rhev files in guest under "C:\Program Files > (x86)\Redhat\RHEV",hope that is what you want,anything else please let me > know. Could you please provide also the vdsm logs for the moment when this is not working.
(In reply to Vinzenz Feenstra [evilissimo] from comment #7) > (In reply to lijin from comment #6) > > (In reply to Vinzenz Feenstra [evilissimo] from comment #2) > > > (In reply to Gal Hammer from comment #1) > > > > Two questions: > > > > > > > > 1. Is the rhev-agent is running? Because in the actual results part you > > > > wrote that you do see a message passed through the virtio-serial. > > > > > > > > 2. What happen if you do step #5 (connect to the listening port) *before* > > > > you install the guest tools. > > > > > > > > Thanks. > > > > > > Actually the uninstalled message is sent during uninstallation of the > > > RHEV-Agent, and afaik that's done by the installer. So therefore I am a bit > > > confused about seing the message at all. > > > > > > Just to be sure please attach the rhev-agent logs > > > > I have uploaded the rhev files in guest under "C:\Program Files > > (x86)\Redhat\RHEV",hope that is what you want,anything else please let me > > know. > > Could you please provide also the vdsm logs for the moment when this is not > working. I boot the guest on local host with qemu-kvm command,didnot install rhevm package,so there is no vdsm log.
Created attachment 838333 [details] service start error RHEV-Agent service does not start at all because 'Error 1075: The dependency service does not exist or has been marked for deletion.' Deps: * Remote Desktop Services * Remote Procedure Call (RPC) * DCOM Server Process Launcher * RPC Endpoint Mapper
FYI There's an issue with VirtIO-Serial driver installation on W2K12 R2, thus I created BZ1044915.
(In reply to Jiri Belka from comment #19) > FYI There's an issue with VirtIO-Serial driver installation on W2K12 R2, > thus I created BZ1044915. There is no win2k12R2 drivers in virtio-win package ,pls try to install the win2k12 one instead from virtio-win package currently Miie
ok, 3.2.18. Agents reports OK on w2k12r2 when having virtio-serial driver from virtio-win-1.6.7-3.el6_5.noarch (62.65.104.7000).
OK, based on comment #21.
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/RHBA-2013-1839.html