Maybe someone here can help point out where and why these messages are printed to console when running Xen?
[133721.499956] physdev match: using --physdev-out in the OUTPUT,
FORWARD and POSTROUTING chains for non-bridged traffic is not supported
anymore.
-M
From: viaum@xxxxxxxxxxxxxxx
To: xen-users@xxxxxxxxxxxxxxxxxxx
Date: 2010年4月19日 23:06:35 -0400
Subject: [Xen-users] Xen networking - dom0 kernel message - question
What causes the Dom0 kernel to post messages like this:
[133721.499956] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
???
My stubdom-dm DomU networking line is: vif = [ 'type=ioemu, mac=00:16:3e:11:12:01, bridge=br200' ]
root@xen-host:~# xm info
host : xen-host.site
release : 2.6.33.2
version : #1 SMP Wed Apr 14 19:55:12 EDT 2010
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 2800
hw_caps : bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 8139
free_memory : 2903
node_to_cpu : node0:0-7
node_to_memory : node0:2903
node_to_dma32_mem : node0:2903
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .1-rc1-pre
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Mon Apr 12 18:29:36 2010 +0100 21107:11010cf627c8
xen_commandline : dom0_mem=2048M com1=115200,8n1,0x1008,21 console=com1,vga
cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1)
cc_compile_by : root
cc_compile_domain : site
cc_compile_date : Thu Apr 15 10:35:36 EDT 2010
xend_config_format : 4
-M
Videos that have everyone talking! Now also in HD!
MSN.ca Video.