Attachment 938397 Details for Bug 1045833 – source libvirtd.log

source libvirtd.log

libvirtd.log (text/plain), 24.29 KB, created by zhe peng on 2014-09-17 09:32:44 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: zhe peng

Created: 2014-09-17 09:32:44 UTC

Size: 24.29 KB

patch

obsolete

>2014-09-11 02:40:58.153+0000: 8880: info : libvirt version: 0.10.2, package: 45.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-09-02-09:54:39, x86-027.build.eng.bos.redhat.com)
>2014-09-11 02:40:58.153+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table nat --delete POSTROUTING --source 192.168.122.0/24 -p tcp '!' --destination 192.168.122.0/24 --jump MASQUERADE --to-ports 1024-65535) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-11 02:40:58.155+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table nat --delete POSTROUTING --source 192.168.122.0/24 -p udp '!' --destination 192.168.122.0/24 --jump MASQUERADE --to-ports 1024-65535) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-11 02:40:58.156+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table nat --delete POSTROUTING --source 192.168.122.0/24 '!' --destination 192.168.122.0/24 --jump MASQUERADE) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-11 02:40:58.157+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --destination 192.168.122.0/24 --out-interface virbr0 --match state --state ESTABLISHED,RELATED --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-11 02:40:58.158+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --source 192.168.122.0/24 --in-interface virbr0 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-11 02:40:58.159+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --in-interface virbr0 --out-interface virbr0 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-11 02:40:58.160+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --out-interface virbr0 --jump REJECT) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-11 02:40:58.161+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --in-interface virbr0 --jump REJECT) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-11 02:40:58.163+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 53 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-11 02:40:58.164+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 53 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-11 02:40:58.173+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table mangle --delete POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68 --jump CHECKSUM --checksum-fill) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-11 02:40:58.174+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 67 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-11 02:40:58.175+0000: 8880: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-11 03:06:25.502+0000: 9484: info : libvirt version: 0.10.2, package: 46.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-09-09-07:49:04, x86-022.build.eng.bos.redhat.com)
>2014-09-11 03:06:25.502+0000: 9484: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: rtm, invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-11 03:08:31.637+0000: 9483: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: rtm, invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-11 05:43:07.933+0000: 9485: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: rtm, invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-11 06:03:14.600+0000: 9485: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: rtm, invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-11 06:06:37.908+0000: 9483: error : virStorageFileGetMetadataRecurse:952 : Failed to open file '/var/lib/libvirt/images/kvm-rhel6.4-x86_64-qcow2.img': No such file or directory
>2014-09-11 06:06:37.908+0000: 9483: error : qemuRemoveCgroup:797 : internal error Unable to find cgroup for test
>2014-09-11 06:06:37.908+0000: 9483: warning : qemuProcessStop:4581 : Failed to remove cgroup for test
>2014-09-11 06:07:08.210+0000: 9484: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: rtm, invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-11 06:09:15.866+0000: 9482: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: rtm, invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-11 06:10:26.454+0000: 9482: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: rtm, invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-11 06:10:56.032+0000: 9483: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-11 06:13:34.052+0000: 9481: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: rtm, invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-11 06:42:52.582+0000: 9484: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:42:52.588+0000: 9484: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:42:52.588+0000: 9484: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:42:52.666+0000: 9484: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:42:52.666+0000: 9484: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:42:52.669+0000: 9484: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:47:31.835+0000: 6653: info : libvirt version: 0.10.2, package: 45.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-09-02-09:54:39, x86-027.build.eng.bos.redhat.com)
>2014-09-11 06:47:31.835+0000: 6653: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:47:31.840+0000: 6653: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:47:31.841+0000: 6653: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:47:31.915+0000: 6653: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:47:31.915+0000: 6653: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:47:31.919+0000: 6653: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-11 06:52:32.298+0000: 7048: info : libvirt version: 0.10.2, package: 46.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-09-09-07:49:04, x86-022.build.eng.bos.redhat.com)
>2014-09-11 06:52:32.298+0000: 7048: error : qemuBuildCpuArgStr:4522 : unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: rtm, invpcid, erms, bmi2, smep, avx2, hle, bmi1, fsgsbase, abm, pdpe1gb, rdrand, f16c, movbe, fma, monitor
>2014-09-17 08:01:27.861+0000: 7049: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:01:28.095+0000: 7049: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:01:28.096+0000: 7049: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:01:28.565+0000: 7049: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:01:28.565+0000: 7049: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:01:28.569+0000: 7049: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:11:43.116+0000: 7048: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:11:43.408+0000: 7048: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:11:43.409+0000: 7048: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:11:43.874+0000: 7048: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:11:43.874+0000: 7048: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:11:43.878+0000: 7048: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:26:17.618+0000: 7046: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:26:17.767+0000: 7046: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:26:17.767+0000: 7046: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:26:18.230+0000: 7046: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:26:18.230+0000: 7046: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:26:18.234+0000: 7046: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:35:14.104+0000: 7045: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:35:14.247+0000: 7045: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:35:14.248+0000: 7045: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:35:14.715+0000: 7045: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:35:14.715+0000: 7045: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:35:14.718+0000: 7045: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:37:36.052+0000: 7044: error : qemuMonitorIORead:515 : Unable to read from monitor: Connection reset by peer
>2014-09-17 08:38:34.316+0000: 7045: error : virSecurityDACRestoreSecurityFileLabel:295 : cannot resolve symlink /var/lib/libvirt/migrate/kvm-rhel6.5-x86_64-qcow2v2.img: Input/output error
>2014-09-17 08:49:27.716+0000: 7047: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:49:27.853+0000: 7047: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:49:27.854+0000: 7047: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:49:28.323+0000: 7047: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:49:28.323+0000: 7047: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:49:28.327+0000: 7047: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 08:57:00.686+0000: 4345: info : libvirt version: 0.10.2, package: 39.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-06-23-13:41:14, x86-022.build.eng.bos.redhat.com)
>2014-09-17 08:57:00.686+0000: 4345: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --destination 192.168.122.0/24 --out-interface virbr0 --match state --state ESTABLISHED,RELATED --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 08:57:00.688+0000: 4345: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --source 192.168.122.0/24 --in-interface virbr0 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 08:57:00.690+0000: 4345: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --in-interface virbr0 --out-interface virbr0 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 08:57:00.693+0000: 4345: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --out-interface virbr0 --jump REJECT) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-17 08:57:00.695+0000: 4345: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --in-interface virbr0 --jump REJECT) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-17 08:57:00.696+0000: 4345: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 53 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 08:57:00.697+0000: 4345: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 53 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 08:57:00.700+0000: 4345: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 67 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 08:57:00.701+0000: 4345: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 09:01:06.752+0000: 4469: info : libvirt version: 0.10.2, package: 39.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-06-23-13:41:14, x86-022.build.eng.bos.redhat.com)
>2014-09-17 09:01:06.752+0000: 4469: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:01:06.881+0000: 4469: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:01:06.882+0000: 4469: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:01:07.343+0000: 4469: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:01:07.343+0000: 4469: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:01:07.347+0000: 4469: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:08:35.383+0000: 4887: info : libvirt version: 0.10.2, package: 46.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-09-09-07:49:04, x86-022.build.eng.bos.redhat.com)
>2014-09-17 09:08:35.383+0000: 4887: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --destination 192.168.122.0/24 --out-interface virbr0 --match state --state ESTABLISHED,RELATED --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 09:08:35.385+0000: 4887: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --source 192.168.122.0/24 --in-interface virbr0 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 09:08:35.387+0000: 4887: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --in-interface virbr0 --out-interface virbr0 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 09:08:35.389+0000: 4887: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --out-interface virbr0 --jump REJECT) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-17 09:08:35.391+0000: 4887: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --in-interface virbr0 --jump REJECT) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-09-17 09:08:35.393+0000: 4887: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 53 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 09:08:35.394+0000: 4887: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 53 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 09:08:35.398+0000: 4887: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 67 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 09:08:35.400+0000: 4887: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-09-17 09:14:12.479+0000: 5001: info : libvirt version: 0.10.2, package: 46.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-09-09-07:49:04, x86-022.build.eng.bos.redhat.com)
>2014-09-17 09:14:12.479+0000: 5001: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:14:12.634+0000: 5001: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:14:12.635+0000: 5001: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:14:13.096+0000: 5001: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:14:13.096+0000: 5001: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous
>2014-09-17 09:14:13.100+0000: 5001: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous

Actions: View

Attachments on bug 1045833: 846626 | 937958 | 937962 | 938397