From: Laine Stump <laine@laine.org>
Date: Tue, 24 Mar 2015 14:45:09 +0000 (-0400)
Subject: qemu: change accidental VIR_WARNING back to VIR_DEBUG
X-Git-Tag: v1.2.14-rc1~54
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=dae3e246637a8863a1988683b0c43f461a1b4a5d;p=thirdparty%2Flibvirt.git

qemu: change accidental VIR_WARNING back to VIR_DEBUG

While debugging the support for responding to qemu RX_FILTER_CHANGED
events, I had changed the "ignoring this event" log message from
VIR_DEBUG to VIR_WARN, but forgot to change it back before
pushing. Since many guest OSes make enough changes to multicast lists
and/or promiscuous mode settings to trigger this message, it's
starting to show up as a red herring in bug reports.
---

diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c
index 80a3d77777..45b5ec8e8d 100644
--- a/src/qemu/qemu_driver.c
+++ b/src/qemu/qemu_driver.c
@@ -4340,7 +4340,7 @@ processNicRxFilterChangedEvent(virQEMUDriverPtr driver,
     def = dev.data.net;
 
     if (!virDomainNetGetActualTrustGuestRxFilters(def)) {
-        VIR_WARN("ignore NIC_RX_FILTER_CHANGED event for network "
+        VIR_DEBUG("ignore NIC_RX_FILTER_CHANGED event for network "
                   "device %s in domain %s",
                   def->info.alias, vm->def->name);
         /* not sending "query-rx-filter" will also suppress any