I may not have described it clearly.
i need to ensure the order of adding port to bridge and deleting from bridge.
i rename tap device to avoid the problem in my first patch.i think it can solve the problem.
my second patch may can't resolve the problem .
Do you have any better ideas?
thanks
为了让您的VPlat虚拟化故障得到高效的处理，请上报故障到: $VPlat技术支持。
芦志朋 luzhipeng
IT开发工程师 IT Development
Engineer
操作系统产品部/中心研究院/系统产品 OS Product Dept./Central R＆D Institute/System Product
 |  深圳市南山区科技南路55号中兴通讯研发大楼33楼 33/F, R&D Building, ZTE Corporation Hi-tech Road South, Hi-tech Industrial Park Nanshan District, Shenzhen, P.R.China, 518057 T: +86 755 xxxxxxxx F:+86 755 xxxxxxxx M: +86 xxxxxxxxxxx E: lu.zhipeng@xxxxxxxxxx www.zte.com.cn |
原始邮件
发件人： ＜berrange@xxxxxxxxxx＞;
收件人：芦志朋10108272;
抄送人： ＜libvir-list@xxxxxxxxxx＞; ＜laine@xxxxxxxxx＞;
日 期 ：2017年05月08日 17:42
主 题 ：Re: [libvirt]答复: Re: [PATCH v2] qemu: clean up network interfaces beforeqemuProcessKill is called in qemuProcessStop
On Mon, May 08, 2017 at 05:18:17PM +0800, lu.zhipeng@xxxxxxxxxx wrote:
＞ ＞This fix won't work correctly either. You cannot assume that libvirt has
＞ ＞control over when the QEMU process exits. It may exit itself *before*
＞ ＞libvirt runs any of its cleanup code.
＞
＞ I don't think there's a problem. Although libvirt does not runs cleanup
＞ code .but tap devices don't exist when when the QEMU process exits.
That still does not make sense. There is no difference in the way tap devices
are cleaned up whether QEMU exits "normally" on its own, or when libvirt kills
QEMU explicitly
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list
＞ ＞This fix won't work correctly either. You cannot assume that libvirt has
＞ ＞control over when the QEMU process exits. It may exit itself *before*
＞ ＞libvirt runs any of its cleanup code.
＞
＞ I don't think there's a problem. Although libvirt does not runs cleanup
＞ code .but tap devices don't exist when when the QEMU process exits.
That still does not make sense. There is no difference in the way tap devices
are cleaned up whether QEMU exits "normally" on its own, or when libvirt kills
QEMU explicitly
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
