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 1470649 - [virtio-win[qemu-ga-win][upstream]]Unable to install qemu-ga on Windows platform : QEMU guest agent -- Error 1722
Summary: [virtio-win[qemu-ga-win][upstream]]Unable to install qemu-ga on Windows platf...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.4
Hardware: x86_64
OS: Windows
medium
medium
Target Milestone: rc
: ---
Assignee: Sameeh Jubran
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1357789
Blocks: 1473046
TreeView+ depends on / blocked
 
Reported: 2017-07-13 11:33 UTC by xiagao
Modified: 2018-04-10 06:33 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1357789
Environment:
Last Closed: 2018-04-10 06:31:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0657 0 None None None 2018-04-10 06:32:59 UTC

Description xiagao 2017-07-13 11:33:35 UTC 
When testing upstream qemu-ga-win,hit the same issue like comment 0 of Bug #1357789.
Version-Release number of selected component (if applicable):
Host kernel: kernel-3.10.0-691.el7.x86_64
Qemu-kvm-rhev: qemu-kvm-rhev-2.9.0-14.el7.x86_64
qemu-ga-win: qemu-ga-win-x64-2.9.0-2.el7ev.noarch



+++ This bug was initially created as a clone of Bug #1357789 +++

Description of problem:

Error message when executing qemu-ga-x64.msi :

There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.

From the windows logs we can see :

Product: QEMU guest agent -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action RegisterCom, location: C:\Program Files\qemu-ga\qemu-ga.exe, command: -s vss-install

Trying to install manually : 

C:\Program Files\AgentQemu>qemu-ga.exe -s install
Registering QEMU Guest Agent VSS Provider:
  C:\Program Files\AgentQemu\qga-vss.dll
  C:\Program Files\AgentQemu\qga-vss.tlb
Failed to pUsersInRole->SaveChanges. (Error: 8000ffff) Défaillance irrémédiable

Removing COM+ Application: QEMU Guest Agent VSS Provider
Unfortunately it doesn't install correctly.

Tested on French windows versions : Windows 2008 R2, Windows 2012 R2 and Windows 7 x64 with latest 0.1.118 virtio drivers installed, qemu agent enabled in Proxmox VM config, UAC disabled and localadmin account.

Version-Release number of selected component (if applicable):

0.1.118

--- Additional comment from Yan Vugenfirer on 2016-07-19 04:55:03 EDT ---

Hello,

Thank you for the report:

* What is the version of the package you are using? 

* Can you please provide full log?

Best regards,
Yan.

--- Additional comment from Silberlog on 2016-07-19 06:03:53 EDT ---

