Bug 990767

Summary: RFE: add support for 'unix' and 'pty' channels
Product: [Community] Virtualization Tools Reporter: Jonathan Lebon <jlebon>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, berrange, crobinso
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-17 14:11:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Lebon 2013-08-01 00:17:13 UTC 
Description of problem:

Right now, the virt-manager GUI only allows users to add 'spicevmc' channels. However, there are two other possible types: 'pty' and 'unix' (see http://libvirt.org/formatdomain.html#elementCharChannel). Just like the 'spicevmc' channel, this would also automatically add a Controller Virtio Serial device to the VM. The extra XML that would be generated for a virtio-serial UNIX socket looks like this:

<devices>
  ...
  <controller type='virtio-serial' index='0' ports='16' vectors='4'/>
  <channel type='unix'>
    <source mode='bind' path='/tmp/foobar'/>
    <target type='virtio' name='my_virtio_port'/>
  </channel>
  ...
</devices>

It seems like virt-manager has *some* knowledge of these devices since modifying the XML does result in virt-manager showing them in the list. There's just no way of creating them directly from within the GUI as it stands.

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

virt-manager-0.10.0-1.fc19.noarch
Comment 1 Cole Robinson 2013-08-17 14:11:44 UTC 
This is upstream now