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 1660123 - No spice channel is added for Windows guests
Summary: No spice channel is added for Windows guests
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-manager
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1653698
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-17 14:48 UTC by Radek Duda
Modified: 2020-11-14 13:51 UTC (History)
11 users (show)

Fixed In Version: virt-manager-2.2.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1653698
Environment:
Last Closed: 2019-11-05 21:19:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3464 0 None None None 2019-11-05 21:19:29 UTC

Description Radek Duda 2018-12-17 14:48:43 UTC 
+++ This bug was initially created as a clone of Bug #1653698 +++

Description of problem:
If I create VM in Virtual Machine Manager, no spice channel is added to VM configuration.

Version-Release number of selected component (if applicable):
virt-manager-2.0.0-1.el8.noarch
libvirt-3.10.0-2.el8+526+412dc3e0.x86_64

How reproducible:
always

Steps to Reproduce:
1. Click 'Create new virtual machine' in virt-manager GUI
2. In step 2 choose 'Microsoft Windows 10' or 'Microsoft Windows Server 2016'
3. Proceed

Actual results:
No spice channel is added to Windows VM, so that spice-vdagent is not functional

Expected results:
Spice channel is added to guest

Additional info:

--- Additional comment from Cole Robinson on 2018-12-13 22:35:40 CET ---

This is intentional though there's pluses and minuses. The reasoning for removing it is that windows VMs installed by virt-manager by default don't support virtio. So we were attaching a virtio-serial channel to the VM (for spice) that default windows couldn't recognize. This means an unknown device in windows device manager for example.

If users then run spice-guest-tools or similar and install spice + virtio bits, they then need to manually add a spice channel to the VM. I'm okay with this tradeoff since there's already manual steps involved.

Longer term I'd like to make it easier to make windows+virtio 'just work' out of the box in virt-manager. This will involve libosinfo unattended install support like boxes uses, and possibly friendlier virtio-win iso behavior.
Comment 1 Cole Robinson 2018-12-18 14:51:30 UTC 
Thanks for opening the RHEL bug, it's worth discussing. My comment above basically covers it, but it's not clear to me if attaching spice channel by default is better or worse. Granted no one complained up until this point so maybe it's just safer to go back, but since installing virtio drivers with virt-manager is a manual process anyways it's not too much to ask of users to manually add the spice channel as well. I'm interested in what others think
Comment 2 Karen Noel 2019-02-11 02:26:38 UTC 
Martin, Any comment whether this should be fixed or not? Does this require a doc change? Thanks.
Comment 3 Martin Tessun 2019-02-15 10:19:36 UTC 
(In reply to Karen Noel from comment #2)
> Martin, Any comment whether this should be fixed or not? Does this require a
> doc change? Thanks.

I believe we should document this in the user story for Windows guest.
@Jirka - Fine with you?
Comment 7 Pavel Hrdina 2019-02-22 11:25:51 UTC 
(In reply to Cole Robinson from comment #1)
> Thanks for opening the RHEL bug, it's worth discussing. My comment above
> basically covers it, but it's not clear to me if attaching spice channel by
> default is better or worse. Granted no one complained up until this point so
> maybe it's just safer to go back, but since installing virtio drivers with
> virt-manager is a manual process anyways it's not too much to ask of users
> to manually add the spice channel as well. I'm interested in what others
> think

There was one complain about it on IRC channel that virt-manager no longer adds
spice channel by default into windows guest.  Yes, it requires manual step that
you need to install drivers for it so I can understand the motivation to remove
it from default devices, however, I would rather revert this change and made it
default again.

Before this change it was fairly easy to get all the functionality with windows
guests, you would just install new guest from scratch, downloaded spice-guest-tools
and install all the drivers and everything worked.  Now you need to add the device
manually which IMHO makes things worse.
Comment 8 Cole Robinson 2019-02-26 15:44:42 UTC 
(In reply to Pavel Hrdina from comment #7)
> 
> There was one complain about it on IRC channel that virt-manager no longer
> adds
> spice channel by default into windows guest.  Yes, it requires manual step
> that
> you need to install drivers for it so I can understand the motivation to
> remove
> it from default devices, however, I would rather revert this change and made
> it
> default again.
> 
> Before this change it was fairly easy to get all the functionality with
> windows
> guests, you would just install new guest from scratch, downloaded
> spice-guest-tools
> and install all the drivers and everything worked.  Now you need to add the
> device
> manually which IMHO makes things worse.

Fine by me, let's add it back
Comment 10 Cole Robinson 2019-06-15 00:58:08 UTC 
This is back upstream now

commit d40975c493a554d179cca1c5c888cacfc2c9cd41 (HEAD -> master, origin/master)
Author: Cole Robinson <crobinso>
Date:   Fri Jun commit d40975c493a554d179cca1c5c888cacfc2c9cd41 (HEAD -> master, origin/master)
Author: Cole Robinson <crobinso>
Date:   Fri Jun 14 20:51:43 2019 -0400

    guest: Add back spice virtio-serial for windows
14 20:51:43 2019 -0400

    guest: Add back spice virtio-serial for windows
Comment 12 zhoujunqin 2019-07-30 09:21:39 UTC 
I can reproduce this issue with package:
virt-manager-2.0.0-5.el8.noarch

Then try to verify this package with build:
virt-manager-2.2.1-1.el8.noarch
libvirt-4.5.0-30.module+el8.1.0+3574+3a63752b.x86_64
qemu-kvm-2.12.0-82.module+el8.1.0+3738+0d8c0249.x86_64
python3-libvirt-4.5.0-2.module+el8.1.0+3531+2918145b.x86_64

Steps:
1. Click 'Create new virtual machine' in virt-manager GUI
2. In step 2 choose 'Microsoft Windows 10'.
3. Proceed until click 'Finish' button

Result:
Spice channel is added to Windows VM.
# virsh dumpxml win10

...
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
...
And it also works when i install win2k16 and win2k19, so I move this bug from ON_QA to VERIFIED.
Comment 14 errata-xmlrpc 2019-11-05 21:19:13 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/RHSA-2019:3464
Note You need to log in before you can comment on or make changes to this bug.