Bug 1005698 - [User Portal] Windows 2012 default console from Windows client is SPICE
[User Portal] Windows 2012 default console from Windows client is SPICE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-userportal (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: nobody nobody
Pavel Stehlik
Depends On:
  Show dependency treegraph
Reported: 2013-09-09 04:32 EDT by Jiri Belka
Modified: 2013-10-02 11:05 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-02 11:05:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jiri Belka 2013-09-09 04:32:31 EDT
Description of problem:
There's still no qxl driver for w2k12, thus SPICE is not very efficient. But recently when a user access User Portal from a Windows client, then he sees SPICE as default console protocol for W2k12.

It used to be RDP - BZ878676. There was another BZ - BZ957822, but this one is closeddeferred. Thus shouldn't w2k12 still be RDP?

(fyi windows 8 has qxl driver, so SPICE for this OS type is OK.)

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

How reproducible:

Steps to Reproduce:
1. create a vm as w2k12
2. access user portal from a windows client and check what kind of console has this w2k12 in user portal

Actual results:

Expected results:
rdp (until there's qxl driver for this os type)

Additional info:
Comment 2 Jiri Belka 2013-10-02 11:05:08 EDT
Spice QE guys told me Windows 8 does _NOT_ have qxl driver. But in is17 from Windows XP client I can see w2k12 and w8 have RDP as console type, I suppose it was repaired with this BZ1012048.

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