Bug 674660

Summary:	Create virtio-serial channel for Matahari usage in specific guests by default
Product:	[Community] Virtualization Tools	Reporter:	Perry Myers <pmyers>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, berrange, crobinso, jforbes, matahari-maint, virt-maint, xen-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	674658	Environment:
Last Closed:	2013-07-23 19:16:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	674658, 767461

Description Perry Myers 2011-02-02 20:30:40 UTC

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

Description of problem:
For Matahari usage we need a virtio-serial device created by default (along with the channel) so that the user doesn't have to worry about configuring this manually.

Channel name should be "org.apache.qpid.matahari.0"

The initial guest OS types that should have this device/channel by default are:

RHEL5
RHEL6
Fedora 14+ (older Fedora's support virtio-serial but we don't anticipate porting the AMQP/virtio-serial transport plugin back further than F14)
Windows (all types)

Comment 1 Cole Robinson 2013-04-21 19:12:14 UTC

virtinst has been merged into virt-manager.git. Moving all virtinst bugs to the virt-manager component.

Comment 2 Cole Robinson 2013-07-23 19:16:50 UTC

Matahari is dead so this isn't really relevant anymore.