Boris Derzhavets
2009-Jul-19 09:03 UTC
How to disable checksum offloading for OSOL DomU via kmdb at initial boot ?
Adding -kd to extra line drops me to kmdb :-
root@ServerJaunty:/home/boris/nevada# xm create -c osol.install
Using config file "./osol.install".
Started domain osol.install (id=4)
Loading kmdb...
Welcome to kmdb
Loaded modules: [ unix krtld genunix ]
[0]>
I want patch kernel like it happens when adding to /etc/system:-
set xnf:xnf_cksum_offload = 0
Please, advise how to manage. I forgot. Googling doesn''t help
--
This message posted from opensolaris.org
Boris Derzhavets
2009-Jul-19 10:25 UTC
Re: How to disable checksum offloading for OSOL DomU via kmdb at initial boot ?
::bp xnf`_init :c xnf_cksum_offload/W 0 :c Thank you. -- This message posted from opensolaris.org
David Edmondson
2009-Jul-20 08:02 UTC
Re: How to disable checksum offloading for OSOL DomU via kmdb at initial boot ?
* no-reply@opensolaris.org [2009-07-19 10:03:41]> Adding -kd to extra line drops me to kmdb :- > > root@ServerJaunty:/home/boris/nevada# xm create -c osol.install > Using config file "./osol.install". > Started domain osol.install (id=4) > Loading kmdb... > Welcome to kmdb > Loaded modules: [ unix krtld genunix ] > [0]> > > I want patch kernel like it happens when adding to /etc/system:- > set xnf:xnf_cksum_offload = 0 > Please, advise how to manage. I forgot. Googling doesn''t helpIs this still necessary? What version of OpenSolaris are you using? dme. -- David Edmondson, Sun Microsystems, http://dme.org
Boris Derzhavets
2009-Jul-20 10:38 UTC
Re: How to disable checksum offloading for OSOL DomU via kmdb at initial boot ?
Please, view :- http://www.nabble.com/Opensolaris-domU-unable-to-get-dhcp-lease-td24554248.html Through my experience OSOL 2009.06 (SNV_111b) has old bug. SNV_117 works OK. I just cannot test every Nevada build for this issue. -- This message posted from opensolaris.org
David Edmondson
2009-Jul-20 10:43 UTC
Re: How to disable checksum offloading for OSOL DomU via kmdb at initial boot ?
* no-reply@opensolaris.org [2009-07-20 11:38:32]> Please, view :- > http://www.nabble.com/Opensolaris-domU-unable-to-get-dhcp-lease-td24554248.html > Through my experience OSOL 2009.06 (SNV_111b) has old bug. > SNV_117 works OK.Ah, okay. If 117 works fine then I''m happy.> I just cannot test every Nevada build for this issue.Understood. Thanks for your help. dme. -- David Edmondson, Sun Microsystems, http://dme.org
Boris Derzhavets
2009-Jul-21 14:25 UTC
Re: How to disable checksum offloading for OSOL DomU via kmdb at initial boot ?
In case of successful dhcp lease for OSOL DomU the tcpdump log captured on any
other box on the LAN appears to have enties :-
17:21:18.435359 IP (tos 0x0, ttl 255, id 63827, offset 0, flags [DF], proto UDP
(17), length 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok]
BOOTP/DHCP, Request from 00:16:3e:1b:c3:b5 (oui Unknown), length 300, xid
0xc5c170eb, Flags [none] (0x0000)
Client-Ethernet-Address 00:16:3e:1b:c3:b5 (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
MSZ Option 57, length 2: 1472
Lease-Time Option 51, length 4: 4294967295
Vendor-Class Option 60, length 11: "SUNW.i86xpv"
Parameter-Request Option 55, length 7:
Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
Domain-Name, BR, Vendor-Option
17:21:18.435427 IP (tos 0x0, ttl 64, id 32888, offset 0, flags [DF], proto UDP
(17), length 66) ServerJaunty.local.55323 > ns.yyyy.xx.domain: [bad udp cksum
114a!] 48715+ PTR? 0.0.0.0.in-addr.arpa. (38)
17:21:18.436895 arp who-has 192.168.1.37 tell 192.168.1.1
17:21:18.437081 arp who-has 192.168.1.38 tell 192.168.1.1
17:21:18.437385 arp who-has 192.168.1.40 tell 192.168.1.1
17:21:18.437583 arp who-has 192.168.1.41 tell 192.168.1.1
. . . . .
17:21:22.825307 IP (tos 0x0, ttl 255, id 63828, offset 0, flags [DF], proto UDP
(17), length 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok]
BOOTP/DHCP, Request from 00:16:3e:1b:c3:b5 (oui Unknown), length 300, xid
0xc5c170eb, secs 4, Flags [none] (0x0000)
Client-Ethernet-Address 00:16:3e:1b:c3:b5 (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
MSZ Option 57, length 2: 1472
Lease-Time Option 51, length 4: 4294967295
Vendor-Class Option 60, length 11: "SUNW.i86xpv"
Parameter-Request Option 55, length 7:
Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
Domain-Name, BR, Vendor-Option
17:21:23.447516 IP (tos 0x0, ttl 64, id 33390, offset 0, flags [DF], proto UDP
(17), length 71) ServerJaunty.local.53362 > ns.yyyy.xx.domain: [bad udp cksum
bd45!] 24456+ PTR? 37.1.168.192.in-addr.arpa. (43)
17:21:23.569486 IP (tos 0x0, ttl 61, id 47748, offset 0, flags [none], proto UDP
(17), length 148) ns.xxxx.yy.domain > ServerJaunty.local.53362: [udp sum ok]
24456 NXDomain q: PTR? 37.1.168.192.in-addr.arpa. 0/1/0 ns:
168.192.in-addr.arpa. SOA prisoner.iana.org. hostmaster.root-servers.org.
2009020501 1800 900 604800 604800 (120)
17:21:23.669704 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 71) ServerJaunty.local.mdns > 224.0.0.251.mdns: [bad udp cksum
1d0d!] 0 PTR (QM)? 37.1.168.192.in-addr.arpa. (43)
17:21:24.205153 IP6 (hlim 1, next-header Options (0) payload length: 36)
fe80::216:3eff:fe1b:c3b5 > ff02::16: HBH (rtalert: 0x0000) (pad1)(pad1)[icmp6
sum ok] ICMP6, multicast listener report v2, length 28, 1 group record(s) [gaddr
ff02::1:ff1b:c3b5 to_ex { }]
17:21:24.435430 IP (tos 0x0, ttl 255, id 63829, offset 0, flags [DF], proto UDP
(17), length 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok]
BOOTP/DHCP, Request from 00:16:3e:1b:c3:b5 (oui Unknown), length 300, xid
0xb5ef2191, secs 4, Flags [none] (0x0000)
Client-Ethernet-Address 00:16:3e:1b:c3:b5 (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Request
Lease-Time Option 51, length 4: 4294967295
MSZ Option 57, length 2: 1472
Requested-IP Option 50, length 4: 192.168.1.37
Server-ID Option 54, length 4: 192.168.1.1
Vendor-Class Option 60, length 11: "SUNW.i86xpv"
Parameter-Request Option 55, length 7:
If checksum offloading is disabled via kmdb installer will succeed in 10 from 10
attempts,
otherwise in 1 or 2 from 10 attempts, even worse.
--
This message posted from opensolaris.org