Hello, Thank you for replying. I managed to see printk() on dmesg, I was debugging wrong (I'm new in this kernel-space area).
I traced my mistake and I found it, thank you very much for your help Kind regards, Raúl 2015-08-06 20:14 GMT+02:00 Joe Stringer <joestrin...@nicira.com>: > --verbose makes the ovs-ofctl process more verbose by allowing the > VLOG_DBG() functions to print to the terminal. > > For kernel debugging, you want printk() or OVS_NLERR(), and these will > print to the kernel log (which shows up in dmesg). If you're not able > to see it there, then it may mean that your code isn't executing (are > you sure that your own custom version of the module is inserted into > the kernel?) > > On 6 August 2015 at 10:52, Raul Suarez Marin > <raul.suarez.ma...@gmail.com> wrote: > > Is there a way of adding messages myself and see them thorugh --verbose? > I > > was told that "printk()" did that but I'm not able to see it anywhere :( > > > > Thank you for your answer, > > > > Kind regards, > > Raúl > > > > 2015-08-05 22:40 GMT+02:00 Joe Stringer <joestrin...@nicira.com>: > >> > >> On 5 August 2015 at 13:02, Raul Suarez Marin > >> <raul.suarez.ma...@gmail.com> wrote: > >> > Hello everyone, > >> > > >> > I am developing a new match option in the datapath. I implemented > almost > >> > everything already, but I am missing something and I don't know what > nor > >> > what is next step. > >> > > >> > Adding the flow directly to the datapath gives the following error: > >> > ovs-dpctl: updating flow table (Invalid argument) > >> > > >> > The full "stack" > >> > > >> > sudo ovs-dpctl add-flow "ovs-system" > >> > > >> > > "in_port(3),eth(src=00:00:00:00:ca:fe,dst=05:05:05:05:05:05),eth_type(0x0800),ipv4(src= > >> > > >> > > 10.10.0.1/255.255.255.255,dst=10.10.0.2/255.255.255.255,proto=17/0xff,tos=0/0,ttl=64/0,frag=no/0xff > ),udp(src=2152/0,dst=2152/0xffff),new_match_option(11259375/0xffffffff)" > >> > "1" > >> > > >> > 2015-08-05T19:58:58Z|00001|dpif|WARN|system@ovs-system: failed to > >> > put[create] (Invalid argument) > >> > > >> > > in_port(3),eth(src=00:00:00:00:ca:fe,dst=05:05:05:05:05:05),eth_type(0x0800),ipv4(src= > >> > > >> > > 10.10.0.1/255.255.255.255,dst=10.10.0.2/255.255.255.255,proto=17/0xff,tos=0/0,ttl=64/0,frag=no/0xff > >> > > >> > > ),udp(src=2152/0,dst=2152/0xffff),new_match_option(id=11259375/0xffffffff) > >> > ovs-dpctl: updating flow table (Invalid argument) > >> > > >> > > >> > Any thoughts, hints or comments are appreciated. > >> > >> dmesg may also have some information. > >> > >> You can use "--verbose" to see more detail on what is actually > >> happening from the ovs-dpctl perspective. But it looks like the kernel > >> is rejecting your flow installation because you're providing an > >> invalid argument (EINVAL), so you'll need to trace through the > >> ovs_flow_cmd_new() code to see why that might be the case. > > > > > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
