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.
Bug 1016861 - Starting the RHEV Spice Agent on the Windows VM, results in the guest in a hung state.
Summary: Starting the RHEV Spice Agent on the Windows VM, results in the guest in a hu...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-vdagent-win
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-08 20:16 UTC by Bill Sanford
Modified: 2019-10-10 14:20 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-12 16:13:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bill Sanford 2013-10-08 20:16:54 UTC
Description of problem:
Install the tools-ISO from rhev-guest-tools-iso-3.3-6.noarch.rpm on the Windows guest. Then you restart the guest from the install.

At this point, the RHEV Spice Agent should be automatically started but it's not and it needs to be turned on in Windows "Services." Once you "Start" the service on the guest, the VM hangs.

At this hang of the VM, if you force the VM off and restart it, the RHEV Spice Agent is now working and the RHEV Spice Agent is now starting automatically.

Version-Release number of selected component (if applicable):
RHEL6.5-20130925.2
Windows & and XP VMs
rhev-guest-tools-iso-3.3-6.noarch.rpm

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Christophe Fergeau 2013-10-09 09:13:37 UTC
Would be interesting to have some logs from the tool installer and from vdagent right after installation. 'the VM hangs' makes me suspect a virtio-serial bug rather than an agent one.

Comment 2 Christophe Fergeau 2013-10-09 11:59:40 UTC
For what it's worth, I just tried to install rhev-guest-tools-iso-3.3-6.noarch.rpm on a RHEL6 host with qemu-kvm-rhev-0.12.1.2-2.406.el6.x86_64 and spice-server-0.12.4-3.el6.x86_64 in a win7sp1 32 bit guest. Arbitrary resolution and c&p between host and guest worked as soon as the installation finished, even without a reboot. After a reboot, the agent is still running.
In short, I could not reproduce this, not sure what difference causes this to trigger in your setup.

Comment 3 Bill Sanford 2013-10-09 13:54:10 UTC
I am running Windows 8.1 for a client.

Comment 4 Christophe Fergeau 2013-10-11 12:09:08 UTC
I tried with a win7 client just in case, and could not reproduce either. How are you creating the VM? Can you give exact name/version number of all components involved? (qemu-kvm and spice-server are likely to be the most interesting ones). Did you manage to reproduce this multiple times?

Comment 5 David Blechter 2013-12-09 17:55:54 UTC
can you provide the answer on the above questions? 
I think that the access to this specific VM will help as well.

Comment 7 Bill Sanford 2013-12-12 16:13:02 UTC
I am not seeing this in RHEV-M 3.3 (is26). I will reopen if this is a problem.


Note You need to log in before you can comment on or make changes to this bug.