w2k12 is already supported, i suppose you wanted w2k12r2.
Yes, its w2k12r2. Thank You. --Uday
ok, 3.5.1
Original request: 1. What is the nature and description of the request? Currently we dont have a rhev-guest-tool that supports for Win8.1 and Win2K12 because of no spice and virtio-win driver. The customer needs the rhevm guest tool for Win8.1 and Win2K12. Based on BZ#1054216, its not available due to the below reason: - no spice driver for those OSes. - no virtio-win drivers for those OSes. Version-Release number of selected component (if applicable): rhevm 3.3 2. Why does the customer need this? (List the business requirements here) We should have this rhev-guest-tool for Win8.1 and Win2K12 as most of the customers deploying this in their RHEV environment due to the project requirement and lask of this is stopping them from using rhev.
(In reply to Yaniv Dary from comment #9) > Original request: > > 1. What is the nature and description of the request? > Currently we dont have a rhev-guest-tool that supports for Win8.1 and > Win2K12 because of no spice and virtio-win driver. > > The customer needs the rhevm guest tool for Win8.1 and Win2K12. Based on > BZ#1054216, its not available due to the below reason: > - no spice driver for those OSes. > - no virtio-win drivers for those OSes. > > Version-Release number of selected component (if applicable): > rhevm 3.3 > > 2. Why does the customer need this? (List the business requirements here) > > We should have this rhev-guest-tool for Win8.1 and Win2K12 as most of the > customers deploying this in their RHEV environment due to the project > requirement and lask of this is stopping them from using rhev. Please note: we do have virtio-win drivers for both 2K12R2 Server and Win 8.1, and they are already included in the rhev-guest-tools package. We do currently missing Spice (QXL) driver for 2K12, 2K12R2 and Win 8 and 8.1, as these are in development.
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/RHEA-2015-0198.html