Bug 794540

Summary: Allow macvtap as an option in virt-manager when creating a new VM
Product: [Community] Virtualization Tools Reporter: Perry Myers <pmyers>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, crobinso, xen-maint
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: 2014-01-28 15:02:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Perry Myers 2012-02-17 03:37:08 UTC 
Description of problem:
When creating a new VM in virt-manager the default network is usually the NAT'd network named 'default'

But via the Advanced Options section it is possible to select other networks to attach to the guest in place of the NAT/default network.

However this screen does not seem to show macvtap linked to a physical interface as an option.  So if you want to use macvtap you need to create the VM and then later change the network interface through the VM details page NIC section.

It would be good to add options to the Advanced Options section of the 'Create a new virtual machine' page to show things like:

Host device eth0: macvtap
Host device em0: macvtap
etc, etc

In addition, we'd need to add a new drop down to the Advanced options section that is only enabled when macvtap is selected that allows the user to choose between options like Bridge, VEPA, Passthrough
Comment 1 Cole Robinson 2014-01-28 15:02:22 UTC 
Upstream now