From b1972ce50be530707bd60b8835db0c191bd2379f Mon Sep 17 00:00:00 2001 From: Laine Stump Date: Tue, 24 Mar 2015 10:45:09 -0400 Subject: [PATCH] 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. (cherry picked from commit dae3e246637a8863a1988683b0c43f461a1b4a5d) --- src/qemu/qemu_driver.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c index 0876cb08aa..ab681cc9d5 100644 --- a/src/qemu/qemu_driver.c +++ b/src/qemu/qemu_driver.c @@ -4367,7 +4367,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