Log filling with bogus(?) VLAN-related error message

[Ian Pilcher]

My syslog is getting flooded with messages like this:

Nov 19 15:27:16 ian libvirtd: 15:27:16.949: 2725: error :
virInterfaceDefParseXML:807 : XML description for vlan interface misses
the vlan element is not well formed or invalid

I do have tagged VLAN interfaces on the host (br0.1, br0.4, and
br0.251), but none of my VMs are using them.  I am not using any
libvirt-managed networks at all:

[pilcher@ian ~]$ sudo virsh net-list --all
Name                 State      Autostart
-----------------------------------------
default              inactive   no

I am running libvirt-0.8.8-7.fc15.x86_64.

Any ideas?

Thanks!

[Adam Huffman]

Came across your message when I saw similar errors.  In my case they
were interfering with the default network.

I found that running iface-undefine on the VLAN interfaces solved the problem.

Adam

On Sat, Nov 19, 2011 at 9:39 PM, Ian Pilcher  wrote:
> My syslog is getting flooded with messages like this:
>
> Nov 19 15:27:16 ian libvirtd: 15:27:16.949: 2725: error :
> virInterfaceDefParseXML:807 : XML description for vlan interface misses
> the vlan element is not well formed or invalid
>
> I do have tagged VLAN interfaces on the host (br0.1, br0.4, and
> br0.251), but none of my VMs are using them.  I am not using any
> libvirt-managed networks at all:
>
> [pilcher@ian ~]$ sudo virsh net-list --all
> Name                 State      Autostart
>
> default              inactive   no
>
> I am running libvirt-0.8.8-7.fc15.x86_64.
>
> Any ideas?
>
> Thanks!
> --
>
> Ian Pilcher                                         [e-mail]
> "If you're going to shift my paradigm ... at least buy me dinner first."
> ========================================================================
>
> virt mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/virt

[Ian Pilcher]

On 05/02/2012 05:54 AM, Adam Huffman wrote:
> Came across your message when I saw similar errors.  In my case they
> were interfering with the default network.
>
> I found that running iface-undefine on the VLAN interfaces solved the problem.

Cool!  Thanks!

[Adam Huffman]

On Sun, May 6, 2012 at 7:25 AM, Ian Pilcher  wrote:
> On 05/02/2012 05:54 AM, Adam Huffman wrote:
> > Came across your message when I saw similar errors.  In my case they
> > were interfering with the default network.
> >
> > I found that running iface-undefine on the VLAN interfaces solved the problem.
>
> Cool!  Thanks!

Actually 'iface-destroy' may be better.  In spite of the name, it
should stop the interface, rather than removing the configuration.