This part adds support for qemu making a macvtap tap device available via file descriptor passed to qemu command line. This also attempts to tear down the macvtap device when a VM terminates. This includes support for attachment and detachment to/from running VM.

Ed Swierk <eswierk(a)aristanetworks.com&gt; wrote on 02/12/2010 11:29:59 AM: > > On Thu, Feb 11, 2010 at 10:19 AM, Stefan Berger <stefanb(a)us.ibm.com&gt; wrote: > > This part adds support for qemu making a macvtap tap device available > > via file descriptor passed to qemu command line. This also attempts to > > tear down the macvtap device when a VM terminates. This includes support > > for attachment and detachment to/from running VM. > > In qemudShutdownVMDaemon(), calling delMacvtapByMACAddress() before > virKillProcess() doesn't work. delMacvtapByMACAddress() tries to be > polite and not delete the macvtap interface if it appears to be owned > by someone else, but in this case it's our own qemu still holding the > tap fd open: > > libvirtd: 16:10:04.836: error : openTap:567 : cannot open macvtap > tap device /dev/tap63: Device or resource busy > > When the qemu process does finally stop, the macvtap interface is > still around. How did you shut down the VM in this case? I may not have tried 'virsh shutdown', but halting from within the VM should clean up properly, or does this also not work?