Bug 1147195
Summary: | Libvirt should remove <backend> element on unsupported interface model in XML | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Hu Jianwei <jiahu> |
Component: | libvirt | Assignee: | Ján Tomko <jtomko> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.1 | CC: | dyuan, honzhang, mzhan, rbalakri |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libvirt-1.2.13-1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 05:53:29 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
Hu Jianwei
2014-09-28 03:30:57 UTC
Upstream patches: https://www.redhat.com/archives/libvir-list/2015-February/msg00154.html With these, the vhost element is only parsed for virtio interfaces. For 'network' interfaces, the usability of the custom tap device depends on the type of the actual network, so it cannot be checked at definition. The second patch checks it on domain startup. Now pushed upstream: commit 8e724e9f3eab08ff1bef96ce1b3319558a86176b Author: Ján Tomko <jtomko> CommitDate: 2015-02-06 12:52:50 +0100 Error out when custom tap device path makes no sense It is only usable for NETWORK and BRIDGE type interfaces. Error out when trying to start a domain where the custom tap device path is specified for interfaces of other types, or when the daemon is not privileged. Note that this cannot be checked at definition time, because the comparison is against actual type. https://bugzilla.redhat.com/show_bug.cgi?id=1147195 git describe: v1.2.12-84-g8e724e9 commit 84f741812f970f9ee9b857673c03433f7c2866a6 CommitDate: 2015-02-06 12:52:50 +0100 Only parse custom vhost path for virtio interfaces It is only supported for virtio adapters. Silently drop it if it was specified for other models, as is done for other virtio attributes. Also mention this in the documentation. https://bugzilla.redhat.com/show_bug.cgi?id=1147195 git describe: v1.2.12-83-g84f7418 Verify it as follows. The result is expected. Move its status to VERIFIED. # rpm -q libvirt libvirt-1.2.14-1.el7.x86_64 # cat r7a.xml|grep /interface -B5 <interface type='network'> <mac address='52:54:00:cc:6d:e8'/> <source network='default'/> <model type='rtl8139'/> <backend tap='/dev/net/tun' vhost='/dev/vhost-net'/> </interface> # virsh define r7a.xml Domain r7a defined from r7a.xml # virsh start r7a Domain r7a started # virsh dumpxml r7a|grep /interface -B8 <interface type='network'> <mac address='52:54:00:cc:6d:e8'/> <source network='default'/> <target dev='vnet1'/> <model type='rtl8139'/> <backend tap='/dev/net/tun'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2202.html |