> I did several installs on Box2 and succeeded every time for SNV87,89,90 DomUs
> at
> SNV91 Dom0 . DHCP request took 20-30 sec as maximum.
> I did also same attempts on Box1 and every time DHCP request for DomU timed
> out.
> It looks like 6703227 is hardware dependent . Per CR xnf gets DHCPOFFER
> (PACK ?)
> before it gets plumbed and brought up by DomU , but eventually recovers.
> Then why it doesn't happen on Box1 (network operates faster and has different
> architecture)
> xnf never recovers. Moreover if i install DomU with static IP , then
> # ifconfig xnf down
> # ifconfig xnf unplumb
> # ifconfig xnf plumb
> # ifconfig xnf dhcp
> It hangs ....
eventually recovers ==> it recovers after the domU has transmitted 192 packets.
It isn't that easy to transmit so many packets, because domU won't see incoming
packets.
A workaround for 6703227 is to lower the tunable "xnb_unmop_hiwat"
for the xnb (network backend) driver in dom0.
In your solaris dom0, run this as root:
echo "xnb_unmop_hiwat/W1" | mdb -wk
(this disables the xnb optimization from CR 6616384).
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
[email protected]