(In reply to Yan Vugenfirer from comment #1)
> Hello,
> 
> Thank you for the report:
> 
> * What is the version of the package you are using? 
> 
> * Can you please provide full log?
> 
> Best regards,
> Yan.

Hello,

Thanks for helping.
Package comes from virtio-win-0.1.118.iso.
You'll find the msiexec full log (msiexec /i qemu-ga-x64.msi /log c:\qemuga.log) in attachement.

Regards,

Thomas

--- Additional comment from Silberlog on 2016-07-19 06:04 EDT ---



--- Additional comment from Laurent Bigonville on 2016-10-05 15:46:50 EDT ---

Hi,

I can confirm this with a windows 7 VM

--- Additional comment from Yan Vugenfirer on 2016-10-27 08:18:26 EDT ---

Can you check that you have sufficient permission?

https://support.microsoft.com/en-us/kb/834484

--- Additional comment from Silberlog on 2016-10-29 09:24:52 EDT ---

(In reply to Yan Vugenfirer from comment #5)
> Can you check that you have sufficient permission?
> 
> https://support.microsoft.com/en-us/kb/834484

Hi,

Tests have been made with a fresh, up-to-date windows 2012 R2 install, UAC disabled and under local administrator account session.

Regards,

--- Additional comment from Martin Beaudet on 2016-11-27 16:24:29 EST ---

Hi Silberlog, have you find a solution of your problem. I have the same, i tried many thing, many guest agent like Spice or Stratus GA but don't work correctly with proxmox.

If you have the solution, please reply me, i desperate. Same probleme with Windows 8.1 et 2012 R2 64 bits.

Thank you.

--- Additional comment from EdouardB on 2017-02-22 05:05:00 EST ---

Hello, have you news for this bug ?

https://forum.proxmox.com/threads/error-installing-windows-qemu-agent.25597/

The problem is the language of Windows, in english it's ok

Ed

--- Additional comment from Benjamin Bellec on 2017-03-13 07:16:06 EDT ---

Hello,

I have the same error.
Also on a french Win 7 Pro (64-bit) version.

Tested with qemu-ga-win-7.3.2-1 (x64 msi).
VirtIO-serial is already installed on the VM (virtio-win 0.1.133).

--- Additional comment from Yan Vugenfirer on 2017-03-15 07:54:45 EDT ---



--- Additional comment from Yan Vugenfirer on 2017-04-18 04:18:16 EDT ---

Hardcoded names were used during installation for "Administrator" and "system", changing it to well know SSIDs according to MS documentation.
Patch is on a way.

--- Additional comment from Benjamin Bellec on 2017-04-21 10:28:15 EDT ---

Good news !
Do you know when a fixed qemu-ga.exe release will be available ?

--- Additional comment from EdouardB on 2017-05-09 03:21:10 EDT ---

Heelo, I've receive the notify from this post
https://forum.proxmox.com/threads/error-installing-windows-qemu-agent.25597/page-2

And i test it's ok for me with the last 1.136 Windows Pro 7 French 64bits

Ed

--- Additional comment from Yan Vugenfirer on 2017-05-09 04:30:25 EDT ---

Yes, the issues is solved in build 136.

--- Additional comment from  on 2017-05-23 02:42:18 EDT ---

Reproduced in qemu-ga-win-7.3.2-1.
Guest: french Win 7 Pro (64-bit) version

Verifed in qemu-ga-win-7.4.5-1.
Guest:  french Win 7 Pro (64-bit) version
Comment 3 Sameeh Jubran 2017-07-17 12:27:20 UTC 
We already have a patch for this, however it still hasn't been reviewed and accepted upstream, once it is in I'll apply it.

https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg00927.html
Comment 4 Sameeh Jubran 2017-07-23 12:30:14 UTC 
(In reply to Sameeh Jubran from comment #3)
> We already have a patch for this, however it still hasn't been reviewed and
> accepted upstream, once it is in I'll apply it.
> 
> https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg00927.html

The patch is currently in upstream, I have applied it to our mingw-qemu-ga-win repo.

Can you test and confirm this? here is an up-to-date build:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13705580
Comment 5 Sameeh Jubran 2017-08-13 16:24:10 UTC 
Hi Xiaoling,
Can you please test this so we can close this BZ?
Comment 6 xiagao 2017-08-14 00:13:42 UTC 
(In reply to Sameeh Jubran from comment #5)
> Hi Xiaoling,
> Can you please test this so we can close this BZ?

Sure, but the build is closed, could you build another one?
btw,yesterday is the weekend so I did not get it. :)
Thanks.
Comment 7 Sameeh Jubran 2017-08-14 07:03:54 UTC 
(In reply to xiagao from comment #6)
> (In reply to Sameeh Jubran from comment #5)
> > Hi Xiaoling,
> > Can you please test this so we can close this BZ?
> 
> Sure, but the build is closed, could you build another one?

Sure no problem, here you go:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13834555
=)
> btw,yesterday is the weekend so I did not get it. :)
> Thanks.
Comment 9 Sameeh Jubran 2017-08-14 07:54:17 UTC 
Do you need any additional thing from me?
Comment 10 Sameeh Jubran 2017-08-14 07:55:21 UTC 
Do you need any additional thing from me? ( needinfo flag?)
Comment 11 xiagao 2017-08-14 08:06:06 UTC 
(In reply to Sameeh Jubran from comment #10)
> Do you need any additional thing from me? ( needinfo flag?)

yes, it's failed when I tried to install the rpm pkg you provided.I had no idea about it. Did I miss something ?
Comment 12 Sameeh Jubran 2017-08-14 08:16:47 UTC 
(In reply to xiagao from comment #11)
> (In reply to Sameeh Jubran from comment #10)
> > Do you need any additional thing from me? ( needinfo flag?)
> 
> yes, it's failed when I tried to install the rpm pkg you provided.I had no
> idea about it. Did I miss something ?

This is weird, I only applied the path from upstream, either way, can you please provide me with the test environment that you are using? (Guest Os version, virtio-serial driver version, Which language is the OS)
Comment 15 Sameeh Jubran 2017-08-15 09:01:12 UTC 
I think that I have figured out why this error is still showing, can you please try this build:
 https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13843940
Comment 16 xiagao 2017-08-15 09:29:30 UTC 
(In reply to Sameeh Jubran from comment #15)
> I think that I have figured out why this error is still showing, can you
> please try this build:
>  https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13843940


The output item in this build is empty.  :(
Could you have another check ?
Comment 17 Sameeh Jubran 2017-08-15 09:34:08 UTC 
(In reply to xiagao from comment #16)
> (In reply to Sameeh Jubran from comment #15)
> > I think that I have figured out why this error is still showing, can you
> > please try this build:
> >  https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13843940
> 
> 
> The output item in this build is empty.  :(
> Could you have another check ?

You need to click on the "buildArch (mingw-qemu-ga-win-2.9.0-2.el7.src.rpm, noarch)

And that would lead you to this:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13843941

I can see that the output here is not empty...
Comment 18 xiagao 2017-08-16 05:58:20 UTC 
(In reply to Sameeh Jubran from comment #17)
> (In reply to xiagao from comment #16)
> > (In reply to Sameeh Jubran from comment #15)
> > > I think that I have figured out why this error is still showing, can you
> > > please try this build:
> > >  https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13843940
> > 
> > 
> > The output item in this build is empty.  :(
> > Could you have another check ?
> 
> You need to click on the "buildArch (mingw-qemu-ga-win-2.9.0-2.el7.src.rpm,
> noarch)
> 
> And that would lead you to this:
> https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13843941
> 
> I can see that the output here is not empty...


Thank you very much,it's ok now.
Comment 19 xiagao 2017-08-16 06:00:39 UTC 
Verified this bug with the build in https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13843941.
Comment 21 errata-xmlrpc 2018-04-10 06:31:38 UTC 
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://access.redhat.com/errata/RHBA-2018:0657
Note You need to log in before you can comment on or make changes to this bug.